SAP Basis SAP Basis Introduction and R3 Architecture Overview (in English) - SAP Corner

Direkt zum Seiteninhalt
SAP Basis Introduction and R3 Architecture Overview (in English)
Each participant will install their own HANA instance for practice ;
In the default scenario, the support packages in the queue are fully loaded. In the event of an error, you will not be able to resume and complete the playback successfully unless the error(s) are resolved. Prerequisites The queue is already defined. Procedure To set the scenario you want, select Additions Settings. Select the desired scenario. Select Insert Support Package Queue. You can also use this function to restore an aborted commit procedure. The status bar provides information on the progress of the commit and the latest steps of the SAP Patch Manager. During the recording, you may get into the modification comparison (SPDD, SPAU). If you are playing with the default scenario, you must immediately perform the comparison of Dictionary objects (transaction SPDD), whereas when you compare Repository objects (transaction SPAU), you have the choice to skip it first and perform it later (modification comparison [page 22]). The mode is blocked while a Support Package is being introduced. To avoid repeated login, open a second mode before inserting the queue.

If you need to reinstall a Support Package because of errors or because a SPAM update is required, reset its status. Resetting does not mean that the system is at an old state. Note that your system is inconsistent when you reset the status after items have already been imported (for example, after the DDIC_IMPORT step and following). Resetting the status should only be used to troubleshoot the issue and you should repeat the playback as soon as possible. Procedure To reset the status of a Support Package or Queue, select Add Status Reset. Result After updating the status, the corresponding entries in the cofile and in the log file are deleted. The support package must then be fully reloaded. The transaction SPAM starts the insertion with the step CHECK_REQUIREMENTS [page 26].
The following list explains the steps in the order they are performed by SPAM: PROLOGUE This step will check if you are eligible to play Support Packages. CHECK_REQUIREMENTS In this step, different requirements for inserting are checked, e.g. the login of the transport control programme tp to your system. DISASSEMBLE In this step, the data files are unpacked from the corresponding EPS packages and placed in the transport directory. ADD_TO_BUFFER In this step, the queue is placed in the transport buffer of your system. TEST_IMPORT This step checks whether there are any objects that are overridden during the commit and are in unreleased tasks. IMPORT_OBJECT_LIST In this step, the object lists for the support packages that are in the queue are fed into the system. OBJECTS_LOCKED_? This step checks to see if there are any objects that are overwritten during the commit and that are in unreleased jobs. SCHEDULE_RDDIMPDP In this step the transport daemon (programme RDDIMPDP) is planned. ADDON_CONFLICTS_? This step checks to see if there are conflicts between objects in the queue and add-ons installed. SPDD_SPAU_CHECK This step will check if a modification match (transactions SPDD/SPAU) is necessary. DDIC_IMPORT In this step, all ABAP Dictionary objects of the queue are imported. AUTO_MOD_SPDD This step checks whether modifications to ABAP Dictionary objects can be adjusted automatically. RUN_SPDD_? This step prompts you to customise your modifications to ABAP Dictionary objects by calling the transaction SPDD. IMPORT_PROPER In this step, all repository objects and table entries are fed. Then actions such as distribution, implementation, activation and generation take place. AUTO_MOD_SPAU This step checks whether modifications can be adjusted automatically. RUN_SPAU_?

In order for your SAP system landscape to function permanently, it requires error-free installation and regular support. You can rely on these services:

Some missing SAP basic functions in the standard are supplied by the PC application "Shortcut for SAP Systems".

The Technical Lead will become more important in the future as the SAP basis acts as a technology consultant and more projects and project activities are expected in the future.

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 you will find useful information on this topic.

This can be done through automated monitoring, validation using tools such as SAP-LVM (Landscape Virtualisation Management) or SAP Solution Manager, as well as manual checklists.
SAP Corner
Zurück zum Seiteninhalt