Extension of the SAP system landscape
Training - Administration SAP HANA
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.
Among other things, it determines which application server a user logs on to in order to distribute the workload (load balancing). The message server also enables the individual application servers to communicate with each other.
SLICENSE SAP License Management
Within this step, a pricing strategy is chosen. The strategy chosen must be based on the value for money. The selection shall also be justified. The price of the service will continue to be determined, as will formal decisions on clearing models and discounts. This step is less important for the SAP basis. While it is necessary to set a price for the IT products to be defined in terms of appreciation and offsetting, it does not require an elaborate pricing system. STEP 8: MARKET COMMUNICATION The step of market communication describes the way in which the respective service is advertised and how it is to be communicated with customers in this regard. It's about the communication tools that are planned, which describe the place of communication, the communication tools that describe what to advertise, and the content. These are usually derived from the target group to be applied for. For the SAP basis, the content is an essential feature of the market communication. That is, depending on the target group, information must be created and communicated. STEP 9: INTERNAL COMMUNICATION Internal communication describes how the above-mentioned aspects can also be successfully communicated internally, i.e. in the direction of one's employees.
It is therefore not unusual for the authorisation allocations to be regularly reviewed in the course of a revision or by external auditors. This is a very laborious process with SAPS standard tools. In this scenario, an authorisation administrator would first have to manually assign each employee to a specific manager and determine their roles. After that, these roles should be exported from the system (for example, to an Excel file) and then submitted to the supervisor so that he can decide whether the role assignment is appropriate or not.
"Shortcut for SAP Systems" simplifies tasks in the area of the SAP basis and complements missing functions of the standard.
The two main tasks of this function are: Deleting profiles including user assignments if no matching role exists.
To enable your developers to perform the modification synchronisation, create an order in the Transport Organiser [Extern] and under this task for the developers.