SAP Basis SWU9 Trace of the BC-BMT-WFM component

Direkt zum Seiteninhalt
SWU9 Trace of the BC-BMT-WFM component
Administration
Following the recommendation of dividing the SAP basis into an application-orientated and infrastructure-related SAP basis [A4], Figure 3 shows a possible presentation form. The SAP-Basis interface function is structured into a SAP basis, which is close to the application and is responsible for coordination and communication with vertical and higher IT specialist and business areas, and a SAP basis close to the infrastructure. The infrastructure-related SAP basis in turn serves as the link between the application-orientated SAP basis and the infrastructure levels. Subject Matter Experts will perform the link task again. In the application-orientated SAP basis, in turn, technology architects are more likely to be placed. The innovation activity or innovation team aspect of the SAP basis is placed at the level of the SAP basis, which is close to the application, because the existing capabilities allow it to assume a leading, also coordinating role and acquire expertise both by adding the SAP basis near the infrastructure and the downstream IT departments. Figure 3: SAP basis as a cross-sectional function SAP basis (near application) SAP basis (near infrastructure) SAP basis (innovation / test laboratory) Application development Databases Virtualisation ....

The CodeProfiler prevents poor-quality code or programs with security vulnerabilities from entering a productive SAP system landscape in the first place. It is therefore important to use the CodeProfiler throughout the entire lifecycle of a software. Already during programming, the CodeProfiler helps the developer to identify and correct errors and vulnerabilities in the SAP landscape. The CodeProfiler automatically ensures that only "clean" code is transported to the next level (development system -> test system -> quality assurance system -> production system). The CodeProfiler can also be used for regular review cycles.
Installing, maintaining and servicing other software that is not an SAP system but also provides important functions such as SAP Router, SAP Cloud Connector, TREX, SAP ETD and many more
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.

In principle, exceptionally good knowledge of computer science is essential. In addition, SAP administrators must of course be particularly well versed in this specialist area and be able to deal confidently with all issues relating to SAP solutions. Since they often also work in international companies, it is an advantage if they have a very good command of written and spoken English.

Tools such as "Shortcut for SAP Systems" are extremely useful in basic administration.

Understanding the structure and functioning of the system is especially important for IT administration. It is not for nothing that "SAP Basis Administrator" is a separate professional field. On the page www.sap-corner.de you will find useful information on this topic.

On the one hand, staff clerks (or other personnel officials) should be able to carry out their important work.

A modern IDM system therefore helps companies to keep track of users and their permissions, especially in complex and heterogeneous system landscapes.
SAP Corner
Zurück zum Seiteninhalt