Background documentationErrors During Support Package Manager Phases Locate this document in the navigation structure

 

Error Types

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  .

Support Package Manager displays the following types of error messages:

  1. Support Package Manager Security 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.

  2. Error messages of 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.

  3. Incorrect configuration of the Change and Transport System

    Errors here often include not having the relevant authorizations for accessing files in 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 DISASSEMBLE phase. If <sid>adm does not have write authorization for directory /usr/sap/trans/data (UNIX), Support Package Manager stops at the DISASSEMBLE phase with CANNOT_DISASSEMBLE_R_DATA_FILE.

    Support Package Manager requires the Change and Transport System to be configured correctly.

For more information on known problems, see the Notes referred to for your release in Note 97620.

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 onto the system's database.

  • QUEUE_NOT_EMPTY: The tp buffer contains incompletely processed OCS requests. You can display these requests with the following tp command: tp SHOWBUFFER <SID> -D SOURCESYSTEMS= TAG=SPAM. You can continue the editing of the queue when these requests have been completed or deleted from the tp buffer.

DISASSEMBLE

In this phase, files from the corresponding EPS parcels are unpacked and stored in directory /usr/sap/trans/data (UNIX). It generates the command files (cofiles) from the accompanying files and saves them to directory /usr/sap/trans/cofiles (UNIX). It may terminate for the following reasons:

  • CANNOT_DETERMINE_EPS_PARCEL: The EPS parcel is not in the EPS Inbox, because it may have been deleted. You need to download the relevant 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 report RSPARAM to check the settings.

  • CANNOT_DISASSEMBLE_R_DATA_FILE: 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 while transmitting a 20K block from the EPS Inbox to directory /usr/sap/trans/data (UNIX).

  • CANNOT_CREATE_COFILE: The cofile could not be created from the relevant data file. One of the possible causes for the error is that <sid>adm does not have write authroizations for the /usr/sap/trans/cofiles (UNIX) directory. Check whether the data file has been created. If it has not been created, check that the option Create New Data File is activated in the Settings.

  • EPS_FILE_TO_OLD: An R3trans data file exists in the transport directory which is newer than the one that is to be unpacked from the EPS package. Do not import the obsolete version. You need to proceed as follows:

    1. Delete the current queue.

    2. Download the newest version of the relevant OCS package.

    3. 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 directory /usr/sap/trans/log (UNIX).

    MODIFY_BUFFER

    This phase prepares the transport buffer so that the subsequent import phases can be processed correctly. 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: An unsuccessful attempt was made 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: 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 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 error in the log of the test import.

You can skip test import errors and continue the import process by choosing ExtrasIgnore Test Import Errors. 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 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 continuing importing the Support Packages.

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

    <user name>

    Trigger 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 coding, screens, and DDIC objects). It 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, read 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 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: The program 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: The program tp could not be executed. For more information, read 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: The program tp could not be executed. For more information, read 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 relevant log (SAPBxxxxxx<SID>). This log is in subdirectory log in the transport directory. To display this file, run report RSPUTPRT, or call transaction AL11.

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: The program 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 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  .

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: The program 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 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 relevant logs can be found in the log overview under 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):

    tpStep 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, run 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 tp program could not change the corresponding 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: The program 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: The program 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 find the cause of the error, read 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, read the SLOG log file.

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

ABAP_GENERATION

This phase generates the runtime objects for the imported Repository objects (ABAP source code and screens). It 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, read 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 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.

    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 importing the queue. Choose   Support Package   Import Queue  .

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

  • CANNOT_MODIFY_BUFFER: The tp program could not change the corresponding 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: The program 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. The cause of the error is in the relevant 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_INTERFACE_FAILURE: The tp interface could not be called.

  • TP_FAILURE: The program 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 from the queue in the transport buffer.