Entering content frameBackground documentation Support Package Manager: Steps Locate the document in its SAP Library structure

The Support Package Manager informs you of the status of the step currently being executed in the status bar. If you want to know which steps are executed for which scenario, run the program RSSPAM10.

The following list explains the Support Package Manager steps in the order in which they are executed:

  1. PROLOGUE

    2. This step checks whether you are authorized to import Support Packages.

  2. CHECK_REQUIREMENTS

    3. This step checks various requirements for importing a Support Package, for example, whether the transport control program tp can log on to your system.

  3. DISASSEMBLE

    4. This step unpacks files from the appropriate EPS parcels and saves them to the transport directory.

  4. ADD_TO_BUFFER

    5. This step places the queue in the transport buffer of your system.

  5. TEST_IMPORT

    6. This step checks whether there are objects that are overwritten by the import, and that are still in unreleased tasks.

  6. IMPORT_OBJECT_LIST

    7. This step imports the object lists for the Support Packages in the queue into the system.

  7. OBJECTS_LOCKED_?

    8. This step checks whether there are objects that are overwritten by the import, and that are still in unreleased requests.

  8. SCHEDULE_RDDIMPDP

    9. This step schedules the transport daemon (program RDDIMPDP).

  9. ADDON_CONFLICTS_?

    10. This step checks whether there are conflicts between objects in the queue and any installed add-ons.

  10. CREATE_VERS_BEFORE

    11. This step generates versions of the objects that are contained in the Support Packages in the queue (if this option is set).

  11. SPDD_SPAU_CHECK

    12. This step checks whether a modification adjustment is necessary (transactions SPDD/SPAU).

  12. DDIC_IMPORT

    13. This step imports all ABAP Dictionary objects in the queue.

  13. AUTO_MOD_SPDD

    14. This step checks whether all modifications to ABAP Dictionary objects can be adjusted automatically.

  14. RUN_SPDD_?

    15. This step prompts you to adjust your modifications to the ABAP Dictionary objects by calling transaction SPDD.

  15. LOCK_EU

    16. This step locks the development environment (only when importing inactive report source code and texts).

  16. DDIC_ACTIVATION

    17. Activates the imported Dictionary objects

  17. INACTIVE_IMPORT

    18. This step imports inactive report source code and texts (only if this import method is chosen).

  18. IMPORT_PROPER

    19. This step imports all Repository objects and table entries. It then runs distribution, conversion, activation and generation programs.

  19. XPRA_EXECUTION

    20. This step executes the XPRAs and after-import methods.

  20. UNLOCK_EU

    21. This step unlocks the development environment (only when importing inactive report source code and texts).

  21. AUTO_MOD_SPAU

    22. This step checks whether modifications can be adjusted automatically.

  22. ABAP_GENERATION

    23. Generates the runtime objects for the imported Repository objects (ABAP source code, screens)

  23. RUN_SPAU_?

This step prompts you to adjust your modifications to Repository objects by calling transaction SPAU.
  1. CLEAR_OLD_REPORTS

    2. This step deletes obsolete versions of report source code and texts from the database (only when importing inactive report source code and texts).

  2. EPILOGUE

This step completes the Support Package import. Among other things, it checks whether the queue has been processed completely.

 

 

 Leaving content frame