SAP Basis Show table of contents - SAP Basis

Direkt zum Seiteninhalt
Show table of contents
SU25 Profile generator: upgrade and initial installation
Reduce resources: depending on the agreement of the contract, you can ask for the service resources only when needed. This will save you some costs.

The positioning depends strongly on the previously identified target groups and must be justified accordingly. Positioning is extremely important for the SAP basis. It is primarily a matter of positioning within the IT organisation and defining or positioning the other IT departments that can be considered as competitors in the context of this step. STEP 6: OWN EMPLOYEES This step will identify the necessary skills and training of their own employees necessary to fulfil the objectives and provide the service. The necessary skills and roles for the SAP basis are explained in detail in the recommendation Skills & Roles.
Support in setting up connectors and interfaces
First you have to create an area menu in the area menu maintenance with the transaction code SE43 or SE43N. Then add the created menu to the SAP standard menu S000.

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.

"Shortcut for SAP Systems" makes it easier and quicker to complete a number of SAP basis tasks.

CANNOT_CHECK_LOCKS: An error occurred while detecting the locks of an object in the queue.

Therefore, SAP Basis is an important core of any SAP infrastructure and is required in both predecessor versions such as R/3 and current versions such as S/4HANA 2021.
SAP BASIS
Zurück zum Seiteninhalt