Figure 2: The Open Innovation Model
Virtualization of your SAP system landscape
In order to ensure the stability of the systems and to reduce the risk through proprietary developments, release and patch management must be implemented. Standardised procedures can help to introduce proprietary developments, such as test strategies or service level agreements (SLAs). It is also important to align the productivity setting of customer applications with the maintenance windows and RTO (Recovery-Time-Objective).
Only one transaction code can be entered here, otherwise a single role would always be searched, which includes all transactions searched for and is assigned to the respective user. However, since the transactions can also be assigned to the user via different roles, this would not be useful. If you use the above Input variants are also only considered transactions that have been maintained in the role menu. If it is not certain whether the transaction was entered in the menu or in the S_TCODE privilege object of the role, up to four transactions can also be checked by searching through the S_TCODE permission object. Important is the attention and appropriate use of the AND/OR relationship. After the query is executed, the roles that contain the requested transaction and are associated with the user are now displayed. If you use the search through the S_TCODE permission object, the following result page appears. When looking at the result, in addition to limiting the number of transactions that can be entered, another drawback of this variant becomes apparent: Although both associated roles are displayed, at first glance it is not possible to see which transaction is contained in which role. To do this, the roles would have to be considered individually. If more transactions with user assignment are to be identified at the same time and the role assignment is to be seen directly, the use of the transaction SE16N is recommended.
System updates
A user name without a restricted character set can be a security risk. Therefore, it is advisable that you restrict the character set of the user ID. In this article you will learn where the dangers lie if you do not limit the user ID. I also explain how to eliminate this security risk.
The identification of critical SAP permissions for the use of an SAP system must therefore be carried out in any case. In addition to permissions, you can also identify critical profiles and roles that are already in the delivery state.
With "Shortcut for SAP Systems" a tool is available that greatly facilitates some tasks in the SAP basis.
In this blog post, I'd like to introduce you to the need for recertifications and our own tool, EasyReCert.
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.
This is technically repackaged into the Q-System in a new order and transported to the quality system.