The following list explains the phases executed by the Add-On Installation Tool in the order in which they are performed.
Preparation Module
…
1. PROLOGUE
This phase checks whether you are authorized to import packages.
2. CHECK_REQUIREMENTS
This phase checks various requirements for importing a Support Package, for example, whether the transport control program tp can log on to your system.
3. DISASSEMBLE
This phase unpacks files from the appropriate EPS parcels and saves them to the transport directory.
4. CREATE_COMPONENTS
This phase initializes the software components that are to be installed.
5. ADD_ TO_BUFFER
This phase places the queue in the transport buffer of your system.
6. MODIFY_BUFFER
This phase prepares the transport buffer for correct processing of the following import phases.
7. IMPORT_OBJECT_LIST
This phase imports the object lists for the packages in the queue into the system.
8. OBJECTS_LOCKED_?
This phase checks whether there are objects that are overwritten by the import, and that are still in unreleased requests.
9. ADDON_CONFLICTS_?
This phase exists only when you install or upgrade add-ons (not for PCS).
This phase checks for conflicts with imported Support Packages that have a higher version than is specified in the import prerequisites for the add-on.
If another add-on is already installed, SAINT checks whether there are conflicts between this add-on and any Support Packages that were included as import prerequisites for the new add-on. It also checks whether the new add-on has direct object conflicts with the add-on that is already installed.
10. SCHEDULE_RDDIMPDP
This phase schedules the transport daemon (program RDDIMPDP).
Import 1 Module
11. CREATE_VERS_BEFORE
This phase exists only when you install or upgrade add-ons (not for PCS).
This phase generates versions of the objects that are contained in the packages in the installation queue (if this option is set).
12. SPDD_SPAU_CHECK
This phase exists only when you install or upgrade add-ons (not for PCS).
In this phase, the system checks if a modification adjustment is necessary (transactions SPDD/SPAU).
13. DDIC_IMPORT
This phase exists only when you install or upgrade add-ons (not for PCS).
This phase imports all ABAP Dictionary objects in the queue.
14. AUTO_MOD_SPDD
This phase exists only when you install or upgrade add-ons (not for PCS).
This phase checks whether all modifications to ABAP Dictionary objects can be adjusted automatically.
15. RUN_SPDD_?
This phase exists only when you install or upgrade add-ons (not for PCS).
In this step, you are asked to adjust your modifications to the ABAP Dictionary objects by calling Transaction SPDD.
16. LOCK_EU (only for import mode downtime-minimized)
This phase locks the development environment.
17. INACTIVE_IMPORT (only for import mode downtime-minimized)
This phase imports program code and program texts in an inactive state.
18. DDIC_ACTIVATION
This phase exists only when you install or upgrade add-ons (not for PCS).
This phase activates the imported ABAP Dictionary objects.
Import 2 Module
19. IMPORT_PROPER
This phase imports all the Repository objects and table entries if they were not already imported in the INACTIVE_IMPORT phase.
20. PREPARE_XPRA
This phase prepares the execution of the XPRAs and after-import methods.
21. UNLOCK_EU (only for import mode downtime-minimized)
This phase unlocks the development environment.
22. AUTO_MOD_SPAU
This phase exists only when you install or upgrade add-ons (not for PCS).
This phase checks whether modifications can be adjusted automatically.
23. XPRA_EXECUTION
This phase executes the XPRAs and after-import methods.
24. ABAP_GENERATION
This phase exists only when you install or upgrade add-ons (not for PCS).
This phase generates the runtime objects for the imported Repository objects (ABAP source code and screens).
Clean Up Module
25. RUN_SPAU_?
This phase exists only when you install or upgrade add-ons (not for PCS).
This phase prompts you to adjust your modifications to Repository objects by calling transaction SPAU.
26. CLEAR_OLD_REPORTS (only for import mode downtime-minimized)
This phase deletes the obsolete versions of program code and program texts in the database.
27. EPILOGUE
This phase completes the import. The add-on is registered.