SAP Basis Call Inheritance Hierarchy - SAP Basis

Direkt zum Seiteninhalt
Call Inheritance Hierarchy
Configuration of email notifications
New risks in SAP HANA: In addition to the known risks, there are also new risks from the use of SAP HANA. A very good example are frequently used web applications that represent something new in the SAP area. In contrast to an SAP ERP system, HANA systems consist mainly of web applications, which were considered optional in the previous versions. These web applications can be found by various search engines on the Internet. This also applies to SAP Portal or Netweaver. There are URL schemes that help locate the system. This also applies to other SAP systems that use Web applications. This makes the new technology vulnerable to typical web attacks. SQL Injection, ABAP Code Injection, or XSS are all included. All risks known for a normal SAP system also apply to a SAP-HANA system. The data is stored unencrypted in RAM. Only then does the system gain this speed advantage. This results in risks such as a read-out by memory scraping malware. These pick up data in memory. Encryption costs performance, so it is not used by default. Especially during a migration HANA runs in a parallel system, therefore at least one new system comes to your landscape. Also note: HANA has its own tools and settings that need to be known and configured. The bottom line is that the system simply needs more attention when operating. Many settings often result in more errors. Three - points - HANA Security Plan 1) Roles and permissions In a previous SAP system, roles and permissions are certainly one of the main pillars of a secure system. Roles and permissions work differently in a HANA system. There are two types of users: 1) Default (limited): With this type of user, there are different access methods to the database. For example, the JDBC or HTTP technologies are used to give two examples.

The past ten years have primarily revolutionized the infrastructure and database layer. The fascinating thing is that there have been hardly any changes to the SAP installation program SAPinst during this time.
Practical experience at home and abroad has given us a proven view of heterogeneous system landscapes. This flows into our consulting as a further plus point and creates not only smooth functionality but also cost efficiency of your individual system landscape.

SAP Basis is the foundation of any SAP system. You can find a lot of useful information about it on this page:

IMPORT_PROPER In this step, the repository and table entries are recorded. There are the following reasons that may lead to the termination of this step: TP_INTERFACE_FAILURE: Unable to call tp interface. TP_FAILURE: The tp programme could not be run. For more information, see the SLOG or ALOG log file. TP_STEP_FAILURE: A tp-Step could not be performed successfully. The cause of the error can be found in the appropriate protocol, for example in the import or generation protocol. If the generation (tp-Step G) is aborted, you can either fix the errors immediately or after the commit is completed. In the latter case, you must do the following: To ignore the generation errors, select Additions Ignore Gen Error. Continue the playback. Buffer synchronisation problems can also cause generation errors. For more information, see Note 40584.

Some missing SAP basic functions in the standard are supplied by the PC application "Shortcut for SAP Systems".

Another would be to grant the jump permission in debugging (S_DEVELOP permission object with the ACTVT = 02 field).

See also: Generation Error [Page 30].

To store all the information on the subject of SAP - and others - in a knowledge database, Scribble Papers is suitable.
Zurück zum Seiteninhalt