FAQs on OCS (Recommendations for error scenarios)

1. What general rules should I take into account before importing Support Packages?

Since the standard transport function is also used when you import Support Packages, you should first refer to the recommendations that apply to this function (system time of minimal work load, tp and R3trans current, ... from LC 556734). In addition, the current version of the SPAM should also be installed. When importing Support Packages, refer to the corresponding note provided for every release for details on known problems (for example, 97629, 97630 and 173814).


2. During the import, an error was reported which I have now eliminated - how do I proceed?

If the import terminated with an error reported via the SPAM transaction, you can nearly always repeat the phase once you have eliminated the error. To do this, you simply have call the SPAM transaction again and select the import button on the screen. Since the last successfully completed step of import is stored in status tables, the SPAM can be started again with the incorrect phase. As of Version 0031 of SPAM, this also applies to a termination in the main import.
However, if import terminates due to a power failure during the import process, the incomplete import can cause inconsistencies in various programs and transactions. In these cases, it is often impossible to start the SPAM transaction for Basis Support Packages. Send a message to the SAP support team to have the error analyzed.

3. The import terminates in the TESTIMPORT step with an error RC=8. (I)

First, please check the further information which are reported for this error in the log file of the Support Package. Should here a row as "R3TRXXXXYYYY was repaired in this system, is not overwritten" stand, at least a request in which a part of this full cost-object YYYY is edited and that is not released exists. Please you search from that how in note 42379 described the corresponding request. After the release you can repeat the importing of the Support Packages simply.


4. The import terminates in the TESTIMPORT step with an error RC=8. (II)

First check the additional information reported for this error that is contained in the Support Package log file. If this contains a line such as "Function XXXX (YYYY ZZ) does not fit in the existing function group ((AAAA BB)) ", an incorrect Support Package queue may have been created. You should therefore check whether the selected Support Package queue is correct for your release as described in the above note listed under point 1. Changing the queue in the step TEST_IMPORT is straighforward. To do this, use transaction SPAM to go to EXTRAS -> RESET STATUS-> QUEUE to define the correct queue. Once the queue is correctly defined, refer to the information in note 199619.


5. The import terminates in the ADDONCONFLICT step with an error.

This termination only occurs if the objects of the Support Package queue that you want to import are checked on already installed add-ons and the required add-on CRTs are not included in this queue. You should therefore reset the queue with transaction SPAM with EXTRAS -> RESET STATUS-> QUEUE and also incorporate the required CRT for the add-on reported in the error text. The error should no longer occur when you rerun the import.


6. The import terminates during/after the DDIC_IMPORT step - can I reset the queue again from here?

Resetting the queue is no longer possible as of step DDIC_IMPORT because objects have already been imported into the system at that stage. For this reason, the relevant field for resetting is grayed out in the SPAM transaction. Resetting the queue only resets the status of the last successful import step for the SPAM the objects already imported in the system are not rolled back!


7. Can I also import the Support Packages directly with the tp?

This procedure is not generally recommended. This is because the attributes of the Support Packages are not used during the direct import and the Support Packages may be imported in the wrong sequence as a result. All additional steps contained in the SPAM that are required for the modification adjustment, for example, are not executed.


8. After receiving an import error message and eliminating the error, I want to continue importing the queue but get a tp error message with "RC=152"?

This tp return code means that the tp did not find any work. This is because, for example, the import queue was changed by a cyclic tp import call via cron-jobs so that the import cannnot be continued using SPAM. In this case, you should send a message to the SAP support team to check and continue the import process. You should also refer to note 326405 to identify and eliminate the error.


9. After importing the Support Packages, I see the hourglass displayed for a large number of objects what can I do?

These objects are recreated in the corresponding system after you import objects via a normal transport as with as a Support Package. This occurs automatically with every first call and is therefore not an error. If you wish to automatically create Support Packages objects, you can select the following option in the SPAM transaction under EXTRAS -> SETTINGS -> ABAP/SCREEN GENERATION ALWAYS. However, this may increase the length of time required for the import and as part of importing the Support Package, this may stop if an error occurs during the import. However, you can deactivate the generation when continuing the import by setting the following option after a generation error: EXTRAS -> IGNORE GENERATION ERRORS.