SAP Basis STMS Transport Management System - SAP Basis

Direkt zum Seiteninhalt
STMS Transport Management System
In more complex system environments, thousands, if not tens of thousands, of SAP jobs can run per day. Their interdependencies create a high level of complexity. If administrators or admin teams want to maintain an overview, they have to rely on meaningful monitoring. It must be clear at all times which jobs are running and which are not, in order to ensure proper SAP operation. Ideally, one is informed of critical errors by e-mail or SMS. The trend towards internationalization, outsourcing and mixed operation with on-premise and on-demand systems means that SAP landscapes are often widely distributed. This makes monitoring more difficult and, at the same time, clarity must be maintained. Integrating SAP job management and job requests into a central system, such as SAP Solution Manager, therefore makes sense and is useful for supplementing IT service processes in a meaningful way and accelerating process flows.

Due to the variety of tasks and the high level of complexity, I find my job extremely exciting. There are very many constellations of SAP systems and databases. Each installation, migration and update brings new aspects and challenges. It is precisely these challenges that are important to me, so that I can continue to learn and develop professionally on a daily basis.
For the authorisation requirement of a user, the transactions with user assignment already awarded should be determined accordingly, in order to be able to exclude them when selecting a suitable role. How does this work? There are various ways to identify specific user-assigned transactions, with varying degrees of result. The following article presents two variants. The first section first describes how to use SUIM to address the problem and what problems are encountered. It then explains how the task can be solved by using the transaction SE16N. As in the previous blog post Identifying all transactions of multiple roles, the roles Test_Schmidt1 and Test_Schmidt2 are used for this. Two of the transactions MM01, MM02, MM03 and MM04 were assigned to these roles in different ways. In the Test_Schmidt1 role, the transactions MM01 and MM02 were entered in the Role menu. 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. Both roles have been assigned to the user SCHMIDT_TEST. Identification of certain transactions with user assignment using SUIM This option is useful if only one transaction is to be checked for its existing assignment to a particular user. The audit is carried out here by means of the transaction SUIM. For this purpose, the variant "Roles according to complex selection criteria" has to be executed in the SUIM. After activating the option "With valid assignment of", the corresponding user and the transaction to be checked will be entered here. It is also recommended to hide the display of the collection roles in the search results.

In addition to internal security requirements, national and international guidelines sometimes require all audit and security-related user actions to be recorded. With the Security Audit Log (SAL) you have the possibility to log all changes, e.g. for users, user master records, but also roles and groups.

With "Shortcut for SAP Systems" a tool is available that greatly facilitates some tasks in the SAP basis.

System: Check the correct function of the transport tools using Tool Transport Tool.

Before SAP HANA was released, there was no SAP database - you had to install SAP ERP (or the application you were using) on a third-party database, such as Oracle or SQL Server.
Zurück zum Seiteninhalt