The Support Package Manager informs you of the status of the phase currently being executed in the status bar. If you want to know which phases are executed for which scenario(test or standard scenario), run the program RSSPAM10.
The following list provides an overview of all the modules and phases and lists them in the order in which they are executed by the Support Package Manager:
This phase checks whether you are authorized to import Support Packages.
This phase checks various requirements for importing a Support Package, for example, whether the transport control program tp can log on to your system.
This phase unpacks files from the appropriate EPS parcels and saves them to the transport directory.
This phase places the queue in the transport buffer of your system.
This phase prepares the transport buffer for correct processing of the following import phases.
This phase performs a test import for the queue with the transport control program tp. The system checks whether there are objects that are in open repairs and that are overwritten during the import, or whether other conditions prevent the import of an object.
This phase imports the object lists for the Support Packages in the queue into the system.
This phase checks whether there are objects that are overwritten by the import, and that are still in unreleased requests.
This phase checks whether there are conflicts between objects in the queue and any installed add-ons.
This phase schedules the transport daemon (program RDDIMPDP).
Import 1 Module
This phase generates versions of the objects that are contained in the Support Packages in the queue (if this option is set).
In this phase, the system checks if a modification adjustment is necessary (transactions SPDD/SPAU).
This phase imports all ABAP Dictionary objects in the queue.
This phase checks whether all modifications to ABAP Dictionary objects can be adjusted automatically.
In this phase, 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.
This phase activates the imported ABAP Dictionary objects.
Import 2 Module
This phase imports all the Repository objects and table entries if they were not already imported in the INACTIVE_IMPORT phase. This is preceded by actions such as table conversion and activation of the name tabs.
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.
This phase checks whether modifications can be adjusted automatically.
This phase executes the XPRAs and after-import methods.
This phase generates the runtime objects for the imported Repository objects (ABAP source texts and screens).
Clean Up Module
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.
This phase completes the import. Among other things, it checks whether the queue has been processed completely.