SAP Authorizations Introduction & Best Practices - SAP Stuff

Direkt zum Seiteninhalt
Introduction & Best Practices
Query the Data from an HCM Personnel Root Record
Starting with SAP NetWeaver 7.31, the Security Audit Log enables the complete display of longer event parameters in messages. To do this, the maximum storage space for variables in messages has been increased to 2 GB. To play this extension, you need a kernel patch. For the fixes and an overview of the required support packages, see SAP Note 1819317.

Additional permission check on the S_RZL_ADM authorization object: For security reasons, an additional permission check is performed on the S_RZL_ADM authorization object for special PSE (Personal Security Environment) files with access type 01 (Create). These files are called *.pse and cred_v2. These files are required for single sign-on, encryption and digital signatures. They are maintained using the transaction STRUST and the transaction STRUSTSSO2, which require the same permission (see SAP Note 1497104 for details).
Centrally view user favourites
If an authorization system grows too much over the years and there is no structured approach, the result is uncontrolled growth. If companies wait too long with the cleanup, a complete rebuild of the authorization structure or a new concept may make sense. This must be clarified quickly in the event of a cleanup.

Authorizations can also be assigned via "Shortcut for SAP systems".

At "www.sap-corner.de" you will also find a lot of useful information on the subject of SAP authorizations.

GET_PASSWORDS_FOR_USER: The example implementation of this method reads the new initial passwords from the transaction buffer with the respective user ID and system.

SAP Stuff
Zurück zum Seiteninhalt