SAP Basis Planning, coordination and installation of SAP Basis upgrades, support packages and patches

Direkt zum Seiteninhalt
Planning, coordination and installation of SAP Basis upgrades, support packages and patches
SUM - the Software Update Manager, the relatively new tool for "remote control" of the known update transactions from outside the system, for ABAP and JAVA
The positioning depends strongly on the previously identified target groups and must be justified accordingly. Positioning is extremely important for the SAP basis. It is primarily a matter of positioning within the IT organisation and defining or positioning the other IT departments that can be considered as competitors in the context of this step. STEP 6: OWN EMPLOYEES This step will identify the necessary skills and training of their own employees necessary to fulfil the objectives and provide the service. The necessary skills and roles for the SAP basis are explained in detail in the recommendation Skills & Roles.

The presentation layer is the interface to the users. Through a graphical interface, users enter data or interact with data through the applications. This presentation layer exchanges data with the application layer.
Table of Contents Show
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.

SAP Basis usually takes care of the administration of the SAP system. The most important SAP Basis transactions are listed in this article.

For administrators, a useful product - "Shortcut for SAP Systems" - is available in the SAP basis area.

DDIC_IMPORT This step imports the ABAP Dictionary.

However, this role will be much more coordinated in the future.
SAP Corner
Zurück zum Seiteninhalt