SAP Basis Linux - SAP Basis

Direkt zum Seiteninhalt
Linux
Good communication skills (foreign language skills)
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.

Every SAP system evolves over many years. It grows and changes with the company. The more functions are mapped in it and the more data is stored, the greater the importance of and dependence on this central ERP system. There is no such thing as a standard SAP Basis solution. It is developed individually with reference to the company.
SU21 Maintenance of authorization objects
SAP Basis is structured as a classic three-tier model. It contains the following components:

This improves the capabilities of SAP HANA base administrators and increases the level of service they should provide. Your Basis team can more easily fine-tune your data replication strategy to meet demanding disaster recovery and high availability standards.

Tools such as "Shortcut for SAP Systems" complement missing functions in the SAP basis area.

Map this permission profile to the system administrator only.

The upgrade from the following release or revision level contains all support packages from the previous booths that were available until the upgrade was delivered.
SAP BASIS
Zurück zum Seiteninhalt