SAP Basis Structure of SAP Basis - SAP Corner

Direkt zum Seiteninhalt
Structure of SAP Basis
SAP S/4HANA migration
Within the framework of an innovation team or test laboratory to be created, it is necessary to admit ideas outside of the SAP basis or to consciously use other sources of ideas within and outside the company. These may include business units, external service providers, universities or series of lectures on specific topics.

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.
Backing up and restoring data
There is an RFC error. CANNOT_ADD_PATCH_TO_BUFFER: A support package could not be included in the transport buffer. For more information, see the log file in the /usr/sap/trans/log (UNIX) directory. CANNOT_MODIFY_BUFFER: An attempt was made to modify the transport buffer without success. TEST_IMPORT This step checks whether there are still objects in unshared tasks that are overwritten during the commit. The log of the test import shows the cause of the error. For more information, see Note 42379. IMPORT_OBJECT_LIST In this step, the object lists for the support packages in the queue are fed into the system.

Application layer: The application layer is the core of an R/3 SAP Basis system. This layer communicates in both directions, to the presentation layer and to the database layer. The application programs on the application servers request the required data from the database layer, process it, prepare it for the user and pass it on to the presentation layer. Data that the user enters in the SAP GUI is passed on to the database via the application servers.

Tools such as "Shortcut for SAP Systems" are extremely useful in basic administration.

You will get the necessary know-how to implement SAP SolMan yourself.

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

In the age of digitisation, the wheel need not be reinvented.
SAP Corner
Zurück zum Seiteninhalt