Errors in Support Package Manager Steps (SAP Library - Support Package Manager (BC-UPG-OCS))

Errors in Support Package Manager Steps

If an error is recognized in a step, the Support Package Manager stops processing the import until the error is corrected. You can find out the reason the transaction was stopped and in which step by choosing Status.

Error Types

The Support Package Manager displays the following types of error messages:

Consistency checks

A typical example is the step OBJECTS_LOCKED?. The Support Package Manager stops the import 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 step TEST_IMPORT. This step checks whether there are unconfirmed repairs to objects that need to be overwritten by the queue. The relevant objects are listed in the test import log.

Incorrect configuration of the Change and Transport System

Errors here often include not having the relevant authorizations for accessing files of the Change and Transport System, or using old versions of the tp or R3trans programs. Check the configuration of the transport tools by choosing Utilities ® Check transport tool.

A typical example is the step DISASSEMBLE. If <sid>adm does not have write authorization for the directory /usr/sap/trans/data (UNIX), the Support Package Manager stops at the step DISASSEMBLE with CANNOT_DISASSEMBLE_R_DATA_FILE.

The Support Package Manager requires that the Change and Transport System is configured correctly.

For more information on known problems, see the SAP Notes 97630 and 97620.

Known Errors

PROLOGUE

In this step, 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 step checks various requirements for importing a Support Package. This step 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

This step unpacks files from the appropriate EPS parcels and saves them to the transport 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 step may terminate for the following reasons:

CANNOT_SKIP_ATTRIBUTE_RECORD: The attributes could not be read in the OCS file. 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 OCS file is not in the EPS Inbox, probably because it has 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 OCS file 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 <sys>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.

For more information, see SAP Note 70752.

ADD_TO_BUFFER

This step places the queue in the transport buffer of your system. This step 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 step 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. For more information, see SAP Note 42379.

IMPORT_OBJECT_LIST

This step imports the object lists for the Support Packages in the queue into the system. This step 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.

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 step checks whether there are objects that are overwritten by the import, and that are still in unreleased requests. This step 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.

SCHEDULE_RDDIMPDP

This step schedules the transport daemon (program RDDIMPDP). This step 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. For more information, see SAP Note 11677.

ADDON_CONFLICTS_?

This step 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 step 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 Repository switch 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.

CREATE_VERS_BEFORE

This step 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 step 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.

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 as ALWAYS. 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

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

DDIC_IMPORT

This step imports the ABAP Dictionary. This step 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 step checks whether all modifications to ABAP Dictionary objects can be adjusted automatically.

RUN_SPDD_?

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

DDIC_ACTIVATION

This step activates the imported Dictionary objects. This step 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

This step imports inactive report source code and texts (only if this import method is chosen). This step 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 INACTIVE_IMPORT could not be executed successfully. The cause of the error is in the corresponding log (SAPZxxxxxx.<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 step imports all Repository objects and table entries. This step 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: 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.

XPRA_EXECUTION

This step executes the XPRAs and after-import methods. This step 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 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, choose Goto ® 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.

AUTO_MOD_SPAU

This step checks whether modifications can be adjusted automatically.

ABAP_GENERATION

This step generates the runtime objects for the imported Repository objects (ABAP source texts, screens). This step 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 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 choosing Extras ® 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 step prompts you to adjust your modifications to Repository objects by calling transaction SPAU.

EPILOGUE

This step completes the Support Package 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 step 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.

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.

CANNOT_RESET_FCS_FLAG: If there is an FCS Support Package (FFD) in the queue, the system is flagged as having the General Availability release after it is imported. This error indicates that the system could not be flagged.