Table Relations (Import) (daxch0521m000)

Use this session to list the available table relations between logical ASCII files and LN tables per batch in an exchange scheme.

Each table relation is identified by a sequential number.

Note: Use multiple table relations to link one ASCII file to more than one LN table or to link one LN table to more than one ASCII file.
Note: If you have started this session by zooming, you can only find and select a record. The relation on field level is created in the Field Relations (Import) (daxch0522m000) session.

Actions/Reference menu

These options are available:

Field Relations (Import)

Creates or changes table field relations for an import.

(De)activate Table Relations

Activates or deactivates a range of import table relations per batch.

Field Information

Exchange Scheme

The exchange-scheme code.

Note: The exchange scheme is created in the Exchange Schemes (daxch0501m000) session.

The batch code in an exchange scheme.

A batch is created in the Batches (daxch0104m000) session.

Table Relation (Import)

A sequential number that identifies the table relation. It makes the table relation unique in the batch.

Sequence Number

The sequence number of the table relation in the batch during an exchange process.

The sequence number of the table relation does not have to be unique. If two relations have the same sequence number, the relation with the lowest table relation number is processed first.


The code of the table in LN that is filled with data from an ASCII file during an import procedure.

Use multiple table relations to write data from more than one physical ASCII file to one LN table.

The LN table name is defined by the package code, a module code and a table number. For example, tcibd001.


The code of the ASCII file that contains data that is transferred to a LN table in an import procedure.

To copy fields of an ASCII file table automatically it is necessary that the code of the ASCII file is the same as the code of the LN table. This is an option if you do not have a data definition file of the ASCII file.

Note: The ASCII file code represents the logical ASCII file and it is created in the ASCII Files (daxch0102m000) session.

ASCII File Name

The name of the physical ASCII file.

The entered file name is an extension on the default relative path. The default relative path is defined in the Path forASCII Files field under Paths on the General tab in the Exchange Schemes (daxch0101s000) session.

  • This path can also be an absolute path.
  • The maximum length of the file name is 11 characters.
  • You do not have to generate the exchange program again if this field is changed.


If this check box is selected, the table relation is active and it can be used for data processing in a regular exchange process.

If this check box is cleared, the table relations are kept for reference purposes but they are not used during a regular exchange process.

This check box does not have to be selected for all table relations in a test run of the exchange process. One table relation is enough.

Note: You do not have to generate the exchange program again if this field is changed.
Import via Data Access Layer

This check box indicates whether the Data Access Layer (DAL) is used for the current table. By using the DAL, an import carries out all the constraint checks, integrity checks and side effects, such as updates on other tables, that are programmed into the DAL. This guarantees database integrity, saves programming time, and avoids the errors that can occur in condition scripts.

Refer to Import using the Data Access Layer (DAL) for details.

Table Relations Text

If this check box is selected, additional information is added to the table relation. The text is generated in the text editor.