Determination of specific transactions with user assignment using SE16N
MANAGED SERVICES
Basically, an SAP Basis administrator is responsible for installing, configuring, managing, maintaining and servicing all technical components of an SAP system landscape. This includes activities such as application setup, monitoring, and troubleshooting.
All topics are relevant, which may also be of interest to a customer. Ideally, you get a balanced communication structure in the communication triangle between marketing, the target group and your own employees. Internal communication is an important aspect for the SAP basis. It is primarily a matter of passing on or communicating your own services, IT products and positioning to your employees. STEP 10: PLANNING The planning provides a translation of the previously agreed definitions into concrete measures. A description of the measure shall be provided. The measures can now be scheduled and included in a cost overview. Above all, it is important to plan realistically and to consider dependencies. This step, too, is of great interest to the SAP basis and is necessary to translate the previously agreed specifications into a concrete marketing concept of the SAP basis.
ASSESSMENT OF EXISTING CUSTOMER-SPECIFIC SOLUTIONS
If you now want to change the permission data, you will be asked for values for the appropriate organisation levels. First enter a tilde (~) and define the value later in the derived roles. Maintain the permissions you want and then generate the master role. Adding the organisational level to the master role Step 2: Define derived roles Create derived roles Assign the master role After you have created the master role, it is the derived roles that are in the process. To do this, re-enter a suitable role name via the PFCG. In our example, it is called "findepartment_d01". For a better overview, it is usually useful to name and number the derivatives after the master roles. You can also define the roles according to a different scheme. After you have created the role, you must then enter the master role in the Derive from Role field in the Description tab. Confirm the Auto Enquiries. Customise the Organisation Levels Now go to the "Menu" tab. There you can see that the data from the master role was automatically copied. Since the role has not yet been generated, the Permissions tab is currently highlighted in red. Therefore, call "Change Permissions Data". The first call should automatically open a dialogue to maintain the organisational levels, as they are still empty. If this is not the case, or if you would like to adjust the organisational levels again in a later case, you can also access them via the button Ordende (see screenshot). If everything worked well, you can now see that the permissions were also automatically taken from the master role. If you generate the role, the permission tab will also appear green. Congratulations, you have successfully created a derived role! Repeat step 2 with the additional derivatives to adjust the organisation levels accordingly.
Tools such as "Shortcut for SAP Systems" complement missing functions in the SAP basis area.
Some useful tips about SAP basis can be found on "www.sap-corner.de".
This is what the future of SAP looks like, and I look forward to an exciting journey.