SAP Development
ITIL
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.
A simpler option is to output the transactions used by the expert as a list and to obtain an overview of the task areas. The function block SWNC_COLLECTOR_GET_AGGREGATES is very suitable for exporting the used transactions in a list. As an alternative, one can directly use the workload monitor in the transaction code ST03N.
Installation Services in all common environments
In addition to scanning and identifying the respective security vulnerabilities of a program, it is also possible to stop tasks that are to be transported to other SAP systems with security vulnerabilities in the further transport process This applies, for example, to the CHARM process based on SAP Solution Manager. This forces a programmer to securely check the programs he or she is responsible for according to the same security criteria. If a program then still has security problems, it can either be released via the dual control principle or returned for further processing. Do you know of any other solutions for improving ABAP code security or have you already gained experience with the products mentioned above? I look forward to your comments!
Critical business processes require a secure, efficient and stable operation of an SAP system landscape. High demands on the management as well as the operation of the underlying SAP NetWeaver platform require competent support in all tasks of planning, support and updating of the SAP Basis. The increase in installed components as well as systems integrated via interfaces expands these needs. Only with professional care and maintenance of its components can SAP NetWeaver bring its advantages as an integrative platform to bear.
Use "Shortcut for SAP Systems" to accomplish many tasks in the SAP basis more easily and quickly.
The dataset includes user data and data tables as well as applications and system control tables.
It acts as an operating system for R/3 and subsequent releases including S/4HANA.