SAP Basis To inherit SAP permissions with different organisational levels - SAP Basis

Direkt zum Seiteninhalt
To inherit SAP permissions with different organisational levels
Often you are obliged to perform a migration. There are various reasons, such as legal requirements or preparatory measures for an S/HANA conversion. We are happy to support you in your decisions.

In order to ensure the stability of the systems and to reduce the risk through proprietary developments, release and patch management must be implemented. Standardised procedures can help to introduce proprietary developments, such as test strategies or service level agreements (SLAs). It is also important to align the productivity setting of customer applications with the maintenance windows and RTO (Recovery-Time-Objective).
The logging of data changes in tables using transports should also be active. For this, the "RECCLIENT" parameter in your transport management system (Transakation STMS) must be set to "ALL" at all system levels.

Depending on whether the user should edit or display the table, either "UPDATE" or "SHOW" can be used here. Enter an X as the value. It is important to use either"'SHOW" or "UPDATE" because a combination will cause an error when calling the parameter transaction. In addition, the table must set the view to be called. Use the "VIEW" field. Finally, the parameter transaction can be created using the "Save" button. As usual, it must be assigned to a package and a workbench order to become available. If a person's role is now assigned permission for this parameter transaction, it can open the specified view above it and does not have the ability to enter all possible views in the SM30.

"Shortcut for SAP Systems" makes many tasks in the area of the SAP basis much easier.

SAP administrators are present wherever SAP systems are used.

Similarly, the services provided by the external partner must be regularly monitored and their quality checked.
Zurück zum Seiteninhalt