SAP R3trans

Share this article :

General Information on R3trans

Use the version of R3trans which corresponds to the version of your R/3 System. However, different versions of R3trans are fully compatible with each other, because the data is transported in a standard format. Thus one can use different versions of R3trans for export and import. Transports between different databases or operating systems are not a problem either. When you transport between different SAP release levels, note that this usually does not present any technical problems due to the upward and downward compatibility of R3trans , but logical inconsistencies could occur in such transports.

Starting R3trans

R3trans is started as follows:

> R3trans
This is R3trans version 6.13 (release 640 - 11.05.06 - 13:04:42).
unicode enabled version

usage: R3trans []

The control_file describes what R3trans has to do.

The following options are possible:

-c f1 f2 : Copy file f1 to f2 with character set conversion.
-d       : DB connect. Test if SAP database is available.
-i file  : Import from file without using a control file.
-l file  : List the contents of file to the log file.
-m file  : List the contents of file to allow tp to create a cofile.
-t       : Test. All database changes are rolled back.
-u  : Unconditional modes. See below.
-v       : Verbose. Write more details to the log file.
-w file  : Log file. The default log file is 'trans.log'.
-x       : DB connect without access on any SAP table.
R3trans finished (0012).

DB connect. Test if SAP database is available.

> R3trans -d
This is R3trans version 6.13 (release 640 - 11.05.06 - 13:04:42).
unicode enabled version
R3trans finished (0000).

Return Codes

R3trans sets a return code which shows whether or not the transport has succeeded. Details on transports can be viewed in the log file. Other return codes are not set by R3trans itself but point to errors, such as segmentation faults. Return codes are as follows:

0: No errors or problems have occurred.

4: Warnings have occurred but they can be ignored.

8: Transport could not be finished completely. Problems occurred with certain objects.

12: Fatal errors have occurred, such as errors while reading or writing a file or unexpected errors within the database interface.

16: Situations have occurred that are normally not allowed.

Unconditional Modes

With the help of unconditional modes you can override the rules of the correction and transport system, if necessary. The following modes are available:


1: Ignore wrong status of a change request.
Normally only change requests with the status A (all locked), O (open) or R (released) are exported. If the transport succeeds, the change request is released by R3trans .

8: Allow direct selection of tables, otherwise forbidden.
Some tables are part of complex objects and generally cannot be exported alone.


1: Ignore the fact that this change request has already been imported into this system and import everything again. Usually only objects which have not already been imported successfully are imported again.

2: Overwrite originals.

3: Overwrite system-dependent objects.

6: Overwrite repaired objects.

8: Ignore the restriction resulting from table classifications and import all table entries into specified clients.


Related posts

ST03N: SAP Workload Monitor
AL12: Buffer Monitoring Tool
SM37: NO_MORE_SPACE: Can not create MTE: no more space
Steps to Create and Copy SAP Area Menu
© 2017 ITsiti. All Rights Reserved
Powered by KEEM