Export  

Exports are usually started within the SAP system (Transport Organizer) or from tp (transport control program), with R3trans being called indirectly.

The control file for exports has the following structure:

export
# < options >
# < selections >

This entry shows a single step. A control file can contain several steps.

Export Options

You can use the following parameters in control files:

●      CLIENT = DEFAULT | ALL | <client>

The default value for the client to export from is 0.

Cross-client data is also exported.

This option allows you to perform the export from clients other than 000 or from all clients.

●      COMPRESS = YES | NO | C | D | P | L

The default value is L.

You can export compressed data. The data is then decompressed automatically at import time. There are the following options:

-          D: Simple compression, where successive bytes with the same value are grouped together

-          P: Compression of common prefixes of successive data entries

-          C: A combination of D and P

-          L: Compression according to Lempel Ziv (default)

●      FILE = <file name>

The default value is trans.dat in the current directory. The data is exported to this file.

●      LANGUAGE = <languages>

Objects belonging to class TEXT or entries from language-dependent tables are only exported if they are in one of the languages specified here.

This parameter is case-sensitive. Lowercase letters in the language vector are not converted automatically into uppercase letters.

See: Transporting Language-Specific Data

●      RECCLIENT=XXX

You can use this R3trans option to activate writing of table logs

XXX can have the following values:

○       nnn: Logs are written for client-specific tables in client nnn only.

○       mmm,nnn,ppp,...: Logs are written for client-specific tables in all clients listed.

○       ALL: Logs are written for client-specific tables in all clients.

○       OFF: No logs are written (default setting)

Logs are only written for tables with the correct designation in ABAP Dictionary (especially Customizing tables).

For further information, particularly on evaluating these logs, see Note 1916.

●      SQLTRACE = YES | NO

The default value is NO.

With this option, you activate a trace for an R3transrun for a database statement. You can use this trace to find the cause of performance problems arising during transports.

This database trace is only implemented for Oracle (tkprof).

Selections for Export

There are various methods of specifying which data to export. Normally this is done using change requests (command files). If this is not possible for whatever reason, you can specify selections directly.

Control File Parameters for Control Files

●      USE COMMANDFILE<change request>: <change request>

Change request that has been maintained using Transport Organizer

A single step can contain several entries of this type.

●      USE DEVCLASS <devclass>

R3trans creates an object list DEVC<devclass> with all objects belonging to this development class and exports these objects.

A single step can contain several entries of this type. This type of selection is especially suited for transporting complete development classes.

Direct Selection

For special purposes (such as repairs), you can export without command files by specifying direct selections of objects in a control file:

●      SELECT <object> [<whereclause>]

The following objects can be specified directly: CMDFILE, CUA, DATAELEMENT, DOCUMENTATION, DOMAIN, DYNPRO, REPORT, SQLTABLE, TABLE.

In <whereclause>, you have the following options:

·         WHERE NAME = <name>, where <name> can also end with “*” (for generic names)

·         WHERE NAME BETWEEN <name1> AND <name2> for selecting an interval

●      SELECT * FROM <tabname> WITH KEY <generic key>

This command lets you select records from a table with a generic key.

SELECT * FROM THLPF WITH KEY SAPMS01*