SAP Common Transport Errors &

Troubleshooting
1. The log for import post processing contains messages that indicate that objects are
missing
Solution- 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.
2. Objects are deleted during import postprocessing although they should have been
imported
Solution- 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
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.
3. Objects were not activated or not found (especially process chains and DataSources)
Solution- The client-dependent parts could not be activated because the transport
destination is incorrect or missing.
Maintain the correct transport destination:
4. troubleshoot when a transport is running for unusually long duration and not getting
completed or terminated
Solution- Go to transaction STMS_IMPORT and identify the transport which is running
since a long duration.
In the below screenshot, transport with the truck symbol is the long running one

Issue could be due to following reasons :

1)

Non availability of space to perform the operation (i.e filesystem or

tablespace is 100% full)
Solution :

Check out if any of the filesystems (like sapmnt, oraarch etc) of the Central
Instance, Database and application servers is 100% full. If so, please add necessary
space, which resolves the issue automatically and completes the import of transport.

Also, check out tablespaces fill levels. If autoextend is off and tablespace is
100% full then add sufficient datafiles, which resolves the issue

2)

RD* jobs are not running in SAP system

Solution :
Check out in SM37 whether RDD* jobs(RDDIMPDP, RDDIC3L, RDDVERSL etc) are
running or not. If not, please make sure they are scheduled and perform the import of
the transport again

3)

Update got deactivated

Solution :
Checkout in SM13 whether update is active or not. If it is not active, activate it and
import the Transported to Production System.

4)

There are no free background workprocesses

Solution :
Check in SM50 whether all background workprocesses are in running status. If so, you
will need to wait for the free background workprocess to run RDD* jobs to complete
the import of the transport. To avoid this issue in future you may increase the number
of background workprocesses

Transport is not getting terminated. How to do terminate?

1) If you are unable to terminate a transport which is running, goto SM50 and identify
the pid of the transport process. Try to cancel the process---> with core or without core
2) If it is not getting terminated from SAP level, then goto Oslevel and kill.
Command for the same in AIX or HP-UX is kill -9 <PID>

What are common transport errors?

Return code (4) indicates imported ended with warning.
Ex:
1. Generation of programs and screens
2. Columns missing and Rows missing.
Return code (8) indicates not imported ended with error
Ex:
1. Syntax error.
2. Program generation error.
3. Dictionary activation error.
4. Method execution error.
Return code (12) indicates import is cancelled.
Ex:
1. Import is cancelled due to object missing.
2. Objects are not active.
3. Program terminated due to job? RDDEXECL? is not
working.
Return code (16) indicates import is cancelled.
Ex:
1. Import cancelled due to system down while importing.
2. Import cancelled due to user expires whileimporting
3. Import cancelled due to insufficient roles.