Details of different phases of a spam-saint update and the logs that needs to be checked while importing a package

When ever you are importing a package through SPAM/SAINT , make sure that first you update the SAPM/SAINT to the latest version. Once the SPAM/SAINT update is done then you can proceed with the importing of packages. There are different phases while you do a package import .The SAP Patch Manager tells 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 and check.

The below list explains the steps executed by SPAM in the order in which they are performed and the logs that needs to be checked if you get stucked in a particular phase. Log files will be under /usr/sap/trans/log . Log files are not created for all the phases .

PROLOGUE :- This is the first phase of the import ,In this phase, the system checks for authorizations to import Support Packages.
CHECK_REQUIREMENTS :- During this phase various requirements are checked for importing a Support Package. Several consistency checks happens , which shall ensure a successful import.
DISASSEMBLE :- During this phase , the files from the corresponding EPS parcels are unpacked, and stored in the directory i.e the PAT file is disassembled into CO file and DATA file. If any issue happenes in this phase you need to check the file SAPL* .
ADD_TO_BUFFER :- During this phase , the queue is put into the transport buffer of your system.
MODIFY_BUFFER :- Appends the OCS requests to the tp buffer and switches off the tp steps which shall not be executed (ABAP generation, creation of versions).
TEST_IMPORT :- During this phase , the system checks if there are still objects in tasks that have not yet been released and are overwritten when the Support Package is imported. This step will actually do a test import and check if the import is possible or not. If you face any issues in this phase you need to check the log file SAPP* .
IMPORT_OBJECT_LIST :- During this phase , the object lists for the Support Packages in the queue are imported into the system.
OBJECTS_LOCKED_? :- During this phase , the system checks if there are still objects in tasks that have not yet been released and are overwritten when the Support Package is imported. It Checks, whether the to be imported objects are locked in table TLOCK.
SCHEDULE_RDDIMPDP :- During this phase, the transport daemon (program RDDIMPDP) is scheduled. tp communicates with the transport dispatcher RDDIMPDP, which in turn calls other ABAP programs to perform different steps of the import process . The ABAP programs executed during imports are referred to as the RDD* programs.
CREATE_VERS_BEFORE :- Creates versions of all objects contained in the OCS Packages
ADDON_CONFLICTS_?:- During this phase, the system checks if there are conflicts between objects in the queue and installed add-ons. Checks for conflicts between installed Add-Ons and Support Packages or Add-Ons which are going to be installed. Table AVERS contains the object list of the Add-On components in fields FULLTASK and DELTATASK.
SPDD_SPAU_CHECK :- During this phase , the system checks if a modification adjustment is necessary . check it with transactions SPDD & SPAU.
DDIC_IMPORT :- During this phase, all the ABAP Dictionary objects of the queue are imported. If you face any issue during this phase you need to check the log file SAPH*.
AUTO_MOD_SPDD :- During this phase , the system checks if modifications to the ABAP Dictionary objects can be adjusted automatically.
RUN_SPDD_? :- During this phase, you are asked to adjust your modifications to the ABAP Dictionary objects by calling Transaction SPDD.
IMPORT_PROPER :-  During this phase , all the Repository objects and table entries are imported. There are four sub phases during this phase :-
     > Distribution :-- if any issue happen in this phase then you need to check the log file DS*
     > Conversion :-- if any issue happen in this phase then you need to check the log file N**
     >Move Name tabs :-- if any issue happen in this phase then you need to check the log file P**
     >Main Import :- if any issue happen in this phase then you need to check the log file SAPI*
AUTO_MOD_SPAU:- During this phase, the system checks if modifications can be adjusted automatically.
RUN_SPAU_? :- During this phase , you are asked to adjust your modifications to the Repository objects by calling Transaction SPAU.
DDIC_ACTIVATION :- During this phase activation od DDIC objects happens. tp starts a batch job in the system (RDDMASGL), transfer of needed informations happens via table TRBAT.
XPRA_EXECUTION :- XPRAs and After Import Methods are executed .
EPILOGUE :- During this phase , the import of the Support Package is ended. The system checks if the queue has been completely processed.