Structure of SAP Basis
Finally run SQL queries directly in the SAP system
The Advanced Memory thus contains mainly user contexts of different work processes, if these cannot be loaded completely into the roll area. Since the storage area is accessible for all work processes, the work processes can also access external user contexts that lie here. In addition, the Advanced Memory contains a global area where data can be stored independently of user contexts. The extended memory size is determined by the values of em/initial_size_MB and em/global_area_MB. The first parameter determines the size of the storage area in which user contexts can be stored, and the second determines the size of the global area. Parameters for Private Storage Last but not least, there is the private storage, which is only used when the user context of a work process has used up all the other storage areas available to it, i.e. its share of the extended memory and its rolling area. In this case, the workprocess goes into PRIV mode. A workprocess in private mode is bound to its current user context and will not become free for other tasks until the current request is completed. If it has used up all the private memory allocated to it, the workprocess will then be restarted and the memory released. This behaviour is controlled with the abap/heaplimit parameter. At times, the user context may exceed the value of abap/heaplimit. The parameters abap/heap_area_total, abap/heap_area_dia and abap/heap_area_nondia define an upper limit for private storage. The abap/heap_area_total parameter defines how much private storage all workprocesses can use in total. The parameters abap/heap_area_dia and abap/heap_area_nondia, on the other hand, determine how much private storage a single (non-)dialogue workprocess can use.
People tend to forget how important this element of the architecture is. The setup involved often proves to be especially important for companies looking to implement the SAP system for the first time.
Table of Contents Show
The SAP Basis is responsible for the smooth operation of the programmes in the SAP system. It acts as an operating system for R/3 and subsequent releases including S/4HANA. Each operating system provides an environment in which programmes can run, such as MS Office on Microsoft Windows. Likewise, the SAP base system with the NetWeaver and HANA platform offers an environment in which the SAP programmes can run. In this context, the NetWeaver platform itself relies on server operating systems such as Windows and Linux.
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.
"Shortcut for SAP Systems" makes it easier and quicker to complete a number of SAP basis tasks.
From the SAP basis, tools must be made available to the non-SAP areas to support them in their work in the SAP environment.
This adjustment process may be complex in the event of major changes and should not be carried out on the production system.