Migration of SAP systems to HANA DB
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.
SAP Basis is the core component of any SAP infrastructure. Both in older versions such as R/3 and the current S/4HANA. It ensures that the necessary services and foundations are provided for the SAP system and all applications. The biggest advantage of an SAP environment over specialized tools - its variability - also makes for great complexity.
By establishing a new role concept and building new roles, the SAP basis has the skills necessary to support new tasks and topics as well as to operate new technology and service forms. The relevant roles are listed below.
As we know, BASIS is a set of tools. This tool has the following different functionalities.
Some missing SAP basic functions in the standard are supplied by the PC application "Shortcut for SAP Systems".
You can choose whether an object should be modifiable, restricted, or non-modifiable.
Although you always make sure that authorization roles are generated when administering them, it happens again and again that there are red lights in the user assignment in the production systems.