OUTTASKING REGULAR TASKS THAT CANNOT BE AUTOMATED
What has changed in the past ten years and what can we expect in the next ten? How will they affect the requirements profile of SAP Basis experts and how can they adapt to them?
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.
On the one hand, staff clerks (or other personnel officials) should be able to carry out their important work. On the other hand, the protection of personal data of one's own employees is one of the most important tasks of the authorisation system. Any mistake in this area can cause the company's data protection officers to wring their hands over their heads. For this reason, tools are currently being developed to provide security and visibility in the HR permissions area. The basic idea is a clear overview that shows which data certain users in the SAP system can access. Based on this, automatic checks can be developed, which run in the background and regularly check whether critical gaps have been created by changes to the permissions in the HR area. The use of such a tool can create more security, especially in the HR authorisation environment. In addition, the possibility of the overview function is very pleasant and relieving for all involved. Read more This blog post is intended to show what is already possible in the field of Security Automation. The topic will accompany us more and more in the SAP area in the next few years. Therefore, it is recommended to start thinking about how your company is prepared for security automation. If you are interested in setting up and preparing a company outside the security area, I can recommend the book 'Consulting Y' by Ferdinando Piumelli (Managing Director of mindsquare GmbH). In this book, Mr. Piumelli describes his observations and experiences of digital transformation as a strategy consultant for leading DAX30 companies. In doing so, he is focusing on the near future, which, in the spirit of the digital revolution, will have a major impact on the world's large companies and economy.
SWEL Display event trace
A clearly structured and secure authorization management is very important to avoid errors and prevent access by unauthorized persons. These services are part of our authorization management:
The task of SAP Basis is to ensure trouble-free, interoperable and portable (mobile) operation of SAP systems in the company. Interoperable means that independent and heterogeneous IT systems can work together.
"Shortcut for SAP Systems" makes many tasks in the area of the SAP basis much easier.
If different jobs are strung together to form chains, further problems arise.
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.
SAP GUI for Windows, SAP GUI for Java, Web Dynpro for ABAP (WDA) and SAP GUI for HTML ("Web GUI") are widely used.