Export Data Dictionary (ttiex1280m000)

Use this session to export the contents of one or more package VRCs to sequential dump files.

You can export dictionary components, such as table definitions and domains, sessions, reports, menus, scripts, libraries, labels and SQL queries.

Exporting components through this session is useful, for example to transfer data dictionary components to a VRC on another server. For example: you want to transfer software from a VRC on a design or test server to a VRC on a "live" server that is used by the end users.

To import the dumpfiles that are generated by this export session into the target environment, use the Import Data Dictionary (ttiex1285m000) session.

Note: This session is meant for internal use only. It is not intended for the distribution of software to customers. Software deliveries to customers should be done in the form of a patch or, even better, a PMC (Product and Maintenance Control) solution. Refer to Patch Codes (ttiex4500m000) and PMC distributor procedure (OP) for more information.

To export components:

  1. Enter the settings for the export process in the Environment tab, e.g. the VRC from which components must be exported, the language code of the components to be exported and the directory on the LN Server where the dump files will be stored. Specify whether the export is Export based on Sessions. If so, you must specify a session range. Refer to the online help of the fields on this tab for more details.
  2. Only if the export is not Export based on Sessions: select the components you want to export in the Components 1, and Components 2 tabs. Select which types of dictionary and software components must be exported, and specify a selection range for each selected type.
  3. Optionally: specify selection ranges for additional components, such as SQL Queries and Customization projects, in the Components 3 tab.
  4. Click Export to start the export process.

The export process generates the following dumpfiles, depending on the content of the exported VRC:

  • dump.e: contains a list of abbreviations that are used to indicate the exported software component types. These abbreviations are used in the names of the dump files that contain the exported components. This file also contains the error messages for missing components.
  • dump.l: Contains the names of the exported components and a list of abbreviations that are used in the dump file's names.
  • dump <abbreviation> 01.Z. This is a compressed file containing exported software components. The abbreviation consists of an alphabetic character. Various files are generated, depending on the component selection for the export process. Examples of file names are dump d 01.Z (domains), dump f 01.Z (forms) and dump s 01.Z (sources). A list of the abbreviations used is stored in the dump.e file and the dump.l file.

If you want to send customizations to a customer, you can use the following value settings:

Package : <package code> range
VRC : <VRC customization>
Update : Yes
Compared with VRC: <VRC, on which the customization is based>
Based on Sessions: No

Field Information


The package codes of the VRC to be exported.

If you specify the same package in the Package From and Package To fields, the dumps are stored in the export folder. This is the folder that you specify in the Path Dumps field.

If you specify a range of packages, a sub folder for each package is created in the export folder.


The version code of the package VRC to be exported.


The release of the package VRC to be exported.


The customer extension of the package VRC to be exported.

Compared with VRC

If this check box is selected,, you must specify a package VRC in the next field. Only changed components, in comparison with that VRC, are exported. This is useful, e.g. when you want to deliver customizations, that are developed in a separate VRC, to a customer.

If you clear this check box, components from the underlying VRCs (i.e. the VRCs that are in the derivation path of the VRC to be exported), are also exported.


You want to export components from the tcB61O_a_cus1 package VRC. This VRC is derived from tcB61U_a_stnd and tcB61U_a_stnd is derived from tcB61_a. Suppose the following:

  • the Compared with VRC check box is selected and tcB61U_a_stnd is specified as "Compared with VRC". Only the changes in tcB61O_a_cus1, in comparison with tcB61U_a_stnd, are delivered. No software components are exported from tcB61U_a_stnd and tcB61_a.
  • the Compared with VRC check box is cleared. Software components of tcB61U_a_stnd and tcB61_a are also delivered, if they are not present in tcB61O_a_cus1.

The version code of the VRC to which the VRC to be exported is compared. See also: Compared with VRC.


The release of the VRC to which the VRC to be exported is compared. See also: Compared with VRC.


The customer extension of the VRC to which the VRC to be exported is compared. See also: Compared with VRC.


The language code(s), e.g. 2 - English or 3- Deutsch. Language dependent components, such as labels, messages, and questions, are only exported for the selected language(s).

Note: It is recommended to select only the default language (in most cases 2 - English) in this session. Components in other languages can be exported and imported via the LTS (Language Translating Support) utilities. See Export Language Dependent Data to XML - Wizard (ttadv8910m000) and Import Language-Dependent Data from XML - Wizard (ttadv8920m000).
Export based on Sessions

If this check box is selected, you can only specify a range of sessions to be delivered.

The system also delivers the forms, reports, charts, scripts, and tables that are required by the selected sessions.

For technical reasons, the system also delivers all other data dictionary components in the selected VRCs and languages.

In this case, software components of other packages also might be delivered, unless Only components of package itself = Yes.

If this check box is cleared, you can specify, for each type of software component, a range to be delivered. So in this case you can, for example, deliver forms without sessions.

Note: If Export based on Sessions = Yes, software components of other packages might also be delivered. The Compared with VRC = Yes flag is not applicable for these other packages. Therefore the software components of previous VRCs are always delivered ( Compared with VRC = No).
Sessions from file

If this check box is selected, a list of sessions to be exported must be present in an ASCII File. Only these sessions will be exported. The name of the ascii file can be filled in on File with sessions field.

If you select No, you can only enter a range of sessions in the Session (from / to) fields.

Create Components List

If this check box is selected, an ASCII file (dump.l) is generated. The file contains the names of all exported components and the code of the VRC from which the components were exported.

Only components of package itself

Only applicable if Export based on Sessions = Yes. If Export based on Sessions = No, this field is always Yes.

Yes. Only components of the selected package are exported.

No. Also components of other packages are exported, for example if a script uses messages of other packages, or if a table uses a domain of another package.

Errors to Printer

If this check box is selected, a report of the export process is printed. The report contains the names of the exported components and, if applicable, error messages.

Also Common Data

Select this check box to export common, non VRC-related, data for the selected package.

If this check box is selected, the common data specified in these sessions is exported:

  • Domains to be Displayed as Checkbox (ttgfd4520m000)
  • Display BMS Mask Data (ttadv4588m000)

The common data is only exported for packages other than tt.

Only select this check box if data was added or modified during the development process in the above sessions and the data must be transferred.

Sessions from Status

The status of the sessions that will be exported. Select the desired status from the list. You can use this field to select only a subset of the sessions within the specified range. For example: only sessions with status "Finished" must be delivered to a customer.

File with sessions

The name of the ascii file that contains the list of sessions to be exported. This field is only applicable if you selected Yes in the Sessions from file field.

Sessions must be listed in the file in the following way:




so: each session code (without package code !) on a separate line in the file. The sessions codes must be all sessions of the same package, as defined above.

Path Dumps

The directory, on the LN server, in which the dumpfiles will be stored.

Customization Projects

If this check box is selected, only data of the projects is exported to the data dictionary. This means that you can transfer the customization project to another Tools installation. If you want to transfer sessions based on a Customization Project, use the Software Components by Customization Part (ttadv1176m000) session.

In that session, on the Specific menu, choose Copy from project to Patch Code to create a patch that you can use to transfer the real sessions.


If this check box is selected, Tools also exports documentation details.

Release Notes

If this check box is selected, Tools also prints release notes.