SAP Basis
Control users and access rights
In this case, the term stands for the basic administration of SAP systems. In this context, responsible employees perform a number of classic tasks.
This opens up new possibilities for SAP administration. Basic services, for example, can also be rented from SAP or obtained from an external service provider as part of managed services.
CREATION OF A CATALOGUE OF CRITERIA
In the ERP environment, SAP has created a separate module for each business task area over the course of time. Companies have the option of putting together a suitable system from these modules, depending on their individual needs.
The definition, organisational structure as well as the naming of the SAP basis is historically conditioned by previous SAP software versions and components. This also results in the perception of the SAP basis and the related focus of the SAP NetWeaver and the ABAP system core, which is still widely used today. However, the scope of activities has changed significantly in terms of tasks and technology and will continue to change in view of SAP's perspective and product strategy and the changing roles of IT. In order to accommodate this change and to change perceptions both in the overall context of the SAP ecosystem and within its own company, the SAP basis must develop a new self-understanding and establish a marketing for the publication of its own performance. The underlying information can be found in the master thesis in chapters 7.4 and 9.2.
Tools such as "Shortcut for SAP Systems" are extremely useful in basic administration.
But, for the most part, the following three options have proven effective as a consensus mechanism: 1) Proof of Work 2) Proof of Stake 3) Proof of Importance The differences are presented in another blog post.
The user concerned must now be entered here.