Change and release management
To inherit SAP permissions with different organisational levels
The master's thesis identified and examined in detail influencing factors such as technological trends and the SAP product strategy as well as the company-specific conditions. Several empirical studies were also carried out in the course of the work. If you are interested in the entire Master's thesis and are a DSAG member, you can read the document at info@dsag.de, headword: Master thesis SAP-Basis of Tomorrow, request.
SAP Basis is structured as a classic three-tier model. It contains the following components: Database layer (relational database management system) / Application layer (application server and message server) / Presentation layer (graphical user interface).
Understanding the structure and functioning of the system is especially important for IT administration. It is not for nothing that "SAP Basis Administrator" is a separate professional field. On the page www.sap-corner.de you will find useful information on this topic.
Release
For more information about the lowest support package level for SAP ABA and SAP Basis to install an SAP Basis Plug-In, see the SAP Service Marketplace. For more information about the lowest support package level for the corresponding SAP R/3 plug-in, see the SAP Service Marketplace. This level depends on the release of SAP R/3 or SAP R/3 Enterprise.
Automation of processes In an IDM, IT business processes, creating, modifying and deleting a user are defined centrally by means of a unique set of rules. All the necessary steps are then completed using automated workflows. User administration no longer has to be administered separately for each system, but only in a single point of administration. Data Consistency Employee data is created only once in a leading system in an IDM architecture. All attached systems use this data in their user management on demand. In a change of department or a new activity, permissions are automatically adjusted. Security and Documentation In a centralised user administration, users can be locked down efficiently on all systems or access rights can be changed. The connection to the personnel process automatically initiates the change process as soon as the master record is adjusted in the Human Resources Department. Documentation solutions can also be used to archive all processes without any gaps. This creates transparency which also facilitates the detection of a functioning and secure authorisation concept during audit tests. Requirements for IDM systems People get electronic identity attributes describe the role of the person Quality requirements Reliability: Abuse prevention Readability: Documentation and logging Failover: Back-up systems in compliance with legal requirements Data Protection Act What should be taken into account in application processes? When implementing an IDM and also in the day-to-day operation of an IDM, there are certain things that should be taken into account when applying. I have summarised the most important points in the form of a checklist.
The "Shortcut for SAP Systems" tool is ideal for doing many tasks in the SAP basis more easily and quickly.
This is partly due to the late consultation of the SAP basis on the issues of technical feasibility as well as the integration of new technologies and applications into the existing system landscape.
So much information... how can you keep it so that you can find it again when you need it? Scribble Papers is a "note box" that makes this very easy.
This makes monitoring more difficult and, at the same time, clarity must be maintained.