Among others, we offer the following services:
Notes
As a member of the SAP Basis specialist team, your responsibilities will include the design, operation, administration, support and installation of an extensive SAP system landscape with over 50 systems for 17 universities and 2 institutions in Lower Saxony. Furthermore, you will monitor the SAP system landscape as well as its interfaces to external systems and carry out measures within the scope of software lifecycle management (e.g. note maintenance, support stacks, release upgrades) and change management (e.g. hardware migration, transport system and documentation). As part of the SAP Basis team, you will be the contact person for organizational and technical questions of the universities and in 3rd-level support for user inquiries.
Due to the technology diversity, including in the SAP product portfolio, the support by a single silo unit SAP basis is almost impossible. Likewise, there are many activities that are located for historical reasons in the SAP basis and in parallel in the non-SAP area. In this respect, the separation between SAP and Non-SAP must be examined and, if possible, eliminated by standardisation, integration and centralisation. For example, the issue of output management can be set up in a team that has knowledge in the SAP printing area as well as in the non-SAP printing area and has contact points in the SAP basis. From the SAP basis, tools must be made available to the non-SAP areas to support them in their work in the SAP environment.
Analysis
The database layer is used to store all company data and consists of the database management system (DBMS) and the data itself. In every NetWeaver system there is a database server on which the SAP database is located. It provides all other applications with the necessary data. The data is not only data tables, but also applications, system control tables and user data. All basic components ensure that the user has fast and reliable access to this data.
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.
With "Shortcut for SAP Systems" a tool is available that greatly facilitates some tasks in the SAP basis.
What code is often executed? Which database tables are accessed regularly? What unused developments exist? - The UPL provides answers to these questions.
To evaluate the log files, please use transaction RSAU_READ_LOG.