Imports are generally started by tp (transport control program), where R3trans is called indirectly. The control file for an import has the following structure:

# < options >
# < selections >

If you use the default options for the import, you do not need a control file. You can perform the import directly with the following command:

R3trans -i <file>

Import Options

By using the following parameters, you can specify in the control file how an import should be performed:

  • BUFFERSYNC = YES | NO: The default is NO.

This parameter controls whether R3trans synchronizes the buffer for the imported data. This synchronization only affects the data actually imported. Synchronization is for single objects (individual tables, reports, etc.). No complete buffer classes are synchronized.


For all language-specific objects, R3trans automatically selects the appropriate conversion table for the language concerned. If you, for example, want to transport a Polish or Czech text, a conversion table according to LATIN-2 is used.

To deactivate the automatic character set conversion and to convert everything according to LATIN-1, use the following R3trans option:


Some texts cannot be converted correctly because they are not stored in language-dependent objects (for example, comments in ABAP programs). If you also want to convert these types of texts correctly, you can specify explicitly which character set is to be used for conversion:

charset = XXX

Replace XXX by one of the following values:


You can also make these settings in the transport profile.

<SID>/r3transoptions = charsetadaption=no;charset=eeuropean

  • CLIENT = DEFAULT | ALL | <client>: The default is ALL.

By default, the import always takes place in the same client as the export. This option allows you to import into other clients. See R3trans and Clients.

  • SAFEANDSLOW = YES | NO : The default is YES.

This parameter enables you to switch off the R3TRANS " Arrayinsert ". This enables R3trans to better manage data inconsistencies. The disadvantage is that R3trans works much more slowly. Use this parameter only if it is specifically recommended by SAP for resolving a particular problem.


See also: Transporting Language-Dependent Data

  • SQLTRACE = YES | NO: The default is NO.

This parameter enables you to activate a trace for a database statement for an R3trans run. You can use this trace to determine the causes of performance problems during transports. This database trace is currently only implemented for Oracle ( tkprof ).

  • SUBSTITUTE <hex1> <hex2>

This parameter activates the special character set conversion for single characters, if the default conversion is not sufficient (for example, if problems occur with umlauts, see Automatic Character Set Conversion with R3trans).


R3trans automatically adapts its main memory requirements during import to the main memory available. This means the main memory requirements are independent of the volume of tables to be transported.

You can limit the size of main memory area to be used for merging the tables by using the option tablecachesize .

Default values for this parameter are:

    • 16000000 for AIX and OSF1 (DEC-UNIX) due to the undefined behavior for the internally used function realloc() . If there is enough main memory, you can increase the value.
    • 16000000 for OS400. Do not increase this value.
    • -1 (= infinite) for all other platforms.

Options for Selective Imports

You can perform a selective import of certain data in an import file. SAP recommends importing complete files. Selective imports are only useful for restoring backups.

The data file is imported completely by default. You can import specific parts of data by specifying include or exclude lists in a control file.

  • EXCLUDING <string1>, <string2>, ...:

With this specification, you can exclude certain objects (reverse logic). During the upgrade, for example, you can exclude table entries the first time in order to import them after the activation.

  • INCLUDING <string1>, <string2>, ...:

Only data whose object directory entry (TADIR) starts with <string> is imported. Typical strings are R3TRTABL , R3TRPROG , etc.

The control file for a selective import appears as follows:

file = ...
excluding "R3TRCNTD", "R3TRTABU"

Test Import

Before an import, you can check if it will succeed or not. The test import checks the rules of the Transport Organizer and transport system.

This option lets you identify problems before you perform the actual import and can solve problems in advance.

The control file for a test import has the following structure:

file = ...

File Contents

If you want to create a table of contents for a file, use the following control file or the R3trans command:

  • listonly
    file = ...
  • R3trans -l <file>