If an error is recognized during a phase, Support Package Manager stops the import process until the error is corrected. You can get information about the reason the SPAM transaction was stopped and in which phase by choosing Queue > Status.
Error Types
Support Package Manager displays the following types of error messages:
- Support Package Manager consistency checks
- A typical example is the OBJECTS_LOCKED_? phase. Support Package Manager stops the import process if objects that need to be overwritten by the queue are still locked in requests.
- Error messages from the programs tp and R3trans
- You can always find the cause of the error in the relevant transport log. A typical example is the TEST_IMPORT phase. This step checks whether there are unconfirmed repairs to objects that need to be overwritten by the queue. The objects in question are listed in the test import log.
- Incorrect Configuration of the Change and Transport System
- Often the errors here are not having the relevant authorizations to files of the transport system, or using old program versions of tp or R3trans. Check the correct function of the transport tools by choosing Utilities -> Check Transport Tool.
- A typical example is the DISASSEMBLE phase. If sidadm does not have write authorization for the directory /usr/sap/trans/data (UNIX), Support Package Manager stops at the phase DISASSEMBLE with CANNOT_DISASSEMBLE_R_DATA_FILE.
- The Change and Transport System (CTS) shall be configured correctly.
Known Errors
PROLOGUE
In this phase, a dialog box prompts you to confirm the import of the Support Package. If you are not authorized to use Support Package Manager, or if the current queue has not yet been confirmed, Support Package Manager stops with a message to this effect.
CHECK_REQUIREMENTS
This phase checks various requirements for importing a Support Package. It may terminate for the following reasons:
- TP_CANNOT_CONNECT_TO_SYSTEM:
- tp cannot log on to the database of the system.
- QUEUE_NOT_EMPTY:
- There are incompletely processed OCS requests in the tp buffer. Use the following tp command to display these requests: tp SHOWBUFFER [SID] -D SOURCESYSTEMS= TAG=SPAM
- You can only continue to import the queue after these requests have been completely processed, or deleted from the tp buffer.
- OPEN_MOVE_NAMETABS:
- Inactive runtime objects exist for ABAP Dictionary objects. These objects must be activated via transaction SE11.
- CRM_REQ_FAILED:
- CRM-specific settings have not been configured. To adjust the settings, start transaction SA38 and run the program GN_XPRA_CRM40.
DISASSEMBLE
In this phase, files from the corresponding EPS parcels are unpacked and stored in the directory /usr/sap/trans/data (UNIX). It generates the command files (cofiles) from the accompanying files and saves them to the directory /usr/sap/trans/cofiles (UNIX). The action log shows detailed information about occurred errors. The following are the most frequent ones:
- The EPS parcel does not exist in the EPS Inbox; most probably, it was deleted. You need to download the relevant Support Package again.
- The signed manifest for an EPS file does not exist is wrong or the verification of the signature aborted with an error. Delete the corresponding EPS file from the EPS inbox and load the Support Package again from the SAP Support Portal or the collection CD/DVD. Then upload the SAR archive.
- The name of a data file could not be determined, because a profile parameter was not correctly configured. Use report RSPARAM to check the settings.
- An R3trans data file could not be disassembled. Possible errors include a missing EPS parcel or a data file that could not be written to. An error occurred when transmitting a 20K block from the EPS Inbox to the directory /usr/sap/trans/data (UNIX).
- The cofile could not be created from the corresponding data file. One possible error source is that sidadm does not have write authorization for the directory /usr/sap/trans/cofiles (UNIX).
- An R3trans data file exists in the transport directory which is newer than the one that you want to unpack from the EPS package. Do not import the obsolete version. You need to proceed as follows:
- Delete the current queue.
- Download the newest version of the relevant OCS package.
- Restart the import.
ADD_TO_BUFFER
This phase adds the queue to your system’s transport buffer. It may terminate for the following reasons:
- TP_INTERFACE_FAILURE:
- The tp interface could not be called. An RFC error has occurred.
- CANNOT_ADD_PATCH_TO_BUFFER:
- A Support Package could not be included in the transport buffer. For more information, see the SLOG log file in the directory /usr/sap/trans/log (UNIX).
MODIFY_BUFFER
In this phase, the transport buffer is prepared for correct processing of the following import phases. It may terminate for the following reasons:
- TP_INTERFACE_FAILURE:
- The tp interface could not be called. An RFC error has occurred.
- CANNOT_MODIFY_BUFFER:
- The system tried unsuccessfully to modify the transport buffer.
IMPORT_OBJECT_LIST
This phase imports the object lists for the Support Packages in the queue into the system. It may terminate for the following reasons:
- TP_INTERFACE_FAILURE:
- The tp interface could not be called.
- TP_FAILURE:
- tp could not be executed. For more information, see the SLOG or ALOG log files.
- COMMAND_FILE_IMPORT_FAILURE:
- The object list of one or more Support Packages could not be imported. You can find the source of the error in the command file import log.
TEST_IMPORT
This phase checks whether any objects overwritten by the import are still in unreleased tasks. You can find the source of the error in the log of the test import. For more information, refer to SAP Note 42379.
You can skip test import errors using Extras -> Ignore Test Import Errors and continue with the import. However, depending on the type of error, this may cause the error to reappear with very serious consequences during the real import. You therefore always need to check test import errors first, and correct them wherever possible.
OBJECTS_LOCKED_?
This phase checks whether any objects overwritten by the import are still in unreleased requests. It may terminate for the following reasons:
- CANNOT_GET_OBJECT_LIST:
- The object list for a Support Package could not be found, because the Support Package does not exist.
- CANNOT_CHECK_LOCKS:
- An error was triggered when the system tried to check the locks of an object in the queue.
- OBJECTS_LOCKED_IN_REQUESTS:
- Objects were found that are still in requests that have not yet been released. Release these requests before continuing with applying the patch.
CHECK_INACT_OBJECTS
In this phase it is checked if there are still objects that are inactive. It may terminate for the following reasons:
- CANNOT_GET_OBJECT_LIST:
- The object list for a Support Package could not be found, because the Support Package does not exist.
- CANNOT_CHECK_INACT_OBJS:
- An error occurred when checking the status of an object in the queue.
- SHOW_DETAIL_AND_DECIDE:
- Objects have been found that are still inactive. Activate the object before continuing with the import.
ADDON_CONFLICTS_?
This phase checks for conflicts between objects in the queue and installed add-ons. If it finds any, Support Package Manager stops and prompts you to import the relevant Conflict Resolution Transports (CRTs). It may terminate for the following reasons:
- CANNOT_GET_OBJECT_LIST:
- The object list for a Support Package could not be determined, because the Support Package does not exist.
- CANNOT_GET_LAST_UPGRADE_INFO:
- The information about the last component upgrade could not be determined.
- UNRESOLVED_ADDON_CONFLICTS:
- Conflicts with add-ons could not be resolved, because the corresponding CRTs are missing from the queue.
SCHEDULE_RDDIMPDP
This phase schedules the transport daemon (program RDDIMPDP). It may terminate for the following reasons:
- CANNOT_SCHEDULE_RDDIMPDP: The job RDDIMPDP could not be scheduled. Call Transaction SM37 (job selection), enter the following parameters and choose Continue:
Job Name RDDIMPDP
User Name [username]
Start after event SAP_TRIGGER_RDDIMPDP
Select the job that was terminated and display the job log.
- Problems with the SAP locking mechanism: Call transaction SM12 and make sure that no programs have the name RDDIMPDP.
CREATE_VERS_BEFORE
This phase creates versions in the version database of the objects that you want to import and for which versions can be created (ABAP code, dynpros, and DDIC objects). It may terminate for the following reasons:
- TP_INTERFACE_FAILURE:
- The tp interface could not be called.
- TP_FAILURE:
- tp could not be executed. For more information, read the SLOG or ALOG log files.
- If the return code is 0152 (nothing done), check in the configuration of the transport tool in the Transport Management System (transaction STMS) whether the VERS_AT_IMP parameter is set as ALWAYS. If it is not, set this value and continue importing the queue.
- TP_STEP_FAILURE:
- The tp step CREATE_VERS_BEFORE could not be performed successfully. To find the exact cause of the error, choose Goto -> Log -> Queue, and look at the version log.
SPDD_SPAU_CHECK
In this phase, the system checks if a modification adjustment is necessary (transactions SPDD/SPAU).
DDIC_IMPORT
This phase imports the ABAP Dictionary. It may terminate for the following reasons:
- TP_INTERFACE_FAILURE:
- The tp interface could not be called.
- TP_FAILURE:
- tp could not be executed. For more information, read the SLOG or ALOG log files.
- CANNOT_IMPORT_DDIC:
- The ABAP Dictionary could not be imported. You can find the source of the error in the dictionary import log.
AUTO_MOD_SPDD
This phase checks whether all modifications to ABAP Dictionary objects can be adjusted automatically.
RUN_SPDD_?
In this phase, you are prompted to adjust your modifications to the ABAP Dictionary objects by calling transaction SPDD.
LOCK_EU (only for import mode downtime-minimized)
This phase locks the development environment. It may terminate for the following reasons:
- TP_INTERFACE_FAILURE:
- The tp interface could not be called
- TP_FAILURE:
- tp could not be executed. For more information, see the SLOG or ALOG log files.
INACTIVE_IMPORT (only for import mode downtime-minimized)
This phase imports program code and program texts in an inactive state. It may terminate for the following reasons:
- TP_INTERFACE_FAILURE:
- The tp interface could not be called.
- TP_FAILURE:
- tp could not be executed. For more information, read the SLOG or ALOG log files.
- TP_STEP_FAILURE:
- The tp step DDIC_ACTIVATION could not be executed successfully. The cause of the error is in the relevant log (SAPBxxxxxxSID). This log is in subdirectory log in the transport directory. If this is the case, the activation errors disappear if the objects are activated again.
CRM_STOP_QUEUE_BDOCS
During this phase, the replication queue and realign queue are stopped, inbound queues are logged off and BDoc messages are fully processed. The following errors can cause the phase to be aborted:
- CRM_STOP_QUEUE_FAILED:
- The queues could not be stopped.
- CRM_ACTION_FAILED:
- The system could not execute the action.
- CRM_STATE_EVALUATION_FAILED:
- Could not read the result of this action.
CRM_LOCK_RTIME_GEN
During this phase, the generation of CRM runtime objects is locked.
The following errors can cause the phase to be aborted:
- CRM_LOCK_GEN_FAILED:
- Could not lock the generation of CRM runtime objects.
- CRM_ACTION_FAILED:
- The system could not execute the action.
- CRM_STATE_EVALUATION_FAILED:
- Could not read the result of this action
DDIC_ACTIVATION
This phase activates the imported ABAP Dictionary objects. It may terminate for the following reasons:
- TP_INTERFACE_FAILURE:
- The tp interface could not be called.
- TP_FAILURE:
- tp could not be executed. For more information, read the SLOG or ALOG log files.
- TP_STEP_FAILURE:
- The tp step DDIC Activation could not be executed successfully. To see the cause of the error in the activation log, choose Goto -> Log -> Queue.
- If you import two or more Support Packages in a queue, activation errors can result from an incorrect activation sequence for dictionary objects. If this is the case, the activation errors disappear if the objects are activated again. To do this, choose Support Package -> Import Queue.
IMPORT_PROPER
This phase imports all Repository objects and table entries. It may terminate for the following reasons:
- TP_INTERFACE_FAILURE:
- The tp interface could not be called.
- TP_FAILURE:
- tp could not be executed. For more information, read the SLOG or ALOG log files.
- TP_STEP_FAILURE:
- A tp step could not be performed successfully. You can find the source of the error in the relevant log, for example, in the import log.
- If a tp step 6, N, or S is in the termination message, it is a step independent of the transport request. As of Release 4.6A, the corresponding logs are in the log overview under the node Import steps not specific to the transport request.
- You can also find these logs in the following files in the log subdirectory of your transport directory (usually /usr/sap/trans/log):
tp Step 6: P[YY][MM][DD].[SID]
tp Step N: N[YY][MM][DD].[SID]
tp Step S: DS[YY][MM][DD].[SID]
To display these files, execute report RSPUTPRT, or call transaction AL11.
PREPARE_XPRA
This phase prepares the execution of the XPRAs and after-import methods. It may terminate for the following reasons:
- TP_INTERFACE_FAILURE:
- The tp interface could not be called.
- CANNOT_MODIFY_BUFFER:
- The program tp was unable to modify the relevant buffer file. For more information, read the SLOG log file.
UNLOCK_EU (only for import mode downtime-minimized)
This phase unlocks the development environment. It may terminate for the following reasons:
- TP_INTERFACE_FAILURE:
- The tp interface could not be called.
- TP_FAILURE:
- tp could not be executed. For more information, read the SLOG or ALOG log files.
AUTO_MOD_SPAU
This phase checks whether modifications can be adjusted automatically.
XPRA_EXECUTION
This phase executes the XPRAs and after-import methods. It may terminate for the following reasons:
- TP_INTERFACE_FAILURE:
- The tp interface could not be called.
- TP_FAILURE:
- tp could not be executed. For more information, read the SLOG or ALOG log files.
- TP_STEP_FAILURE:
- The tp step XPRA_EXECUTION could not be performed successfully. To view the cause of the error in the method execution log, choose Goto -> Log -> Queue.
- CANNOT_READ_BUFFER:
- The tp program was unable to open the relevant buffer file. For more information, read the SLOG log file.
- CANNOT_MODIFY_BUFFER:
- The program tp was unable to modify the relevant buffer file. For more information, read the SLOG log file.
CRM_UNLOCK_RTIME_GEN
During this phased, the generation of runtime objects is unlocked and CRM Adapter Repository tables are adjusted. The following errors can cause the phase to be aborted:
- CRM_UNLOCK_GEN_FAILED:
- Could not unlock the generation of CRM runtime objects.
- CRM_ACTION_FAILED:
- The system could not execute the action.
- CRM_STATE_EVALUATION_FAILED:
- Could not read the result of this action.
CRM_MERGE_BDOCS
During this phase, BDoc messages are adjusted. With inconsistent BDoc messages, the phase is aborted and you have to adjust the corresponding BDoc message manually. The following errors can cause the phase to be aborted:
- CRM_MERGE_BDOC:
- After the changes have been imported, some BDoc messages may be inconsistent and need to be adjusted. Adjustments are made in the BDoc Modeler. Choose the Adaption pushbutton to open the BDoc Modeler. BDoc types with inconsistent versions are flagged accordingly.
- CRM_ACTION_FAILED:
- The system could not execute the action.
CRM_REGEN_RTIME_OBJS
During this phase, changed runtime objects are generated again. The following error can cause the phase to be aborted:
- CRM_RUNTIME_GENERATION:
- If you have not planned any jobs for regenerating runtime objects, the import process is stopped and you can start the regeneration of runtime objects manually or create a job.
CRM_START_QUEUE
During this phase, the replication queue and realignment queue are started and the inbound queue is logged on. The following errors can cause the phase to be aborted:
- CRM_START_QUEUE_FAILED:
- Could not start the replication queue and realignment queue.
- CRM_START_INB_Q_FAILED:
- The inbound queue could not be logged on.
- CRM_ACTION_FAILED:
- The system could not execute the action.
- CRM_STATE_EVALUATION_FAILED:
- Could not read the result of this action.
ABAP_GENERATION
This phase generates the runtime objects for the imported Repository objects (ABAP source code and dynpros). It may terminate for the following reasons:
- TP_INTERFACE_FAILURE:
- The tp interface could not be called.
- TP_FAILURE:
- tp could not be executed. For more information, read the SLOG or ALOG log files.
- TP_STEP_FAILURE:
- The tp step could not be executed successfully. To see the cause of the error in the generation log, choose Goto -> Log -> Queue.
- Remember that objects delivered in Support Packages have already been imported completely. If the return code is 0008, all objects without syntax errors have been generated.
- The persistence of syntax errors can be due to one of the following reasons:
- Systems that have been developed over a long period of time often contain many objects that are not longer used or maintained. These objects are still active in the Repository and can reference or use other objects (such as includes). If these includes are modified, syntax errors might occur in the obsolete objects. However, these errors have no effect on the SAP System, and can be ignored.
- Generated includes or programs can contain syntax errors after an import. You can usually ignore these errors, since the source code of the generated objects is generated again when the corresponding transactions are started (a special generation transaction might exist).
- If SAP objects have been modified, or if customer objects use SAP objects, there are may also be syntax errors in the modified SAP objects and the customer objects. If this is the case, you must adjust the modifications or customer developments.
- Buffer synchronization problems can also cause generation errors. For more information, see SAP Note 40584.
- Generation errors do not necessarily indicate inconsistencies in the system. However, you should investigate them using the criteria above. If the errors are non-critical, or temporary, ignore them by choosing Extras -> Ignore Generation Errors, and continue the import of the queue. Choose Support Package -> Import Queue.
- CANNOT_READ_BUFFER:
- The tp program was unable to open the relevant buffer file. For more information, read the SLOG log file.
- CANNOT_MODIFY_BUFFER:
- The program tp was unable to modify the relevant buffer file. For more information, read the SLOG log file.
RUN_SPAU_?
This phase prompts you to adjust your modifications to Repository objects by calling transaction SPAU.
CLEAR_OLD_REPORTS (only for import mode downtime-minimized)
This phase deletes obsolete versions of program code and program texts from the system. It may terminate for the following reasons:
- TP_INTERFACE_FAILURE:
- The tp interface could not be called.
- TP_FAILURE:
- tp could not be executed. For more information, read the SLOG or ALOG log files.
- TP_STEP_FAILURE:
- The tp step CLEARREPORTS could not be performed successfully. To see the cause of the error, look in the corresponding log (PZ[yy][mm][dd].[SID]). This log is in subdirectory log in the transport directory. To display this file, run report RSPUTPRT, or call transaction AL11.
EPILOGUE
This phase completes the import process. The system checks if the queue has been completely processed. If it has, there should be no more transport buffer entries for the queue. It may terminate for the following reasons:
- TP_FAILURE:
- tp could not be executed. For more information, read the SLOG or ALOG log files.
- QUEUE_STILL_IN_BUFFER:
- The queue has not been processed completely, since there are still incomplete Support Packages in the queue in the transport buffer.
- CANNOT_RESET_FCS_FLAG:
- If there is an FCS Support Package (FFD) in the queue, the system is marked as Final State after the Support Package is applied. In this case, this operation could not be successfully performed.
