# Import-/Export-Facility

## Exporting Data

The following overview describes the format descriptions possible for exporting data from Agile e6. The headlines give examples for the respective formats.

The export function is started with the menu userexit "edb_ief_put_dat_men".

### Item (ENT)

This format describes the export of simple entities as for example items, projects etc. All data records selected are written to the file with this format. It is possible to export all fields of this mask.

### Documents (TYP)

This format describes the export of type entities as for example document types. All data records selected are written to a file with this format. Type entities have fields containing two tables, the master table and the type table. With this format it is possible to export fields from both tables as long as they exist in the type-specific mask.

### Structure (STR)

This format describes the export of reference entities whereas the allocated entity must be of the same type as the father entity (e.g. item structures, document structures). For every selected data record in the father entity (e.g. item list) the related structure is opened and every position with this format is written to the file. It is only possible to transfer fields to this mask. If additional fields of the father entity are to be transferred, they have to be included in the mask.

### Item document allocation,
Item type reference (REF)

This format describes the export of general reference entities. It is possible to export any desired relationship contained in Agile e6. For every selected data record in the father entity (e.g. item list) the allocation list related is opened. For every allocated data record the fields of the father element, son element and if necessary the allocation are read out to the file. If fields of the document are to be read out when reading out item data this is enabled with this format type. The fields of the item list are defined in the father format, the fields from the document list (from the master table as well as from the type table) are defined in the son format. The fields of the reference entity can also be dropped that means this format has no field description . If the field description is called up from a relationship mask only the selected positions of the relationship is issued.

### Item external key entity (EKY)

This format describes the export of relationships which are not defined as DP relationships but via so-called key fields.

####
Example:

A text entity exists which contains all texts in a field. Every text is identified by a text number. Several texts can have the same text number. In the item management only the text number is carried on.

For each selected data record in the father entity (item) all data records of the son entity (text) which have the same key (text number) are read to the file. Any field desired of the father entity (e.g. item number) can be issued for any text.

The external fields are defined as follows: In both entity formats descriptions of the following type are entered for all external key fields:

<EDB-field name> allocated with @P to the file. This description must set the key field specification . In this format no other additional lines with @P or @PART_ID are allowed.

If other fields are to be external key fields it is possible to use @R, @V and @S.

####
Example:

The fields T_MASTER_DAT.TEXT_ID and T_MASTER_DAT.TEXT_VER are key fields for a text entity in the item management.
The fields T_TEXT_DAT.TEXT_ID and T_TEXT_DAT.TEXT_VER are key fields in the text entity.

In the father format the entry must be as follows:

EDB-field | key | EDB start | EDB End | file line
T_MASTER_DAT.TEXT_ID | yes | 1 | 5 | @P
T_MASTER_DAT.PART_ID |
| 1 | 15 | @L
T_MASTER_DAT.TEXT_VER | yes | 1 | 3 | @V
T_MASTER_DAT .PART_ID |
| 1 | 15 | 01

In the son format the entry is as follows:

EDB-field | key | EDB start | EDB end | file line
T_TEXT_DAT.TEXT_ID | yes | 1 | 5 | @P
T_MASTER_DAT.TEXT_VER | yes | 1 | 3 | @V
T_TEXT_DAT. TEXT_GER |
| 1 | 80 | 01

### Structure external key allocation

This format is a further development of the preceding format type. The text entity can now also contain texts from structure entities (e.g. in the item structure a field exists which allows a text position related.) This format allows only one text per bill of materials in case of ambiguity the first text to be found is used. Any field desired of the father entity and the external key entity can be issued to the bill of materials positions.

### History (NRF)

The history is structured in the same way as the item document allocation. But as the son entity is a naught entity, the son format need not to be defined.

### Aggregate reference (AGG)

The format type enables the export of where-used data. The definition and usage of the format corresponds to the REF format. The import must be carried out in the format types REF or STR.