Troubleshooting (Transport)
Use
In the target system, check the transport in the enhanced view of the Transport Organizer (transaction SE01). If errors are displayed in the log, correct them.
The errors and their possible causes are listed below. Some of the errors should be corrected in the original system and others in the target system of the transport.
Procedure
Log for import postprocessing only displays the information Error occurred in object <xyz>
Possible Cause |
Procedure |
Where? |
The log displays the first object in the list that is processed when the after-import function module is called. This object need not necessarily be the object in which the error occurred. More information: SOBJ: Transportable Objects, Section Methods |
Expand the log. Navigate to the location where the error message occurred. The actual error is displayed here in its context. |
In the target system |
The log for import postprocessing contains messages that indicate that objects are missing
Possible Cause |
Procedure |
Where? |
The transport request is inconsistent. More information: Object Dependencies and Consistency |
Look for the missing objects on transport requests using the tools of the Transport Organizer (transaction SE03). If the missing object is on another request, import it first. If the missing object is not on a request, collect it and the incorrect object on a request and transport it. Do not import the original request again. Create a merge transport for the consolidation if necessary. More information: Technical names of the object types: Transportable Object Types |
In the original system |
A different package is assigned to the missing object than to the dependent object. |
Change the package assignment. Then transport the missing object. More information: Changing Package Assignments |
In the original system |
The DataSource is not active in the source system. |
First import the DataSource in the source system (object type OSOA) and replicate it to the BI system. You can then import the DataSource-dependent BI objects.
If the replication of the DataSource is on the BI transport request, replication is not required.
You must first import the OSOA objects separately, even for DataSources of the Myself system. |
In the target system |
The object was imported for the wrong source system. |
Define the correct target source systems by maintaining the view V_RSLOGSYSMAP. More information: Defining the Target Source System |
In the target system |
Objects are deleted during import postprocessing although they should have been imported
Possible Cause |
Procedure |
Where? |
The object was transported as a deletion. You can see this from the piece list of the request in that the objects to be deleted are marked with a deletion indicator. |
Make sure that the object to be transported is active. When delivering BI Content, make sure that the delivery or shadow version exists. |
In the original system |
The request was included in a mass import and the object is in more than one request. |
Import the requests individually or create a merge transport by merging the object lists of the requests. |
In the target or original system |
Objects were not activated or not found (especially process chains and DataSources)
Possible Cause |
Procedure |
Where? |
The client-dependent parts could not be activated because the transport destination is incorrect or missing. |
Maintain the correct transport destination: More information: Importing Client-Dependent Objects |
In the target system |