SUM - the Software Update Manager, the relatively new tool for "remote control" of the known update transactions from outside the system, for ABAP and JAVA
SXDA Data Transfer Workbench
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.
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 application logs, identify potential errors and even suggest fixes, making it much easier to get to the root of the problem.
Support of SAP modules
It is of great importance to keep the knowledge of SAP Basis experts in the company transparent. One possibility is of course to "look over the shoulder" or to ask the expert directly. However, this is very time-consuming and puts a strain on the expert himself.
If table logging is active in your system, you can specify which tables are to be logged in transaction SE13. For an active logging it is necessary to set the flag "Log data changes".
The "Shortcut for SAP Systems" tool is ideal for doing many tasks in the SAP basis more easily and quickly.
It has a basic understanding of the infrastructure and is well connected within the IT departments.
Since they often also work in international companies, it is an advantage if they have a very good command of written and spoken English.