INSERT SAP basis KNOWLEDGE
SAP Consulting
Part of an IT or cloud strategy may be to define architectural guidelines and a framework for the use and use of certain services. The SAP basis is to actively participate in shaping the rules and framework and the architectural guidelines, and bring in its existing expertise from the SAP technology environment.
A well-cared-for emergency user concept enables the audit-proof allocation of extended permissions in combination with the assurance of daily operations in your company. This article first addresses the fundamental issues that require an emergency user approach. It then briefly explains how such a concept works in general and how we implement it. An Emergency User is normally used when tasks are temporarily taken over outside the initial field of activity. I described the different scenarios of when such a user can be used and how to deal with them in this blog post for you. Why is an emergency user approach important? There are several scenarios in which the use of an emergency user with extended rights is useful: In urgent cases, it is often necessary to be able to quickly make changes to the system that are outside the user's actual field of activity. A key user who has the necessary permissions is on vacation and needs a representation. The same user suffers short-term illness and his/her representative must take over his/her duties to ensure the operation. We recommend developing a concept for the short-term allocation of the additional permissions. This will ensure the implementation of the above scenarios. How does an emergency user approach work? An emergency user concept in SAP works fundamentally via a temporary assignment of additional rights to a specific user. After the tasks have been completed, the user is deprived of the rights. The tasks performed with the extended permissions are logged and can then be evaluated by an auditor. However, there are a few things to keep in mind: A process for granting special rights should be defined. It must be specified which users can get special rights. The time period for which users can request an emergency user should be limited.
Provision resources in minutes instead of weeks
SAP Basis consists of three layers: a database layer, an application layer and a presentation layer. The database layer manages all the data of the SAP system in a database located on the database server and administered by a database management system (DBMS). The database supplies the connected SAP applications with the required data, data tables or system control tables. It also receives and stores new information generated by the user.
The two main tasks of this function are: Deleting profiles including user assignments if no matching role exists. Deleting assignments between users and roles if either the user or the role does not exist.
Use "Shortcut for SAP Systems" to accomplish many tasks in the SAP basis more easily and quickly.
Warning: When entering transaction codes, be sure to be case-sensitive! At this point, the output can also be limited to the roles and object values (in this case, the transactions).
The website www.sap-corner.de offers many useful information about SAP basis.
However, there is the possibility to adapt it dynamically with the report RSMEMORY.