SAP Authorizations Manual authorizations

Direkt zum Seiteninhalt
Manual authorizations
System Settings
Roles can be assigned to users directly through user management in the SU01 transaction, role maintenance in the PFCG transaction, or mass change of users in the SU10 transaction. However, if the employee changes his or her position in the company, the old roles must be removed and new roles assigned according to the new activities. Because PFCG roles are created to represent job descriptions, you can use organisational management to assign roles to users based on the post, job, etc.

This approach makes authorization management considerably more efficient, since functional changes do not have a global impact on the entire authorization structure. This ensures the quality of authorizations in the long term. Authorizations in SAP systems enable users to access the applications relevant to their activities. To ensure that processes are mapped securely and correctly, SAP authorizations must be regularly checked and reworked.
Roles and permissions in SAP SuccessFactors often grow organically and become confusing
In this case, please note that you may need to replace the SS table permission group with other table permission groups. This is required if you have entered a different table permission group when maintaining the table permission groups, for example, for the T000 table.

Regardless of whether you select the degree of simplification COARS = 1 or 2, you should not enter * or SAPDBPNP (programme name of logical database PNP) in the REPID field. With these values, you allow access to the logical databases SAPDBPNP and SAPDBPAP and thus to all contained root data.

During go-live, the assignment of necessary authorizations is particularly time-critical. The "Shortcut for SAP systems" application provides functions for this purpose, so that the go-live does not get bogged down because of missing authorizations.

The website www.sap-corner.de offers many useful information about SAP basis.


A password lock only prevents a user from logging in via his password, because the number of errors is only evaluated if the login is done by password.

So much information... how can you keep it so that you can find it again when you need it? That's what Scribble Papers is great for.


Therefore, the structures of the company and the relevant processes must be analyzed in detail during the creation process.
Zurück zum Seiteninhalt