Objectives of the training SAP HANA - Installation and Administration:
Call Inheritance Hierarchy
Due to the technology diversity, including in the SAP product portfolio, the support by a single silo unit SAP basis is almost impossible. Likewise, there are many activities that are located for historical reasons in the SAP basis and in parallel in the non-SAP area. In this respect, the separation between SAP and Non-SAP must be examined and, if possible, eliminated by standardisation, integration and centralisation. For example, the issue of output management can be set up in a team that has knowledge in the SAP printing area as well as in the non-SAP printing area and has contact points in the SAP basis. From the SAP basis, tools must be made available to the non-SAP areas to support them in their work in the SAP environment.
Hosting environments and third-party offerings have also contributed to these improvements. Public cloud environments such as Azure and AWS provide a layer of abstraction that eliminates the difficult task of maintaining hardware that was required with SAP on-premises.
Tools for SAP experts
Have you ever wondered what there is actually a tab personalisation for role maintenance in the PFCG or for user data maintenance in the SU01? I will answer this question for you in this blog post. What do we need the Personalisation tab for? This tab gives you access to the central repository for personalisation data. The purpose of this repository is to create a storage facility for user- and role-specific data without the need to create additional database tables. This data should then be taken into account in all manipulations of users and roles. The functionality initially includes a generic repository for user- and role-specific data and centralised access to that data by user and role maintenance. It also provides the ability to connect existing tables with user-specific data to the central access via a defined interface. To store personalisation data in the central repository, a key must be assigned to the data: This is done via the registration transaction PERSREG. The personalisation data that you create is stored in the generic drop table. Access to it is provided by the class methods of the CL_PERS_ADMIN class. Different levels of personalisation The data can be stored either to the user, to roles or to the system. A user can then read all data assigned to him (via role or his own settings) at once.
Hosting environments and third-party offerings have also contributed to these improvements. Public cloud environments such as Azure and AWS provide a layer of abstraction that eliminates the difficult task of maintaining the hardware that was required with SAP on-premises.
Some missing SAP basic functions in the standard are supplied by the PC application "Shortcut for SAP Systems".
If you want to get more information about SAP basis, visit the website www.sap-corner.de.
In the area of SAP Basis Operations, we handle all technical tasks for our customers that arise during the installation, operation and maintenance of SAP systems.
The transactions are stored in blocks of the chain.