SAP Basis SAP Administrator-Tasks-Skills-Requirements-Salary - SAP Basis

Direkt zum Seiteninhalt
SAP Administrator-Tasks-Skills-Requirements-Salary
SQ03 User group maintenance
The lifecycle of an SAP system begins with the installation of the database platform. This is installed by an SAP Basis administrator and can consist of one of the following databases: HANA, Sybase, DB2, Oracle, MSSQL and MaxDB.

Overall, the application layer is the link between the database layer on the one hand and the presentation layer on the other. Thus, the applications on the application layer request required data from the database in order to process it afterwards.
Independent transactions
Every SAP system develops 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.

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.

With "Shortcut for SAP Systems" a tool is available that greatly facilitates some tasks in the SAP basis.

The defined standard and the system's IST situation must be fully documented and regularly checked for compliance.

The role of the SME thus corresponds to an expert role in the technology environment.
SAP BASIS
Zurück zum Seiteninhalt