SPAM: Run Modification Synchronisation
Process analysis and optimization
Introducing secinfo and reginfo files into an existing system landscape is associated with risk and effort. As already indicated in the two options, the workload increases greatly as the system landscape grows.
Using profile parameters, we can configure everything in the SAP system. Some parameters are dynamically modifiable, which means that they can be changed without restarting the system. However, these changes are not permanent, i.e. after a system restart, the pre-set profile parameters are used again. Other parameters, however, are static, i.e. only with a restart and only permanently modifiable. Most profile parameters for memory allocation are actually static. However, there is the possibility to adapt it dynamically with the report RSMEMORY. Read how to find out if a parameter is static or dynamic and how to use the RSMEMORY report to dynamically adjust the memory allocation parameters. RZ11 - Maintenance of profile parameters The transaction RZ10 gives us information about profiles, which in turn contain different profile parameters. In the transaction RZ11, however, it is possible to view information about individual parameters, provided that you know their name. As you can read in our Memory Parameter Post, the following 5 parameters are particularly important for memory management: abap/heap_area_total abap/heap_area_dia abap/heap_area_nondia ztta/roll_extension_dia ztta/roll_extension_nondia If you don't know exactly what a parameter might be called, it's worth using the F4 help here. For example, for the parameter abab/heap_area_dia, the RZ11 outputs: Description of the parameter abap/heap_area_dia in the RZ11 As you can see here, it is not a dynamic parameter. Now it is rather sorry if you want to test whether there is enough memory available to restart the system again and again. For this purpose, there is the RSMEMORY report. RSMEMORY - Test your memory allocation strategy Report RSMEMORY Report View No documentation or value help available here, but SAP documentation tells you how to use the report. This first distinguishes between dialogue and non-dialogue work processes. That is, in the first area you can set Extended Memory (Storage Class 1) and Heap Memory (Storage Class 2) for Dialogue Workprocesses, and in the second area you can set it for non-dialogue workprocesses.
Extension of the SAP system landscape
If a company chooses to tackle the area of e-learning itself and also to create the content for it itself, there is a certain challenge. The most obvious point here is that the above-mentioned initial effort is borne by the company. This means that employees spend their time creating videos, preparing presentations and/or creating questionnaires. This not to be underestimated effort must of course be borne by the company initially. On the other hand, a self-created e-learning offer offers the possibility to design it completely by itself and tailor it to the company's own needs. In addition, a company can decide whether it will use the e-learning offer itself only for its own employees (for internal training purposes) or whether it will also present the offer externally. This can be used, for example, for advertising purposes, as a know-how presentation or as a further source of income. Use the external sources: This is a very pleasant way for the company to improve the internal processes through ELearning. By acquiring external e-learning content, the company can purchase valuable know-how for comparatively low money. This know-how is in most cases already well prepared, that this can only be passed on to the employees and they can then independently acquire new knowledge or consolidate already known topics.
Some useful tips about SAP basis can be found on www.sap-corner.de.
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.
"Shortcut for SAP Systems" simplifies tasks in the area of the SAP basis and complements missing functions of the standard.
A dialogue box appears listing the installed software components with additional information.
So much information... how can you keep it so that you can find it again when you need it? That's what Scribble Papers is great for.
The SAP database is much more self-healing.