Symptom
There are two different cases:
- The export of a transport request finishes with return code 14.
In the "Main Export" log file you can find different errors, for example:
######################################
Main export
Transport request : <SID>K<nnnnnn>
System : <SID>
tp path : tp
Version and release: xxx.xx.xx.xxx
R3trans.exe version x.xx (release xxx - dd.mm.yy - hh:mm:ss).
unicode enabled version
===============================================
....
Incomplete log ==> R3trans terminated for unknown reasons
Incorrect export. Request not imported.
Main export
End date and time : <DateTime>
Ended with return code: ===> 14 <===
######################################
As mentioned above, you can find different errors in the log file, but it always ends with the return code 14:
Ended with return code: ===> 14 <===
- The import of a transport request finishes with return code 255.
The Import log finishes with the following message:
Main import
End date and time : <DateTime>
Ended with return code: ===> 255 <===
######################################
Read more...
Environment
- SAP Kernel 7.20
- Oracle database
- Windows operating system
Keywords
TP195, TP 195, TP200, TP 200,Export of transport request finishes with return code 14 , KBA , BC-CTS-TMS , Transport Management System , BC-DB-ORA , Oracle , Bug Filed
About this page
This is a preview of a SAP Knowledge Base Article. Click more to access the full version on SAP for Me (Login required).Search for additional results
Visit SAP Support Portal's SAP Notes and KBA Search.