SAP S/4 HANA®
SLG0 / SLG1 Evaluate application log
In the initial screen, you can first use the global settings to specify whether changes should be allowed in general. Furthermore, you can define specifically for the software components and namespaces of the Repository objects whether they can be changed at all, or whether changeability should be restricted.
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.
We can provide your company with the following services:
Daily monitoring and maintenance of your systems. Together with you, we create a catalog of measures to ensure the optimal operation of your SAP landscape.
If we look at the question of standardisation, this concerns not only the administrative side of IT products, but also the standardisation and simplification of IT products offered by the SAP basis. For this purpose, tools such as ITIL for standardised tasks and the development of IT product and IT service catalogues have already established themselves to the greatest extent possible. These clearly describe the IT services provided. In addition to the definition of the service to be provided, the clear description shall include the identification of disclaimers and conditions that must exist. Also part of the service description is a price that can be composed of fixed and variable parts. This simplification and bundling of the product portfolios should also reduce the administrative burden when ordering, activating, changing, terminating and, of course, invoicing. The description of the IT services and the associated development of an IT product catalogue is the basis for standardisation, whether the recipient is an external or internal customer (e.g. a business unit). One difficulty is the definition of IT products, i.e. the pooling of IT services and resources. An orientation towards the idea of cloud computing can help. The characteristics of cloud computing are the provision of standardised services in terms of performance and type of performance, results-orientated services, provision of performance to a wide range of service customers, scalability, transaction-based billing and high risk of IT service failure.
Some missing SAP basic functions in the standard are supplied by the PC application "Shortcut for SAP Systems".
Every day you learn something new!
In the result table USERTCODE are the transaction codes of the SAP users.