OUTTASKING REGULAR TASKS THAT CANNOT BE AUTOMATED
Creating clients, copying clients, deleting clients, etc
If you want to skip the backgrounds and prefer a direct step-by-step guide, you can jump directly into the last section. Preparation For this workaround, you need access to both the source system and the BW system. In addition, they shall have the possibility to access the SE37 and execute functional modules there. Especially in production systems this is a very critical justification. So assume that you may need a Firefighter user for this action. Working in the BW system Now that the preparations have been completed, you have to call a FuBa on the BW system and on the source system, which solves the connection on the respective page. Beginning on the BW system, go into the transaction SE37 and call the function block "RSAR_LOGICAL_SYSTEM_DELETE": RSAR_LOGICAL_SYSTEM_DELETE Enter the required values here. The following table helps you fill in: Field Description I_LOGSYS The logical name of the source system. The name of the source system, as found in RSA1, will be entered here. In addition, this name can also be found in the DB table TBDLT. I_FORCE_DELETE Boolean, X = Delete despite error messages I_NO_TRANSPORT Boolean, X = This change should not be transported to subsequent systems I_NO_AUTHORITY Boolean, X = Ignore Permission Checks Work in the source system In the source system, go to transaction SE37 and call the function block "RSAP_BIW_DISCONNECT" : The descriptions of the fields are as follows. These can be found in the RSBASIDOC source system connection table Field Description I_BIW_LOGSYS The logical name of the BW system. In the RSBASIDOC table, find the correct value in the column "RLOGSYS". I_OLTP_LOGSYS The logical name of the source system. The column ‘SLOGSYS’ in the table RSBASIDOC. I_FORCE_DELETE The logical name of the BW system. In the RSBASIDOC table, find the correct value in the column "RLOGSYS". Completion In the end, you have to call the respective function block in the BW and source system, fill in the parameters and execute the function block.
What are the requirements and benefits of a modern identity management system (IDM) in the GRContext and what should be taken into account in application processes? Modern companies need to be able to effectively control their employees' access and system permissions to ensure optimal corporate control and monitoring. This need can also be inferred from legal requirements. IDM is the user and permission management within an organisation. These systems are an essential part of the internal control system. This includes the continuous monitoring and allocation of access possibilities as well as the systematic securing of functional separation (SoD - Segregation of Duties) in the IT systems. This is primarily intended to better manage relevant business and financial risks and to prevent criminal acts. The management of user and permission structures must ensure that, when the roles and responsibilities change, the privileges of the employees concerned in the systems are adjusted. Failure to do so will result in a multi-department employee having extensive privileges that can be critical in combination. Trust is good, control is better In order to avoid employees being entitled beyond your area of competence, user data and permissions must be continuously adjusted to the current requirements. It therefore makes sense to regularly carry out a recertification process in which the role owner and the manager sign off in compliance with the four-eye principle that the employee is entitled to the current privileges or may have to be deprived of rights from previous activities. Provisioning as a central function of the IDM Provisioning components form a central function of IDM systems, which provide users with individual access rights for the required IT resources according to their task.
Maintenance and transport of application and system modifications
Database layer: The database layer contains a database server on which all the data of the SAP ERP system is managed. This includes the database management system (DBMS for short) and the actual dataset. The dataset includes user data and data tables as well as applications and system control tables.
Tools such as "Shortcut for SAP Systems" are extremely useful in basic administration.
If you want to get more information about SAP basis, visit the website "www.sap-corner.de".
Data exchange between two systems requires a valid RFC connection to the receiver system and a transactional RFC IDoc port.