SAP Basis Data cleansing - SAP Basis

Direkt zum Seiteninhalt
Data cleansing
Implementation
All the roles that contain the string "ADM" are considered critical, as they usually refer to administrative roles. When identifying critical SAP permissions, profiles and roles, it should be noted that SAP does propose a concept for names, but this is not always taken into account by applications or its own developments.

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.
ABAP Objects
Due to the variety of tasks and the high 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.

This access method depends solely on the rights assigned to the user. System users: Users of this user group are comparable to SAP*. They act as administrator in the system. Therefore, they should be deactivated / set to inactive as soon as possible, as soon as the system operation is ensured. You should still be aware of the SAP ERP environment to address this security risk. In a HANA system, there are privileges instead of permissions. The difference is first of all in terms of terminology. Nevertheless, the permissions are assigned differently (directly / indirectly) via the assignment of roles. These are thus accumulations of privileges. As in older SAP systems, system users must be disabled and certain roles that already exist must be restricted. Compared to an SAP ERP system, small apps are allowed instead of large applications. In this case, attention should be paid to an individual authorisation. It should be a matter of course for users to have implemented secure password rules. Settings Securing the system also means securing the underlying infrastructure. Everything from the network to the host's operating system must be secured. When looking at the system landscape, it is striking that the new technology brings many connections that need to be secured. The SAP Gateway, which is responsible for the connection between backend and frontend, is also a security risk and must be considered. All security settings of existing and future components must be validated to HANA compatibility. Secure communication of connections is obtained when you restrict access where possible. Encryption of the data of a HANA system is disabled by default. Be sure to encrypt sensitive data anyway. Especially data that is archived. If an attack is made on your system, you should be able to run forensic analysis, so you should enable the audit log. Moreover, few users should have access to it.

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

These specify how the outgoing data should be processed.

The possibilities and limits are examined and corresponding specifications and tools are developed in order to use the technologies profitably.
SAP BASIS
Zurück zum Seiteninhalt