The Basis system comprises a total of three layers (Figure 1):
SHARING OF THE SAP basis INTO A SINGLE APPLICATION AND INFRASTRUCTURE-RELATED LAYER
Every SAP system develops over many years. It grows and changes with the company. The more functions are mapped in it and the more data is stored, the greater the importance of and dependence on this central ERP system. There is no such thing as a standard SAP Basis solution. It is developed individually with reference to the company.
Different events can be used to change to the new or changed role concept. Among other things, the introduction of new technologies can be used to establish, for example, the characteristics of the SME or technology architect. But also fluctuation or new hires are suitable for the conversion and establishment of the new roles. In principle, it is recommended that the new rollers be introduced and implemented successively parallel to the existing operating model.
Buffer analysis
SAP Basis Operation manages the IT underlying the SAP system. In addition, the operation ensures the maintenance and availability of business processes. Various tools can be used for this purpose, which take over the maintenance, care, configuration and monitoring of the SAP system. Basic operation is the prerequisite for ensuring that the SAP system is fully operational and covers the business processes well.
I believe that in ten years, enterprises will be able to choose from a variety of platforms for multi-cloud automation. As a result, installation costs will no longer run into the tens of thousands and migrations and upgrades will no longer consume millions.
Tools such as "Shortcut for SAP Systems" complement missing functions in the SAP basis area.
If all miners accept the correctness of a completed block, they will all work the next one immediately.
For the authorisation requirement of a user, the transactions with user assignment already awarded should be determined accordingly, in order to be able to exclude them when selecting a suitable role.