SAP Authorizations Evaluation of the authorization check SU53 - SAP Basis

Direkt zum Seiteninhalt
Evaluation of the authorization check SU53
Error analysis for authorizations (part 1)
For result and market segment accounting, you can define planning authorization objects, the information system, and item-based reports of the information system. In the customising (transaction SPRO), you create them via the following path and then select the corresponding section. Controlling > Income and market segment calculation > Tools > Permissions management > CO-PA specific eligibility objects.

A user trace is therefore also a trace over a longer period of time. Currency of the trace execution, the authorization check is recorded exactly once for each user.
Making the RESPAREA responsibility the organisational level
For the transport of PFCG roles with their profiles there is also an SAP notice: Note 1380203. If you enter the correction, it is possible to use separate positions for the third and fourth digits of the generated profile name for the definition. In the SAP standard, the name of a generated profile is composed as follows, for example, if the System ID is ADG: T-AG#####. If your other source systems differ only in the second place of the system ID, the profile name does not indicate from which system the profiles originate.

To maintain suggestion values, use the transaction SU24. Here you can view and customise suggestion values for all types of applications, such as SAP GUI transactions, RFC building blocks, or Web Dynpro applications. One way to maintain suggestion values is to use the system trace, which is linked to the transaction SU24 after inserting the support package named in SAP Note 1631929 and the correction instructions. This means that from the transaction SU24 you start the system trace, collect trace data and use this data directly during maintenance.

"Shortcut for SAP systems" is a tool that enables the assignment of authorizations even if the IdM system fails.

Now you can remove the SAP_NEW profile from all users.

Five years earlier, the number of cases was significantly lower - 23,562 cases - and have steadily increased from then on.
SAP BASIS
Zurück zum Seiteninhalt