Export

You can use the following parameters in control files:

• CLIENT = DEFAULT | ALL | <client>

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

  Note

  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. The following options are available:

  • 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 by 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.

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

  See also: Transporting Language-Dependent Data

• RECCLIENT=XXX

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

  XXX can have the following values:

  • nnn: Logging is only performed in client nnn for client-specific tables.
  • mmm,nnn,ppp,...: Logging occurs for the clients listed here for cross-client tables.
  • ALL: Logging always occurs for all clients for client-specific tables.
  • OFF: No logging (default)
  Note 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 SAP Note 1916 .

• SQLTRACE = YES | NO

  The default value is NO.

  With this option, you activate a trace for an R3trans run 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).

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>]

  You can specify the following objects 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.

  Example SELECT * FROM THLPF WITH KEY SAPMS01*