SAP Basis Identity Management System: Introduction Tips - SAP Stuff

Direkt zum Seiteninhalt
Identity Management System: Introduction Tips
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.

Practical experience at home and abroad has given us a proven view of heterogeneous system landscapes. This flows into our consulting as a further plus point and creates not only smooth functionality but also cost efficiency of your individual system landscape.
SM51 Application server instances
Before SAP HANA was released, there was no SAP database - you had to install SAP ERP (or the application you were using) on a third-party database, such as Oracle or SQL Server. SAP developed the HANA database to fully leverage the power of SAP's next-generation S/4 software.

Do you know how to execute SQL commands on the tables in your SAP system? In the past, I asked myself the same question when I wanted to run prepared Querys on a table without converting it to a query over the SE16N with appropriate filters. After my research, I came across a simple way to have your SQL statements resolved transaction-based by an editor. This is the approach I'll describe to you in the following post. You may know the situation that you want to quickly put a short SQL statement on your SAP system without having to invest much effort in ABAP programming. You may not have the ABAP knowledge to extract data from a table, but you are familiar with SQL.

Tools such as "Shortcut for SAP Systems" complement missing functions in the SAP basis area.

In short, it changes the user type of a technical RFC user in a production system from to by calling the function block.

On you will also find useful information about SAP basis.

The selection shall also be justified.
SAP Stuff
Zurück zum Seiteninhalt