Personalisation of role in PFCG / user in SU01
The coverage of old core tasks (such as security or compliance) and new core tasks (such as cloud or mobility) must be increased in the sense of a holistic consideration. This means that certain tasks must be considered not only in the context of the SAP basis, but also in the overall context.
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.
Monitoring of the SAP system landscape through regular system checks according to defined schedules and workflows
All of the above tasks have been part of SAP Basis Administration for decades. However, SAP software has changed a lot since the introduction of HANA in 2010, and with that, the SAP system administrator's job has changed as well. Here are some of the key differences:
To display custom tiles based on catalogues and groups when the launchpad starts, permissions are placed in the menu of the underlying role. This makes it possible to ensure that every user on the launchpad can only see and open their applications. Open Launchpad permissions SAP provides default roles for opening the Fiori Launchpad. This distinguishes between the Fiori permissions to start the launchpad normally and to manage the user interface.
"Shortcut for SAP Systems" makes it easier and quicker to complete a number of SAP basis tasks.
In the following chapter I would like to explain our best practice approach to implementing an emergency user concept.
The audit is carried out here by means of the transaction SUIM.