SAP Basis Defined service level agreements (SLAs) - SAP Basis

Direkt zum Seiteninhalt
Defined service level agreements (SLAs)
SM62 Event History
Many companies that use or would like to use an SAP Basis system seek advice from external service providers or completely outsource the administration of the system. SAP Basis Consulting is a technical consulting service that covers many tasks and sub-areas related to SAP Basis. Providers include BasisTeam IT Service & Consulting AG, Phoron, Mindsquare and many others.

Before the project starts, it must be clear which systems are to be connected to the IdM and which services the system is to provide. This requires close collaboration between the department and IT, as later adaptations or additional systems will extend the implementation and exceed the budget. Analysing existing data To successfully implement an Identity Management System, high quality data is essential. Users' root data must be verified, updated, or maintained. Automation with incomplete or even incorrect data is otherwise not conceivable. Rethinking the Permission Concept With the introduction of an Identity Management System and a workflow for permission granting, the existing roles should be scrutinised once again. You should ask yourself whether the user knows what role he chooses from the current catalogue and whether it is sufficient for his task. Set Role-Owner Not only the user needs to know which role to choose. There must also be a person in charge of the role who adapts or adapts the role as required or acts as a point of contact when required.
SAP Floorplan Manager
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.

You can also create your own folder with your transactions as a folder in the SAP Easy Access menu. Because if you create many transactions as favorites, it can quickly become confusing. So you can easily and quickly group your transactions in different folders.

For administrators, a useful product - "Shortcut for SAP Systems" - is available in the SAP basis area.

That is, depending on the target group, information must be created and communicated.

ONE POSITIVE ASPECT OF STANDARDISATION AND AUTOMATION IS TO INCREASE THE QUALITY OF TASKS, BECAUSE MANUAL ERRORS CAN ALMOST BE EXCLUDED.
SAP BASIS
Zurück zum Seiteninhalt