Check Transport Tools tp and R3trans

The transport tools tp and R3trans must work correctly when importing a queue. If errors occur here, the system shows the following error message: TP_CANNOT_CONNECT_TO_SYSTEM. The cause is usually an error in the system configuration of the transport system in the Transport Management System (transaction STMS). You can call a detail check for more precise information on the errors and the possible causes. Choose  Check Transport Tool Utilities for this. Solve the error and continue the import.

Check Minimum Versions of Transport Tools tp and R3trans

Some functions of the import tools and the OCS packages themselves require minimum versions of the transport tools tp and R3trans. If the required minimum versions of the transport tools are not installed, the system displays this in a dialog window. Load at least the minimum required versions (or newer) of the tools from the SAP Service Marketplace and install them (see SAP Note 19466). Then continue the installation process.

Check User DDIC Status

The system executes individual import steps under the control of the user DDIC. For this the user DDIC must exist and not be locked. If this is not the case, the system shows a message that informs you how you can solve the problem. Follow the instructions. Then continue the installation process.

Check Open Data Extraction and V3 Update Requests

If changes are made to DDIC structures by an import, it is possible that open data extractions and V3 update requests can no longer be processed. The processing must take place before the Import 2 module is started. For more information on these data extraction requests, see 1081287, 1083709, and 328181.

If the system finds open requests, it shows them in a dialog box and cancels the import process. You either have to process the open requests (or not) before continuing with the import depending on whether you have defined the import tool to execute the processing of the Import 2 module immediately or start manually in the start options. If you have chosen manual start the Import 2 module you can first ignore this warning message with the Skip pushbutton.

Check the Transport Requests Still to be Imported in the Transport Management System (TMS)

To avoid problems, only import transport requests into systems that have the same system status as the installed software component versions (including Support Package status) as the export system at the time of the export. This checks if there are transport requests in the import queue of the TMS that are to be imported before importing the package queue. If this is the case, the system displays the transport requests in a dialog box. You can jump directly to the TMS using the TMS - Import Queue pushbutton and start the import of the transport requests.

If you are sure that the transport requests that are still to be imported are independent from the system status and the OCS packages that are to be imported, you can ignore the check with the Skip pushbutton and continue with the import.

Check for Note Correction to be Implemented Before Import

It is possible that OCS packages can only be imported after specific note corrections have been implemented in the system. For example, this makes sense to avoid import errors as a result of known and corrected software errors. If this is the case, the system lists the SAP Notes to be implemented in a dialog box. You can use the Note Assistant pushbutton to jump straight to the Note Assistant and implement the specified SAP Notes.

Check for Open Conversion Requests in the DDIC

When importing transport requests, table conversions and requests for creating table indices can be triggered which can be canceled for different reasons. Since such requests are also processed when importing OCS packages and can then cause serious problems, they have to be processed or removed before the import.

If such requests exist, the system displays the affected objects in a dialog box. To check the specified objects, use the DDIC tools of transactions SE11 or SE14. Either process the open conversion requests completely or, if this is no longer necessary, delete them.

Check for Open Workbench Requests

If objects that are also changed by the OCS Packages to be imported were changed locally in the system, this change must be completed, that is, the related Workbench change request must be released. Only this way can you ensure that local changes and OCS Package changes do not collide and that a modification adjustment is possible.

If objects from the OCS packages to be imported are still locked in open Workbench requests, the system displays them in a dialog box. By double-clicking a request you can branch directly to the request display and release the request directly, as long as you have the required authorization and are logged on in the relevant client. You can continue with the import when all open Workbench requests are released.