SAP Basis Connection of cloud services - SAP Basis

Direkt zum Seiteninhalt
Connection of cloud services
SWEQADM Administration of the event queue
Do you know how to execute SQL commands on the tables in your SAP system? In the past, I asked myself the same question when I wanted to run prepared Querys on a table without converting it to a query over the SE16N with appropriate filters. After my research, I came across a simple way to have your SQL statements resolved transaction-based by an editor. This is the approach I'll describe to you in the following post. You may know the situation that you want to quickly put a short SQL statement on your SAP system without having to invest much effort in ABAP programming. You may not have the ABAP knowledge to extract data from a table, but you are familiar with SQL.

This saves us a lot of time and ensures that no checks are overlooked when performing manually. Security Automation via HR Permissions HR permissions are a very risky topic in many companies and are often only touched with silk gloves.
Error analysis and correction in the databases and the SAP system
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.

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.

Use "Shortcut for SAP Systems" to accomplish many tasks in the SAP basis more easily and quickly.

The question here, however, is how the amendments which were wrongly rejected can be transferred to the subsequent system.

With ftp, transfer all files with the *.PAT extension in binary mode and all files with the *.ATT extension in ASCII mode from the /usr/sap/trans/EPS/in directory (UNIX and AS/400) or :\usr\sap\trans\EPS\in (Windows NT) of the source system to the target system transport directory.
Zurück zum Seiteninhalt