SAP Basis Proactive and continuous optimization of system availability and performance - SAP Stuff

Direkt zum Seiteninhalt
Proactive and continuous optimization of system availability and performance
RFC Security, Science-Fiction and Theatre
The lifecycle of an SAP system begins with the installation of the database platform. This is installed by an SAP Basis administrator and can consist of one of the following databases: HANA, Sybase, DB2, Oracle, MSSQL and MaxDB.

Reachable at any time: Your competent contact person is available at all times. If you operate SAP Basis Support in-house, personnel bottlenecks may occur. If your SAP employees are absent due to illness or vacation, there may be no equivalent replacement available.
Agents
Always the latest version: Your system will always be up to date and you will have access to the latest versions. Patches are performed by the external SAP Basis team.

In the area of SAP Basic Administration there are many tasks that occur at long but irregular intervals, such as adjusting the system modifiability. As a result, the know-how is often lacking and it is quickly taken to the next search engine, where long and partially incomplete forum entries make finding the right approach even more difficult. For this reason, I will regularly record recurring tasks from the SAP basis Administration for you in simple tutorials. This blog post will start with the topic system modifiability and client control. If you want to jump directly to a step-by-step guide, just scroll down to the bottom, where I summarised everything once. System Modifiability - What Is It? The system modifiability allows you to set which objects of the repository and the client-independent customisation are modifiable or not. Repository objects can also be customised even further, with respect to the software component and the namespace. You can choose whether an object should be modifiable, restricted, or non-modifiable. In this context, restrictively modifiable means that repository objects can only be created as non-originals (small note: for packages the setting "restricted modifiable" and "modifiable" is identical in the function). Let us now turn to the direct approach to the changeover to system variability. Change system modifiability As a preparation, you should clarify how long the modifiability should take place in your system. I have learned from my clients that it is often desired to set the system to "changeable" for certain tasks from the specialist areas only temporarily. If you have organised this, call the transaction SE06 in the 000 client and click on the button "System Modification". If you do not have permissions for this transaction, you can try either the transaction SE03 —> System Modifiability or the transaction SE09 -> Jump -> Transport Organiser Tools -> System Modifiability (under "Administration"). The following screenshot shows the way across the SE03: Here you can change the desired namespaces and software components depending on your request.

For administrators, a useful product - "Shortcut for SAP Systems" - is available in the SAP basis area.

You can choose between the matchup types Profile Matchup, Matchup of Indirect Assignments from Composite Roles, and Matchup HR Organizational Management.

On www.sap-corner.de you will also find useful information about SAP basis.

Constant further development and growing complexity are placing ever-increasing demands on the SAP infrastructure in terms of performance and feasibility.
SAP Stuff
Zurück zum Seiteninhalt