SAP Basis Technical changes

Direkt zum Seiteninhalt
Technical changes
Schedule user adjustment as a job
But when it comes to the intricacies of large SAP environments, Ansible quickly reaches its limits. If you want to use Ansible to implement simple automations - starting and stopping SAP environments, for example - you have to put up with a lot of manual effort and complicated scripts.

An understandable and comprehensible strategy enables the SAP basis to derive it as easily as possible to practice and to the resulting requirements and activities. The main task of the SAP basis is to support new business models by implementing the strategy and to show how much technical and financial effort and benefit is generated. It is also the task of the SAP basis to identify the skills and resources necessary for them and to ensure their existence at an early stage.

SAP Basis refers to the administration of SAP system that includes activities like installation and configuration, load balancing, and performance of SAP applications running on Java stack and SAP ABAP. This includes the maintenance of different services related to database, operating system, application and web servers in SAP system landscape and stopping and starting the system. Here you can find some useful information about SAP Basis: www.sap-corner.de.
ABAP Objects
Whenever you find a red traffic light on the Roles tab in the user master in SU01 - or a yellow traffic light on the Users tab in PFCG, you can usually solve the problem with a simple user synchronization. The fact that such a user adjustment is necessary can have several reasons. Among others: after a role transport to / when assigning users to roles via PFCG after restricting the validity of roles to users when roles are assigned indirectly via organizational management. Users usually notice the problem of a user comparison that has not been carried out quite quickly: Authorizations are missing, although at first glance they are available in the assigned authorization roles. This is because a user is assigned the correct authorization role - but the profile associated with the role is not up to date.

Do you want to allow an employee access to exactly one view maintenance dialogue, but he should not be able to search for other care views in the SM30? This can be done easily with a parameter transaction. Learn how to create such a transaction step by step here. To create a parameter transaction, navigate to the SE93 first. Here you can create all types of transactions. The following dialogue will open: After pressing the "Create" button, a popup will open, on which you select the radio button "Transaction with parameters (parameter transaction)". In addition, type a short description as usual and confirm. The following dialogue will open: The transaction code must be specified here first. If you want to skip the entry dialogue when invoking the parameter transaction, and there is no way to open tables other than the one you want, make sure to select "Skip Entry Image". Furthermore, the GUI properties of the SM30 should be inherited so that the parameter transaction can be started with the same software. Configuration of the parameters In the lower part of the dialogue you will find a table ready for input. Here you can use the search help (F4).

For administrators, a useful product - "Shortcut for SAP Systems" - is available in the SAP basis area.

However, there are a few things to keep in mind: A process for granting special rights should be defined.

So much information... how can you keep it so that you can find it again when you need it? That's what Scribble Papers is great for.


Every operating system, such as Windows, provides an environment in which programs developed for that environment can run, such as MS Office.
Zurück zum Seiteninhalt