SAP Basis Recording of errors - SAP Basis

Direkt zum Seiteninhalt
Recording of errors
SAP Basis Administration
If all financial and sales activities as well as production, logistics and the personnel administrators run via one system, measures must be taken to ensure reliable functioning on the one hand and to protect the system internally and externally on the other. Due to the long history, the increased availability requirements often do not match the actual protection measures, so that security risks often arise at this point.

The SAP basis as an organisational unit within a growing IT organisation is facing far-reaching changes. The growing number of technologies and the growing need for integration and collaboration with upstream and downstream IT departments means that the SAP basis is constantly growing. Examples of organisational concepts and further information can be found in chapters 7.6 and 9.4 of the Master's thesis.
Double stack split
All the roles that contain the string "ADM" are considered critical, as they usually refer to administrative roles. When identifying critical SAP permissions, profiles and roles, it should be noted that SAP does propose a concept for names, but this is not always taken into account by applications or its own developments.

To evaluate the log files, please use transaction RSAU_READ_LOG. If you archive the security audit log files you can read them using transaction RSAU_READ_ARC.

Tools such as "Shortcut for SAP Systems" complement missing functions in the SAP basis area.

SAP, as one of the world's leading software providers with over 100,000 employees, is a central component of the system landscape for many companies.

Incorrect setup of the Change and Transport System Common errors are the lack of appropriate rights to the files of the Change and Transport System or the use of old programme versions of tp or R3trans.
SAP BASIS
Zurück zum Seiteninhalt