Advanced Memory Parameters
The basics of Basis Administration
The definition, organisational structure as well as the naming of the SAP basis is historically conditioned by previous SAP software versions and components. This also results in the perception of the SAP basis and the related focus of the SAP NetWeaver and the ABAP system core, which is still widely used today. However, the scope of activities has changed significantly in terms of tasks and technology and will continue to change in view of SAP's perspective and product strategy and the changing roles of IT. In order to accommodate this change and to change perceptions both in the overall context of the SAP ecosystem and within its own company, the SAP basis must develop a new self-understanding and establish a marketing for the publication of its own performance. The underlying information can be found in the master thesis in chapters 7.4 and 9.2.
This is the heart of the SAP system. In the classic three-tier model, this would be the logic or control layer. One or more application servers host the necessary services for the various applications at this layer. These application servers provide all the services required by the SAP applications. In theory, a single server could fill this role. In practice, these services are in most cases distributed among several servers, each serving different applications.
Installation Services in all common environments
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.
However, the tasks also include strategic and planning aspects. For example, administrators define requirements and standards, select and control upgrades or extensions, implement monitoring processes, and take care of necessary backups and emergency management.
"Shortcut for SAP Systems" makes it easier and quicker to complete a number of SAP basis tasks.
The strategy chosen must be based on the value for money.
Procedure To set the scenario you want, select Additions Settings.