Exports are usually started within an SAP system (Transport Organizer) or fromtp (transport control program), where R3trans is called indirectly.
The control file for an export has the following structure:
This entry shows a single step. A control file can consist of several steps.
You can use the following parameters in control files:
The default is 0. The export is performed from client 0 by default.
Cross-client data is also exported.
The option allows you to perform the export from clients other than 000 or from all clients.
The default is L.
You can export compressed data. The data is automatically unpacked at import. There are the following options:
The default is
Objects belonging to the class TEXT or entries from language-dependent tables are only exported if they exist in one of the languages specified here.
With this parameter, not the differences in upper and lowercase spelling. Lowercase letters in the language vector are not converted automatically into uppercase letters.
You can activate table logging with this R3trans option.
XXX can have the following values:
Only the tables marked appropriately in the ABAP Dictionary are logged (particularly Customizing tables).
For further information, particularly on evaluating these logs, see Note 1916.
The default is NO.
With this option, you activate a trace for an R3trans run for a database statement. You can use this trace to determine the causes of performance problems during transports.
This database trace is only implemented for Oracle (tkprof).
Selections for Export
There are various methods for specifying which data is to be exported. Normally this is done using change requests (command files). If this is not possible for any reason, you can also specify selections directly.
Control File Parameters for Control Files
Change request that was maintained by the Transport Organizer
Several entries of this type may also be contained in a single step.
R3transcreates an object list DEVC<devclass> with all objects belonging to this development class and exports these objects.
Several entries of this type may also be contained in a single step. This type of selection is especially suited for transporting complete development classes.
For special purposes (such as repairs), you can export without command files by specifying direct selections of objects in a control file:
The following objects can be specified directly:
You have the following options in<whereclause>:
This command lets you select records from a table with a generic key.
SELECT * FROM THLPF WITH KEY SAPMS01*