SAP Authorizations Check for permissions on the old user group when assigning a new user group to a user - SAP Corner

Direkt zum Seiteninhalt
Check for permissions on the old user group when assigning a new user group to a user
Take advantage of roll transport feature improvements
In case of missing authorizations, SAP Basis also helps with an authorization trace in addition to the well-known SU53 for a more detailed analysis of authorization objects. The article "SAP Basis Basic or finding missing authorizations thanks to SU53 or ST01 Trace" describes this in more detail.

First, consider the transport of your proposed permissions from various development systems to a consolidation system. When you save permission proposal values in transport orders, you will notice that generic entries are used instead of detailed BOMs. These generic entries mark all applications, for example, with TR*..
Use the authorisation route to identify proposed values for customer developments
The SAP Note 1903323 provides a solution. The functionality is only provided via support packages for NetWeaver releases 7.31 and 7.40. This fix extends the naming conventions so that namespaces in the /XYZ/ format can be used up to a maximum of eight characters. In the development and creation of authorization objects, some functionalities of the SAP hint are extremely helpful, which we present in this tip.

First of all, represent your organisation. Map the business processes (if necessary only at the generic level of applications such as MM or CO) across the organisation. On this basis, determine which organisational characteristics (organisational levels, but also cost centres, organisational units, etc.) represent which parts of the organisation. Define (if necessary, only in detail in accounting, otherwise at the level of applications) which functions must necessarily remain separate. If you have a running system, evaluate the use of the last 13 months (see Tip 26, "Use usage data for role definition"). Set up a new system and make sure that processes are always documented to the level of transactions. In such a case, it is also best to collect the business risks directly in the process description.

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

Note the implications if you want to actually run this programme.

At you will also find a lot of useful information on the subject of SAP authorizations.

Check these suggestion values by clicking Yes in the S_TABU_NAM column.
SAP Corner
Zurück zum Seiteninhalt