Troubleshooting and fault elimination
Preparation of full access to SAP systems and solutions in case of disasters (High Availability/Disaster Recovery)
At best, for the time in which an emergency user is in service, a separate log of the activities undertaken is written, which can then be evaluated. In the following chapter I would like to explain our best practice approach to implementing an emergency user concept. Our approach to using an emergency user concept We have had good experience with the use of the Xiting Authorizations Management Suite (XAMS) in this area. This suite consists of various modules for creating role concepts, managing permissions including a permission concept, and also enables the implementation of an emergency user concept. XAMS works here with a limited time assignment of reference users with extended privileges to enable the emergency user concept. A self-service application may be made with a justification and a period for allocating special rights. The application window is illustrated in an example in the following screenshot: Evaluation of the use of the Emergency User Concept Once this request has been initiated, a new mode will be opened for the user, in which he can work with the extended rights. In addition, depending on the configuration, a stored workflow can be initiated as an approval process, or pre-defined controllers will be notified by email to verify activities. Once the session has ended with the emergency user, the responsible persons will receive another email with the logged activity of the user with the extended permissions. One of these logs is shown in the next screenshot: These logs can also be viewed in the system. Here you will get an overview of all the sessions that have been run. In addition, it is possible to approve activities with special rights after an evaluation. This allows the controller to get an overview of the activities undertaken with the emergency user. If you are using this Emergency User Concept and following these steps, you can ensure: Each user on the production system retains his or her original necessary rights.
SAP Basis operations manage the IT underlying the SAP system. In addition, the operation ensures the maintenance and availability of business processes. Various tools can be used for this purpose, which take over the maintenance, servicing, configuration and monitoring of the SAP system. Basis operation is the prerequisite for ensuring that the SAP system is fully operational and covers the business processes well.
Implementation of a highly available HANA data solution
In addition to the optimisation potential of Security Automation, which I explained in more detail in my last post, the E-Learning division also offers numerous possibilities for automation. Since many companies are not yet making the most of these potentials due to a lack of knowledge about this particular form of knowledge transfer, I would like to address this in the following post. E-learning is also a form of automation that, if used correctly, brings many positive aspects. In the end, e-learning is a way to store know-how in a form that can be retrieved again and again. This means, of course, a certain initial effort for the creator, which nevertheless pays off more than if the quality is sufficient. What are the opportunities for a company to take advantage of e-learning? A company has several ways in which it can exploit and use the area of e-learning for itself. The fundamental question that should arise immediately after the decision to do so is whether the company creates the content itself or whether it relies on the content from external sources. Both have advantages and disadvantages, which I would like to explain in the following.
Together with our SAP development team, our SAP Basis experts develop programs and transaction processes using Web Dynpro technology. This includes, for example, our SAP AddOn "SAP Password Reset". We would be happy to develop your solution.
"Shortcut for SAP Systems" makes many tasks in the area of the SAP basis much easier.
Each Support Package is valid for one release level (but for all databases and operating systems) and requires a precisely defined number of predecessors.
Some useful tips about SAP basis can be found on www.sap-corner.de.
Since the role has not yet been generated, the Permissions tab is currently highlighted in red.