SAP Authorizations Preventing sprawl with the workload monitor - SAP Corner

Direkt zum Seiteninhalt
Preventing sprawl with the workload monitor
Controlling permissions for the SAP NetWeaver Business Client
In the PRGN_CUST table, set the customising switch REF_USER_CHECK to E. This prevents you from using other types of users than reference users. This switch only affects new mappings; You should manually clean up any existing mappings of other user types.

Administrative activities are used to control system behavior and make various security-relevant settings. To minimize the risk of a system failure or the creation of a security vulnerability, administrative rights should only be granted to employees in the basic administration. The following list may be supplemented by suggestions from the company's own administration. It contains only the most important authorization objects for each subject area.
Immediate authorization check - SU53
For an overview of the active values of your security policy, click the Effective button. Note that not only the attributes you have changed are active, but also the suggestion values you have not changed.

For table logging, it must be ensured that SAP® Note 112388 (tables requiring logging) is fully implemented and that all tables containing financially relevant data are also included in the logging. Of course, this also applies to all Z-tables! As last point of the important parameter settings are those for the definition of the password settings. Here, it should be ensured that the parameters are also set up in accordance with the company's specifications. However, the check should not only focus on the global settings that are valid for all users, but should also include all those users who have been assigned their own security policies. Especially for these, an appropriate justification must be available in writing.

The possibility of assigning authorizations during the go-live can be additionally secured by using "Shortcut for SAP systems".

You should therefore protect the passwords in your system in various ways.

You can also find some useful tips from practice on the subject of SAP authorizations on the page www.sap-corner.de.


In the SCUA transaction, which you typically use to create or delete a ZBV distribution model, you can temporarily disable a subsidiary system.
SAP Corner
Zurück zum Seiteninhalt