SAP Basis Application of support patches, upgrades and installation of add-ons - SAP Stuff

Direkt zum Seiteninhalt
Application of support patches, upgrades and installation of add-ons
SAP SM37: How to monitor a background job?
Especially after security incidents it may be necessary to find out which (technical) users have logged in at which time. The USR02 table provides a first entry point. In the TRDAT column you can find the last login date for the user you want. However, a history of previous applications is not found in this table. In such cases, the Security Auditlog or SAL helps. Preparation In order to access the desired data, it must also have been saved previously. In the Security Auditlog, you can use various filters to determine which users are logged on which client and which information. The Security Auditlog stores, depending on configuration, logins, RFC calls, and other actions for specific users. You can make these settings in the SM19 transaction. Note: Logging user activity must be aware of the users concerned! Configure the SAL only for technical users or in consultation with users / works council / etc. It can be seen there among other things when the SAL was activated and last edited (1). You can also select the various filters (2), activate the filters individually (3), specify clients and users (4) and specify which activities are logged (5). Static configuration in the SM19 Under the Dynamic Configuration you can also see if SAL is currently active for the system. Determine the status of the SAL Evaluation of the SAL If the Security Audit Log is active, switch to the SM20 evaluation of the Security Audit Log. Select the desired user and client and the appropriate time window. The option Dialogues login is sufficient for the login. Then, restart the AuditLog analysis. Start evaluation You will get an overview of the user's login to the selected client of the system.

You can view them using the RSPUTPRT report or the AL11 transaction. AUTO_MOD_SPAU This step checks whether modifications can be adjusted automatically. RUN_SPAU_? This step prompts you to customise your modifications to Repository objects by calling the transaction SPAU. EPILOGUE In this step the insertion is completed. Checks whether the queue is fully processed. In this case, transport buffer entries should no longer exist for the Queue. There are the following reasons that may lead to the termination of this step: TP_INTERFACE_FAILURE: Unable to call tp interface. TP_FAILURE: The tp programme could not be run. For more information, see the SLOG or ALOG log file.
Beta test: secinfo and reginfo Generator for SAP RFC Gateway
Job scheduling: your system needs to run various automatic background jobs that consume resources. Your administrator must carefully schedule these tasks when user demand is low so they don't impact performance.

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


SAP Basis refers to the administration of SAP system that includes activities like installation and configuration, load balancing, and performance of SAP applications running on Java stack and SAP ABAP. This includes the maintenance of different services related to database, operating system, application and web servers in SAP system landscape and stopping and starting the system. Here you can find some useful information about SAP Basis: "www.sap-corner.de".

If the Queue is already fully defined, it is only displayed; they no longer have the ability to change the selection.

SAP Stuff
Zurück zum Seiteninhalt