OUTSOURCING NON-SAP PRODUCT MANAGEMENT
SM21 System log
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.
SAP Basis ensures smooth operation of the SAP Basis system. The SAP Basis system is a kind of operating system of the R/3 system or SAP ERP. It includes three layers: database, application and presentation. In addition, Basis includes many SAP middleware programs and administration tools. With Basis SAP applications can be used compatible and independent of operating system and database and can be enriched with the necessary data.
Potential security risks in application processes in IDM systems
In the context of the SAP basis, the deployment of an SAP application server for any SAP system can be used as an example. Parameters include processor count, memory, disk space, operating system, and run-time environment.
NEW TECHNOLOGIES AND INNOVATIONS The role of IT is changing (bi-modal IT). On the SAP basis, this new bi-modal organisation is particularly true. On the one hand, it is necessary to continue to ensure the SAP operation in the usual stability and security, and on the other hand, to act as a business innovator in order to fulfil the role as a technology consultant for SAP technology. ADJUST SAP basis NAMING The original definition and naming of the SAP basis no longer meets today's task. Therefore, it is recommended to give the SAP basis a meaningful and contemporary description depending on the future organisation form. For example, the bi-modal role listed in Recommendation [A1] should be taken into account.
Use "Shortcut for SAP Systems" to accomplish many tasks in the SAP basis more easily and quickly.
In this case, the critical SAP permissions are usually predefined by special verification software.
Some useful tips about SAP basis can be found on www.sap-corner.de.
Deleting assignments between users and roles if either the user or the role does not exist.