SAP Basis Installation/upgrade of SAP systems based on HANA Platform - SAP Corner

Direkt zum Seiteninhalt
Installation/upgrade of SAP systems based on HANA Platform
CLOUD SOLUTION
In addition to internal security requirements, national and international guidelines sometimes require all audit and security-related user actions to be recorded. With the Security Audit Log (SAL) you have the possibility to log all changes, e.g. for users, user master records, but also roles and groups.

Permissions beyond the daily task spectrum are granted only for limited periods and under control. The activities with the emergency user are logged in a revision-proof manner. Do you already have an emergency user concept in use or would like to introduce one? I'm happy if you share your experience with me! You can leave me a comment or contact me by e-mail.
OPERATOR (OP)
Basis administrators often have basic ABAP knowledge, for example, and ABAP developers know the basics of SAP Basis. Nevertheless, the two fields of activity are usually organizationally separated in the company.

The support packages were successfully fed into a system (test or development system). You performed the modification synchronisation. Procedure Load the support packages into the next system (quality or production system). You must distinguish between the following cases: Their systems have a common transport directory: Release Level 3.x: If the *.ATT files are not present, run RSEPSDOL in the source system and then RSEPSUPL in the target system. If the *.ATT files are present, run only RSEPSUPL in the target system. Release level 4.x: Select SPAM Support Package Upload in the target system. Your systems do not have a common transport directory: Release Level 3.x: Run RSEPSDOL in the source system to create the *.ATT files if they do not already exist. With ftp, transfer all files with the *.PAT extension in binary mode and all files with the *.ATT extension in ASCII mode from the /usr/sap/trans/EPS/in directory (UNIX and AS/400) or :\usr\sap\trans\EPS\in (Windows NT) of the source system to the target system transport directory. Run RSEPSUPL in the target system. Release level 4.x: With ftp in binary mode, transfer all files with the *.PAT extension from the source system's /usr/sap/trans/EPS/in (UNIX and AS/400) or :\usr\sap\trans\EPS\in (Windows NT) directory to the target system's transport directory. Select SPAM Support Package Upload in the target system. Play the Support Packages as usual. Import the Modification Balance Transport. Steps of the SPAM The SAP Patch Manager informs you about the step in progress in the status bar. If you want to know what steps are being performed for which scenario, run RSSPAM10.

Some missing SAP basic functions in the standard are supplied by the PC application "Shortcut for SAP Systems".

SPAM updates are an exception; certain settings are specified for these.

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.


One of these logs is shown in the next screenshot: These logs can also be viewed in the system.
SAP Corner
Zurück zum Seiteninhalt