Roles
Authorization management: Preparation and follow-up of audits as well as ongoing or selective support
Daily monitoring and maintenance of your systems. Together with you, we create a catalog of measures to ensure the optimal operation of your SAP landscape.
There are the following reasons that may lead to the termination of this step: CANNOT_GET_OBJECT_LIST: The Object List of a Support Package could not be found because the Support Package does not exist. CANNOT_GET_LAST_UPGRADE_INFO: Unable to locate information about the latest Repository Switch upgrade. UNRESOLVED_ADDON_CONFLICTS: Conflicts with add-ons could not be resolved because the corresponding CRTs from the queue are missing. SPDD_SPAU_CHECK This step will check if a modification match (transactions SPDD/SPAU) is necessary. DDIC_IMPORT This step imports the ABAP Dictionary.
Planning
User name without restrictions - critical? Depending on the release of the SAP_BASIS component in your system, invisible special characters may end up in the user name. This is especially critical if only spaces or alternate spaces are used for the user name when creating a new user. In Unicode systems, "alternative" spaces, so-called "wide spaces", can be used in addition to the normal space character (hexadecimal value 20). For example, the key combination "ALT+0160" can be used to insert non-breaking spaces. If a user is now created whose user name consists exclusively of such alternative spaces, this can be confusing. This is because entries for this user ID do appear in change documents, but the impression is created that the entry was created by a non-existent / deleted user. This circumstance can lead to confusion. In addition, certain special characters in the user name can also lead to errors, for example in the Change and Transport System (CTS). This is because the user name is also used in the CTS-ORG to create a file with the same name in the transport directory. Furthermore, there are letters/characters that look identical in different alphabets, but have a different hexadecimal value in the character set. This means that confusion in user names cannot be completely ruled out. Seemingly identical user names then stand for different users.
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.
With "Shortcut for SAP Systems" a tool is available that greatly facilitates some tasks in the SAP basis.
The process takes about 30 minutes.
In addition, the SAP consulting can transition to an external takeover of updates and upgrades of SAP components or even the complete takeover of the administration of the SAP system.