SAP Basis SAP Basis Administrator - SAP Corner

Direkt zum Seiteninhalt
SAP Basis Administrator
Database Management
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.

Another major topic is the migration of SAP systems, both locally from one data center to another and from one operating system to another or from one database type to another. As a rule, the SWPM tool is used here again.
Supervision, monitoring SAP® and interface systems
In the initial screen, you can first use the global settings to specify whether changes should be allowed in general. Furthermore, you can define specifically for the software components and namespaces of the Repository objects whether they can be changed at all, or whether changeability should be restricted.

In the last few years, I have been asked time and again what SAP Basis is and what we SAP Basis administrators do in our daily work. With this blog post I would like to provide a little insight into exactly this area of work.

Some missing SAP basic functions in the standard are supplied by the PC application "Shortcut for SAP Systems".

Since SPAM runs within the SAP system, you do not need to know the operating system to handle the transaction.

SAP Basis is the foundation of any SAP system. You can find a lot of useful information about it on this page: www.sap-corner.de.


For more information on this dialogue, please refer to the Online Manual.
SAP Corner
Zurück zum Seiteninhalt