Controlling users and access rights
SAP Basis Consulting
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.
Do you know how to execute SQL commands on the tables in your SAP system? In the past, I asked myself the same question when I wanted to run prepared Querys on a table without converting it to a query over the SE16N with appropriate filters. After my research, I came across a simple way to have your SQL statements resolved transaction-based by an editor. This is the approach I'll describe to you in the following post. You may know the situation that you want to quickly put a short SQL statement on your SAP system without having to invest much effort in ABAP programming. You may not have the ABAP knowledge to extract data from a table, but you are familiar with SQL.
Over time, the tasks associated with the base became more complex and time-consuming, so that only the consultants could handle them. A need arose to hire a person to deal only with Basis matters.
SAP administrators can basically be found wherever SAP systems are used. These are now numerous industries and departments of companies. SAP systems can be found in accounting, costing, activity-based costing and controlling. In all these areas, they take care of the smooth functioning and development, thus helping the company to make internal processes more efficient and consequently save costs and resources.
With "Shortcut for SAP Systems" a tool is available that greatly facilitates some tasks in the SAP basis.
After that, these roles should be exported from the system (for example, to an Excel file) and then submitted to the supervisor so that he can decide whether the role assignment is appropriate or not.
Different levels of personalisation The data can be stored either to the user, to roles or to the system.