SAP Basis Documentation and training - SAP Corner

Direkt zum Seiteninhalt
Documentation and training
Support for your SAP basis
A degree in computer science is usually required and is now almost obligatory. If you have completed training as a computer scientist, you can continue your education to become an SAP Basis Administrator and position yourself particularly well on the job market. Integrata CegosEine also offers training to become an SAP Basis Administrator.

In the result table USERTCODE are the transaction codes of the SAP users. Afterwards you simply have to output the complete list via "Object > Output complete list". Then save the list via "System > List > Save > Local file". The column Account contains the SAP user. This way you can see the used transactions grouped by SAP user.
Extension of the SAP system landscape
The prerequisite for employment is a relevant university degree (bachelor's degree, FH diploma) preferably in computer science, business informatics, mathematics or a scientific discipline as well as at least three years of practical experience. Ideally, you also have a completed scientific university education (master's degree, university diploma).

A secure SAP system does not only include a good role concept. It is also necessary to check whether a user should (still) have a specific role. Regular verification of role assignment is called recertification. In this blog post, I'd like to introduce you to the need for recertifications and our own tool, EasyReCert. The need for recertification - scenarios: Example 1: The "apprentice problem" Imagine the following scenario: A new employee (e.g. apprenticeship or trainee) will go through various departments as part of his or her training and will work on various projects. Of course, an SAP User will be made available to your employee right at the beginning, which is equipped with appropriate roles. As each project and department passes, the employee repeatedly needs new permissions to meet the requirements. After the employee has successfully completed his or her induction and is now in a permanent position, he or she still has permissions that are not necessary to perform his or her duties. This violates the principle of "last privilede" and represents a potential security risk for your company. Example 2: The change of department The change of department is one scenario that probably occurs in every company. If a change of department does not automatically involve a complete reallocation of roles and the employee simply takes his old permissions with him, critical combinations of permissions can occur very quickly. For example, an employee who has permissions in accounts payable and accounts receivable violates the SoD ("Segregation of Duties") principle and poses a potential security risk to your company. Recertification as part of a revision: The two examples above show that a regular review of role allocation identifies potential security risks for your business and can be addressed.

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

He also quickly got the password for various RFC users via the radio ("As long as passwords are only communicated by phone and never exchanged in writing, we are clean!").

SAP Basis is the foundation of any SAP system. You can find a lot of useful information about it on this page: www.sap-corner.de.


It takes a few minutes to complete the installation.
SAP Corner
Zurück zum Seiteninhalt