SAP Authorizations SU2X_CHECK_CONSISTENCY & SU24_AUTO_REPAIR - SAP Basis

Direkt zum Seiteninhalt
SU2X_CHECK_CONSISTENCY & SU24_AUTO_REPAIR
Schedule PFUD transaction on a regular basis
SAP customers do not maintain suggested values in this transaction. However, there are cases where data in the SU22 transaction is maintained in a customer environment. If TADIR services or external services are developed by the customer or partner, these services are not available by default in the SU22 transaction or the SU24 transaction. For these services, the header data must first be written to the USOBHASH table, which serves as the basis for maintaining the services. These entries in the USOBHASH table are generated automatically when running TADIR services. Read Tip 41, "Add external services from SAP CRM to the proposal values", for dealing with external services. Once the data in this table is available, you have the option to maintain the proposed values.

Most client programmes are additions to the standard functionalities or variations of the same. Therefore, when you create your own programmes, you can follow the eligibility checks of the standard programmes or reuse the permissions checks used there.
Roles and permissions in SAP SuccessFactors often grow organically and become confusing
In addition, you must note that you may not execute this report on systems that are used as a user source for a Java system. This is due to the fact that a login to the Java system will only update the date of the last login to the ABAP system if a password-based login has taken place. Other Java system login modes do not update the date of the last ABAP system login.

S_PROJECT authorization object: The S_PROJECT authorization object enables you to work with customising projects. You can modify, view or delete projects, maintain status information, project documentation, and perform project evaluations.

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

In these cases, the total permissions from the RFC_SYSID, RFC_CLIENT, and RFC_USER fields will not be applied.

In principle, all eligibility fields can be upgraded to the organisational level; there are, however, technical exceptions and fields where this is not useful.
SAP BASIS
Zurück zum Seiteninhalt