Start of Content Area

Background documentation Recommendations for R3trans  Locate the document in its SAP Library structure

The following recommendations help you if you must use R3trans directly.


Use transport requests. They have significant advantages for the import.


Exporting objects using a transport request gives you the following advantages:


Note that the log file is always called trans.log , unless you specify otherwise. To redirect logging, use the option -w so that you can keep track of all errors that have occurred.

Transporting Between Different SAP Releases

R3trans is upward compatible. R3trans writes data using a standard SAP transport format. This enables you to export data with an old R3trans version and import data with a new version of R3trans . If you have any doubts on which version to use, contact the SAP hotline.

Transports between different databases or operating systems are not a problem either. When you transport between different SAP releases, this usually does not present any technical problems due to the upward and downward compatibility of R3trans , but logical inconsistencies can occur in such transports.

Unconditional Modes

Use unconditional modes very carefully. Transport according to the rules of the Transport Organizer and Transport Management System.


Using R3trans unconditional modes, it is easy to destroy work that has taken days or even weeks to perform.


If you have any problems with R3trans , refer to this documentation to check if the function you have used is exactly what you need. All known errors are stored in the SAP information system (Notes). In addition, you can contact the SAP hotline.