Do you have any questions?
SAP System Copies
If you are running a multi-system landscape with a common transport directory, it is convenient to enable this option only in the first system you are inserting support packages into, and to disable it in the following systems. Since the data files no longer need to be regenerated there, this saves time when playing in. Delete data files after inserting You can specify whether the data files should be deleted after inserting the support packages. This saves disk space and is enabled in the default setting. If you are running a multi-system landscape with a common transport directory, it is convenient to disable this option, since then the data files in the other systems no longer need to be re-created (see above Regenerate data files). Execute ABAP/Dynpro generation This option determines whether the programmes and screens shipped with the support packages should be generated during the commit. Note that generation can take a long time. Without automatic generation, the programmes and dynpros are not generated until the first call. Note that this parameter can only be affected by you if the generation is allowed by SAP during the insertion of this support package. The SPAM update does not affect the generation. SPAM Settings Option SAPM Basic Setting Transmission Monitor From Scenario Standard Rebuild Data File A data file after the example. Delete Do a Generation From Use the transaction SPAM to insert Support Packages [page 8] into your system, regardless of whether the support packages come from the SAPNet - R/3 Frontend, the SAPNet - Web Frontend, or Collection CDs. Prerequisites User: It must have the appropriate permissions [page 7] for the SAP Patch Manager. He must be registered with the client 000. He must have called the transaction SPAM. Select Tools ABAP Workbench Tool Maintenance Patches or enter the transaction code SPAM.
The SAP Patch Manager offers two scenarios for inserting support packages or queues: Test Scenario Use the test scenario to determine whether conflicts or problems occur (e.g., unreleased repairs) or whether a modification match is necessary before the actual insertion. This scenario allows you to estimate and minimise the time and effort required to load support packages. In this scenario, no data is imported into the system, and you can continue to play in the event of an error without the error being corrected. You must select the test scenario explicitly. Note that once the test scenario has passed, the queue is empty and needs to be redefined. You must also explicitly choose the default scenario.
How to create a parameter transaction for the SM30
SAP Basis is responsible for the smooth operation of the SAP Basis system. The SAP Basis system is like an operating system for R/3 as well as S/4. Every operating system, such as Windows, provides an environment in which programs developed for that environment can run, such as MS Office. Likewise, the SAP Basis system provides an environment in which SAP programs can run. In any R/3 or S/4 system, there is a database server, such as HANA, where the database resides. It provides the necessary data to all other applications. The data here is not only data tables, but also applications, system control tables and user data.
Reachable at any time: Your competent contact person is available at all times. If you operate SAP Basis Support in-house, personnel bottlenecks may occur. If your SAP employees are absent due to illness or vacation, there may be no equivalent replacement available.
Tools such as "Shortcut for SAP Systems" complement missing functions in the SAP basis area.
Use the latest SPAM update.
Permissions beyond the daily task spectrum are granted only for limited periods and under control.