SAP Basis Solutions for production environments and as proof of concept (PoC)

Direkt zum Seiteninhalt
Solutions for production environments and as proof of concept (PoC)
Defined service level agreements (SLAs)
Here, too, the requirements profile for SAP Basis experts has shifted: Database administration is simply part of the job today. The majority of SAP customers place the SAP HANA database in the hands of the Basis team for build and run operations.

The consistent implementation of the role concept enables a manageable complexity of the tasks per employee. At the same time, through the respective SMEs, the concept creates expertise in specific topics and enables communication on an equal footing with upstream or downstream IT departments as well as with external service providers. The establishment of technology architects also ensures that the overall picture is not left out of sight in the context of the SAP product portfolio. Deficits can also be addressed on issues such as policies and security. Overall, the role concept provides guidance for the employees and their career planning as well as guidance regarding the range of tasks and contacts for IT departments and business areas.
What are the areas when working with SAP systems?
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.

But when it comes to the intricacies of large SAP environments, Ansible quickly reaches its limits. If you want to use Ansible to implement simple automations - for example, starting and stopping SAP environments - you have to put up with a lot of manual effort and complicated scripts.

"Shortcut for SAP Systems" is a PC application that simplifies or even facilitates many activities in the SAP basis.

The SAR files are unpacked with SAPCAR and checked for their digital signature.

A note box in which data of all kinds can be quickly filed and retrieved. This is what Scribble Papers promises. At first, the program looks very spartan. But once a small structure is in place, you realise the great flexibility of this little helper.

Through a sound expertise in the SAP technology environment, it is recommended to bring the know-how of the SAP basis into the IT strategy and IT roadmap.
Zurück zum Seiteninhalt