Implementation of your user and security management
SAP BASIS OPERATIONS
In addition to the database, the SAP system itself is installed. This installation is planned using a tool from SAP, the "Maintenance Planner", and then carried out using the SWPM (Software Provisioning Manager) and SUM (Software Update Manager) tools.
With SAP Basis, SAP delivers the foundation of its software. Based on this foundation, SAP applications can be used independently of the operating system and database, interact with each other and be enriched with data. Based on a client/server architecture, SAP Basis includes configuration, a relational database management system, and a graphical user interface.
A new SAP system is created...
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 recommends a role design for Fiori permissions based on the defined catalogues and groups in the launchpad. In such a catalogue there is usually a set of apps and services which is relevant for a specific user group. If a role for one or more catalogues in the launchpad has been authorised, the corresponding catalogues and groups will be displayed in the app finder only for eligible users when the launchpad is launched. This ensures that every user only sees what they are working with. Important: These Fiori permissions are maintained on the frontend server! Maintain catalogue permissions in the PFCG To add a Fiori permission to open a catalogue for a role, reopen this role in the PFCG in Change mode and follow the next steps: 1) Select Menu tab 2) Click on the small arrow to add an item 3) Select "SAP Fiori Tile Catalogue" Then select the corresponding Catalogue ID for which the selected role should be eligible. Now the role only has to be assigned to the corresponding users in the system. Once you have completed these steps, you will have the Fiori permissions you need to view individual tile catalogues on the launchpad.
"Shortcut for SAP Systems" simplifies tasks in the area of the SAP basis and complements missing functions of the standard.
That is, in the first area you can set Extended Memory (Storage Class 1) and Heap Memory (Storage Class 2) for Dialogue Workprocesses, and in the second area you can set it for non-dialogue workprocesses.
Application of SNOTE and elimination of errors.