// ]]>

Sunday, 5 January 2014

Phases of the Support Package Manager

                                 Phases of the Support Package Manager

1.
 The Support Package Manager runs through a series of phases when it imports Support Packages. If you
    want to know which phases were performed for which scenario (test scenario or standard scenario),
    execute program RSSPAM10.

2. The following list provides an overview of all the modules and phases and list them in the order in which
    they are executed by the Support Package Manager:

                                               Module: Preparation
1. PROLOGUE
   This phase checks if you are authorized to import Support Packages.

2. CHECK_REQUIREMENTS
   This phase checks various prerequisites for importing Support Packages such as the tp logon to your
   system.

3. DISASSEMBLE
   This phase disassembles, or unpacks, the data files from the relevant EPS parcels and copies them to the
   transport directory.

4. ADD_TO_BUFFER
   This phase copies the queue to the transport buffer of your system.

5. MODIFY_BUFFER
    In this phase, the transport buffer is prepared for correct processing of the following import phases.

6. IMPORT_OBJECT_LIST
    This phase imports the object lists of the Support Packages in the queue into the system.

7. TEST_IMPORT
    This phase performs a test import for the current queue using tp. It checks if there are objects that are in
    open repairs and will be overwritten during the import, or if any other circumstances are preventing an
    object from being imported successfully.

8. OBJECTS_LOCKED_?
    This phase checks if there are objects that will be overwritten by the Support Package, and that are still in
    requests that have not yet been released.

9. ADDON_CONFLICTS_?
   This phase checks if there are conflicts between the objects in the queue and the installed add-ons.

10. SCHEDULE_RDDIMPDP
     This phase schedules the transport daemon (program RDDIMPDP).
                                           Module Import 1

11.
 CREATE_VERS_BEFORE
      This phase generates versions of the objects in the Support Packages that are in the queue.

12. SPDD_SPAU_CHECK
     This phase checks if a modification adjustment is necessary (Transactions SPDD/SPAU).

13. DDIC_IMPORT
     This phase imports all ABAP Dictionary objects in the queue.

14. AUTO_MOD_SPDD
      This phase checks if modifications to ABAP Dictionary objects can be adjusted automatically.

15. RUN_SPDD_?
     This phase prompts you to adjust your modifications to ABAP Dictionary objects with Transaction
     SPDD.

16. LOCK_EU (For Import Mode Downtime-Minimized Only)
     This phase locks the development environment.

17. INACTIVE_IMPORT (For Import Mode Downtime-Minimized Only)
      This phase imports program code and program texts in an inactive state.

18. DDIC_ACTIVATION
     This phase activates the imported Data Dictionary objects.

19. IMPORT_PROPER
     This phase imports all Repository objects and table entries, provided they have not already been
     imported during the phase INACTIVE_IMPORT. This is preceded by actions such as table conversion
     and activation of the name tabs
.
20. PREPARE_XPRA
      This phase prepares the XPRAs and after-import methods to be executed.

21. UNLOCK_EU (For Import Mode Downtime-Minimized Only)
      This phase unlocks the development environment.

22. AUTO_MOD_SPAU
      This phase checks whether modifications can be adjusted automatically.

23. XPRA_EXECUTION
     This step executes the XPRAs and the post-import methods.

24. ABAP_GENERATION
      This phase generates runtime objects for the imported Repository objects (ABAP source texts and
      screens).
25. RUN_SPAU_?
      This phase prompts you to adjust your modifications to Repository objects with transaction SPAU.

26. CLEAR_OLD_REPORTS (For Import Mode Downtime-Minimized Only)
      This phase deletes obsolete versions of the program code and program texts in the database.

27. EPILOGUE
      This phase completes the import of the Support Package. It also checks if the queue was processed completely.