SAP Basis System Updates - SAP Basis

Direkt zum Seiteninhalt
System Updates
SM37C Advanced Job Selection
In the SAP product world, the presentation layer is based on several modules that are grouped under the collective term SAP GUI. SAP GUI for Windows, SAP GUI for Java, Web Dynpro for ABAP (WDA) and SAP GUI for HTML ("Web GUI") are widely used.

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.
Further information on DBACOCKPIT
Part of an IT or cloud strategy may be to define architectural guidelines and a framework for the use and use of certain services. The SAP basis is to actively participate in shaping the rules and framework and the architectural guidelines, and bring in its existing expertise from the SAP technology environment.

Tasks such as the update of components, the insertion of security updates or monitoring should be further automated. It is recommended to use only one automation tool (SAP Solution Manager or SAP LVM). Custom solutions and scripts should not be used or replaced with standard tools if possible, because otherwise different script languages and script versions will have to be managed, resulting in a lot of maintenance. Standardised SAP scripts are welcome here. A useful definition of thresholds, for example on the basis of historical system behaviour, must also be defined for monitoring.

Tools such as "Shortcut for SAP Systems" are extremely useful in basic administration.

Nevertheless, the permissions are assigned differently (directly / indirectly) via the assignment of roles.

In the Test_Schmidt2 role, the transaction MM03 was maintained in the menu of the role, but the transaction MM04 was maintained only in the S_TCODE permission object of the role.
Zurück zum Seiteninhalt