Software maintenance of SAP® systems
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 ....
EDI enables companies to exchange business data such as purchase orders or invoices electronically. This data exchange is known as Electronic Data Interchange (EDI). What steps are needed to exchange data between two systems? In this post, I'd like to show you how to configure your SAP system so that an order, after it has been released, is sent electronically to your supplier. Data exchange between two systems requires a valid RFC connection to the receiver system and a transactional RFC IDoc port.
The SAP Basis Plug-In is backward compatible and follows the release and maintenance strategy of the SAP R/3 Plug-In. SAP ships it together with the SAP R/3 Plug-In.
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.
"Shortcut for SAP Systems" makes many tasks in the area of the SAP basis much easier.
If the generation (tp-Step G) is aborted, you can either fix the errors immediately or after the commit is completed.
It is also necessary to check whether a user should (still) have a specific role.