Known Errors in Support Package Manager

 

PROLOGUE

In this phase, a dialog box prompts you to confirm the import of the Support Package. If you are not authorized to use the Support Package Manager or the current queue has not yet been confirmed, the Support Package Manager stops with an appropriate message.

 

CHECK_REQUIREMENTS

This phase checks various requirements for importing a Support Package. This phase 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.

 

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). This phase may terminate for the following reasons:

¡        CANNOT_SKIP_ATTRIBUTE_RECORD: The attributes could not be read in the EPS parcel. The file cannot read, either because it has been deleted or you do not have the correct authorizations at the operating system level.

¡        CANNOT_DETERMINE_EPS_PARCEL: The EPS parcel is not in the EPS Inbox, because it may have been deleted. You must load the appropriate Support Package again.

¡        CANNOT_DETERMINE_DATA_FILES: The name of a data file could not be determined, because a profile parameter was not correctly configured. Use the report RSPARAM to check the settings.

¡        CANNOT_DISASSEMBLE_R_DATA_FILE: An R3trans data file could not be unpacked. 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).

¡        CANNOT_DISASSEMBLE_D_DATA_FILE: An ADO data file could not be unpacked. The reasons are the same as for CANNOT_DISASSEMBLE_R_DATA_FILE.

¡        CANNOT_CREATE_COFILE: The cofile could not be created from the corresponding data file. One possible error source is that <sid>adm does not have write authorization for the directory/usr/sap/trans/cofiles (UNIX). Check whether the data file was created. If it was not created, check that the option Create new data file is activated in the settings.

 

ADD_TO_BUFFER

This phase places the queue in the transport buffer of your system. This phase may terminate for the following reasons:

¡        TP_INTERFACE_FAILURE: The tp interface could not be called. There is an RFC error.

¡        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).

¡        CANNOT_MODIFY_BUFFER: An unsuccessful attempt was made to modify the transport buffer.

 

MODIFY_BUFFER

This phase prepares the transport buffer for correct processing of the following import phases. This phase may terminate for the following reasons:

¡        TP_INTERFACE_FAILURE: The tp interface could not be called. There is an RFC error.

¡        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).

¡        CANNOT_MODIFY_BUFFER: An unsuccessful attempt was made to modify the transport buffer.

 

TEST_IMPORT

This phase checks whether there are objects that are overwritten by the import, and that are still in unreleased tasks. You can find the source of error in the log of the test import.

You can skip test import errors and continue the import by choosing Extras ® Ignore Test Import Errors. However, depending on the type of error, this may cause the error to reappear during the real import with very serious consequences. For this reason, you must always check test import errors first, and correct them if possible.

                                                   

IMPORT_OBJECT_LIST

This phase imports the object lists for the Support Packages in the queue into the system. This phase may terminate for the following reasons:

¡        TP_INTERFACE_FAILURE: The tpinterface could not be called.

¡        TP_FAILURE: The program tp could not be executed. For more information, see the SLOG or ALOG log files.

¡        COMMAND_FILE_IMPORT_FAILURE: The object list for one or more Support Packages could not be imported. You can find the source of error in the log of the command file import.

 

OBJECTS_LOCKED_?

This phase checks whether there are objects that are overwritten by the import, and that are still in unreleased requests. This phase 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 occurred when checking 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 you continue with the import of the Support Packages.

 

ADDON_CONFLICTS_?

This phase checks whether there are conflicts between objects in the queue and any installed add-ons. If there are any conflicts, the Support Package Manager stops and asks you to import the relevant Conflict Resolution Transports (CRTs). This phase 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 component upgrade could not be determined.

¡        UNRESOLVED_ADDON_CONFLICTS: Conflicts with add-ons could not be resolved, because the relevant CRTs are missing from the queue.

 

SCHEDULE_RDDIMPDP

This phase schedules the transport daemon (program RDDIMPDP). This phase 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 then choose Continue:

Job name	RDDIMPDP
User name	<User name>
Trigger event	SAP_TRIGGER_RDDIMPDP

Select the job that was terminated and display the job log.

¡        Problems with the SAP lock mechanism: Call transaction SM12 and make sure that there are no programs listed with the name RDDIMPDP.

 

CREATE_VERS_BEFORE

This phase creates versions in the version database of the objects that you want to import and of which versions can be created (ABAP coding, screens, and DDIC objects). This phase may terminate for the following reasons:

¡        TP_INTERFACE_FAILURE: The tpinterface could not be called.

¡        TP_FAILURE: The program tp could not be executed. For more information, see the SLOG or ALOG log files.

If the return code is 0152 (nothing done), check in the configuration of the transport tools in the Transport Management System (transaction STMS) whether the VERS_AT_IMP parameter is set asALWAYS. If this is not the case, set this value and then continue to import 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. This phase may terminate for the following reasons:

¡        TP_INTERFACE_FAILURE: The tp interface could not be called.

¡        TP_FAILURE: The program tp could not be executed. For more information, see the SLOG or ALOG log files.

