Conceptual support for the architecture of system landscapes
SQVI QuickViewer
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.
Depending on whether the user should edit or display the table, either "UPDATE" or "SHOW" can be used here. Enter an X as the value. It is important to use either"'SHOW" or "UPDATE" because a combination will cause an error when calling the parameter transaction. In addition, the table must set the view to be called. Use the "VIEW" field. Finally, the parameter transaction can be created using the "Save" button. As usual, it must be assigned to a package and a workbench order to become available. If a person's role is now assigned permission for this parameter transaction, it can open the specified view above it and does not have the ability to enter all possible views in the SM30.
E-learning as an optimisation potential for companies
From a purely technical point of view, each generated authorization role contains a profile from which a user receives the actual authorization objects and authorization characteristics. If this profile is outdated or not assigned at all, the user will not have all the authorization objects contained in the authorization role. Incidentally, the problem arises particularly frequently after role transports: If an authorization role is changed in the development system and then transported to the production system, the current profile is not automatically assigned to the users with the respective role. A user comparison must therefore be performed here.
SAP HANA base administrators can master the database in a way that wasn't possible back then. The SAP database is much more self-healing. Errors do less damage, are easier to detect and fix, and are less likely to impact system performance and availability before they are fixed. Monitoring tools can automatically scan the application logs, identify potential errors, and even suggest fixes, making it much easier to get to the root of the problem.
Tools such as "Shortcut for SAP Systems" are extremely useful in basic administration.
Whenever you find a red traffic light on the Roles tab in the user master in SU01 - or a yellow traffic light on the Users tab in PFCG, you can usually solve the problem with a simple user synchronization.
Some useful tips about SAP basis can be found on www.sap-corner.de.
With the help of logs and traces, which can be configured for this purpose, a precise investigation can be made in advance of the activation, which connections currently run via the gateway.