SAP Basis SAP PI(XI) - SAP Admin

Direkt zum Seiteninhalt
SAP PI(XI)
What are the tasks of an SAP administrator?
To facilitate communication within IT departments, it is necessary to identify clear communication channels and contact persons and also to use uniform tools for communication. It would also be possible to designate contact points (contact points) for upstream and downstream IT departments and external service providers and suppliers.

Today, most customers rely on an infrastructure abstraction layer, whether it's VMware or one of the cloud hypervisors. So base administrators need to know how to provision and manage systems in the cloud.

The website www.sap-corner.de offers many useful information about SAP basis.
To transport rejected transport jobs in the SAP system
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.

SAP will provide all SAP Notes in the SAP ONE Support Launchpad digitally signed. This is to increase the security when the updates are loaded. If you have unsigned SAP hints, there is a risk that the notice has been changed unnoticed and malicious code will be added to your SAP system when you install the notice. This poses a significant threat to the SAP system, which is why the digitally signed provision of the clues is an important improvement. However, to use digitally signed notes in your system, you will need to take a few steps to prepare them. If you install SAPCAR version 7.2 or later and have a user with the necessary permissions, all you have to do is insert the Note 2408073 into your system and do the manual pre- and post-processing. A digital signature technically ensures that any change can be detected at the notice and can be checked by the system to see if the present note, which is to be inserted into the system, is unchanged. Prerequisites to use digitally signed SAP hints To prepare your SAP system for digitally signed clues, you first have to meet some requirements: Digital signed SAP hints are provided as SAR files. The SAR files are unpacked with SAPCAR and checked for their digital signature. SAPCAR must be available on the Application Server in version 7.20 or higher. Therefore, it is strongly advised to update SAPCAR. If SAPCAR is not at least in version 7.20, the digital signature verification fails and the message cannot be unzipped. Installation of the digitally signed clue is then not possible. The implementing user also needs some permissions to perform the necessary manual pre- and post-processing of the note on the system: Authentication for the transaction SLG1 Read permission for the S_APPL_LOG permission to write and delete data from the application directory Upgrade the SAPCAR version on your system to version 7.20 or higher SAP basis version 700 or higher, for older versions the notice must be inserted manually If you have met these requirements, you can use the implementation of note 24080 Start 73. Implementation SAP Note number 2408073.

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

Further information on SAP Security in addition to the article can be found here.

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.


The legal requirements (e.g. EU guidelines) to secure your business processes and IT systems have not yet been implemented and the increasing networking with business partners presents new challenges to your security system.
Zurück zum Seiteninhalt