SAP Authorizations Criticality - SAP Basis

Direkt zum Seiteninhalt
Criticality
Analyze user buffer SU56
In order to perform an operation in the SAP system, several authorizations may be required. The resulting interrelationships can become very complex. In order to nevertheless offer a procedure that is manageable and easy to handle, the SAP authorization concept was implemented on the basis of authorization objects. Several system elements to be protected form an authorization object.

The difficulty in assigning permissions to the S_DATASET object is determining the correct values for the FILENAME and PROGRAMME fields. If you have not specified a path in the FILENAME field, only the files in the DIR_HOME directory will be allowed.
Temporarily disable Central User Management
The evaluation performance of the Security Audit Log was optimised from SAP NetWeaver 7.31. For this extension, you need a kernel patch. For the fixes and an overview of the required support packages, see SAP Note 1810913.

In compliance with the minimum principle and the separation of functions, the roles used must be defined, along with specifications for their naming, structure and use. Close attention should also be paid to the application and allocation process in order to prevent authorization conflicts, which arise primarily as a result of employees' changing or expanding areas of responsibility.

With "Shortcut for SAP systems" you can automate the assignment of roles after a go-live.

These can be internal auditors, auditors or developers.

To generate the role profile, switch to the Permissions tab.
SAP BASIS
Zurück zum Seiteninhalt