¡        CANNOT_IMPORT_DDIC: The ABAP Dictionary could not be imported. You can find the source of 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 asked 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. This phase may terminate for the following reasons:

-          TP_INTERFACE_FAILURE: The tpinterface could not be called.

-          TP_FAILURE: The program tp could not be executed. For more information, see the SLOG or ALOG log files.

 

DDIC_ACTIVATION

This phase activates the imported ABAP Dictionary objects. This phase may terminate for the following reasons:

¡        TP_INTERFACE_FAILURE: The tp interface could not be called.

¡        TP_FAILURE: The program tp could not be executed. For more information, see the SLOG or ALOG log files.

¡        TP_STEP_FAILURE: The tp step DDIC_ACTIVATION could not be executed successfully. To view 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.

 

 

INACTIVE_IMPORT (only for import mode downtime-minimized)

This phase imports program code and program texts in an inactive state. This phase may terminate for the following reasons:

-          TP_INTERFACE_FAILURE: The tpinterface could not be called.

-          TP_FAILURE: The program tp could not be executed. For more information, see the SLOG or ALOG log files.

-          TP_STEP_FAILURE: The tp step INACTIVE_IMPORT could not be executed successfully. The cause of the error is in the corresponding log (SAPBxxxxxx.<SID>). This log is in the log subdirectory of the transport directory. To display this file, execute treport RSPUTPRT, or call transaction AL11.

 

IMPORT_PROPER

This phase imports all Repository objects and table entries. This phase may terminate for the following reasons:

¡        TP_INTERFACE_FAILURE: The tpinterface could not be called.

¡        TP_FAILURE: The program tp could not be executed. For more information, see the SLOG or ALOG log files.

¡        TP_STEP_FAILURE: A tp step could not be performed successfully. You can find the source of 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. The corresponding logs are in the log overview are 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 treport RSPUTPRT, or call transaction AL11.

 

PREPARE_XPRA

This phase prepares the execution of the XPRAs and after-import methods. This phase may terminate for the following reasons:

¡        TP_INTERFACE_FAILURE: The tp interface could not be called.

¡        CANNOT_MODIFY_BUFFER: The tpprogram could not change the corresponding buffer file. For more information, see the SLOG log file.

 

UNLOCK_EU (only for import mode downtime-minimized)

This phase unlocks the development environment. This phase may terminate for the following reasons:

-          TP_INTERFACE_FAILURE: The tpinterface could not be called.

-          TP_FAILURE: The program tp could not be executed. For more information, see 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. This phase may terminate for the following reasons:

¡        TP_INTERFACE_FAILURE: The tpinterface could not be called.

¡        TP_FAILURE: The program tp could not be executed. For more information, see the SLOG or ALOG log files.

¡        TP_STEP_FAILURE: The tp step XPRA_EXECUTION could not be performed successfully. To find the cause of the error, see the method execution log. To view the cause of the error in the log, chooseGoto ® Log ® Queue.

¡        CANNOT_READ_BUFFER: The tp program could not open the corresponding buffer file. For more information, see the SLOG log file.

¡        CANNOT_MODIFY_BUFFER: The tp program could not change the corresponding buffer file. For more information, see the SLOG log file.

 

ABAP_GENERATION

This phase generates the runtime objects for the imported Repository objects (ABAP source texts and screens). This phase may terminate for the following reasons:

¡        TP_INTERFACE_FAILURE: The tpinterface could not be called.

¡        TP_FAILURE: The program tp could not be executed. For more information, see the SLOG or ALOG log files.

¡        TP_STEP_FAILURE: The tp step could not be executed successfully. To view 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 have been generated that contained no syntax errors.

There may be various reasons for any remaining syntax errors:

§         Systems that have been developed for 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 choosingExtras ® Ignore generation errors, and continue the import of the queue. Choose Support Package ® Import queue.

¡        CANNOT_READ_BUFFER: The tp program could not open the corresponding buffer file. For more information, see the SLOG log file.

¡        CANNOT_MODIFY_BUFFER: The tp program could not change the corresponding buffer file. For more information, see 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 the obsolete versions of program code and program texts from the system. This phase may terminate for the following reasons:

-          TP_INTERFACE_FAILURE: The tpinterface could not be called.

-          TP_FAILURE: The program tp could not be executed. For more information, see the SLOG or ALOG log files.

-          TP_STEP_FAILURE: The tp step CLEARREPORTS could not be performed successfully. The cause of the error is in the corresponding log (PZ<yy><mm><dd>.<SID>). This log is in the log subdirectory of the transport directory. To display this file, execute treport RSPUTPRT, or call transaction AL11.

 

EPILOGUE

This phase completes the import. The system checks if the queue has been completely processed. If the queue has been completely processed, there should be no more transport buffer entries for the queue. This phase may terminate for the following reasons:

¡        TP_INTERFACE_FAILURE: The tpinterface could not be called.

¡        TP_FAILURE: The program tp could not be executed. For more information, see the SLOG or ALOG log files.

¡        QUEUE_STILL_IN_BUFFER: The queue has not been processed completely, since there are still incomplete Support Packages of the queue in the transport buffer.