INTRODUCTION OF RELEASE AND PATCH MANAGEMENT
Connection of cloud services
For existing solutions, it is necessary to assess to what extent the solution is customised. A modification is the more serious the more time-consuming the maintenance is, including testing, e.g. in the case of upgrades. The fewer customer specifications are available, the more suitable a system or application is for external operation by a service form to be chosen.
Administrators often need to replicate part or all of a database, for example, to create a system backup or test an upgrade before putting it into production. In the past, this was surprisingly difficult to do with most databases. With HANA, replication works instantly and offers richer features and better control than previous databases.
High sense of responsibility
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.
People tend to forget how important this element of the architecture is. The structure associated with it often proves to be especially important for companies that want to implement the SAP system for the first time.
For administrators, a useful product - "Shortcut for SAP Systems" - is available in the SAP basis area.
The website www.sap-corner.de offers many useful information about SAP basis.
Fiori Eligibility for OData Services The launch authorisation for the OData service stored in the backend from a Fiori app is queried on both the front-end and back-end servers when the application is launched.
It thus forms the interface to the users (GUI).