# Import-/Export-Facility

## Importing Data

It is possible to read in data from a file into any entity desired. Different entity types exist for the different format types.
The import function is called up with the menu userexit "edb_ief_get_dat_men".

### Simple entities (ENT)

Simple entities as for example items and projects are described by an individual format. It is necessary to specify the entity name (e.g. EDB-ARTICLE) and the list mask related (e.g. EDB-ART-SLI). The key fields must be selected for the field description so that the data record to be read in can be searched for in Agile e6. Two virtual widgets are opened one for searching the data record and one for entering.

EDB-field | key | EDB Start | EDB Start | file line | file start | file start
T_MASTER_DAT.PART_ID | yes | 1 | 15 | 01 | 10 | 25
@LOGINFO |
| 1 | 15 | 01 | 10 | 25
T_MASTER_DAT.PART_NAME_GER |
| 1 | 30 | 01 | 26 | 55

### Type entities (TYPE)

Type entities are like simple entities described by a single format. For this the entity name (e.g. EDB-DOCUMENT) and the type name (e.g. DRAWING) must be specified. Only data of the same type can be read in (a different type has after all other fields and another mask).

### Structure entities (STR)

Structure entities (e.g. bill of materials) are data relationships of the same type (e.g. item-item relationship). The structure format describes the fields of the position in a structure. The position number (@INDEX) must be defined additionally. The position of the father item number and if necessary the version, revision and sheet number must also be defined. (@PART_ID, @VERSION, @REVISION, @SHEET_NO). For searching for the father item number and the son item number in Agile e6, the formats of the father and son must be defined.

In the relationship format the entry must look as follows:

EDB-field | key | EDB start | EDB end | file line | file start | file end
@INDEX |
| 1 | 5 | 01 | 1 | 5
T_MASTER_STR .POS_NO |
| 1 | 5 | 01 | 1 | 5
@PART_ID |
| 1 | 15 | 01 | 6 | 20
T_MASTER_DAT .PART_ID |
| 1 | 15 | 01 | 21 | 35
T_MASTER_STR.QUANTITY |
| 1 | 10 | 01 | 36 | 45

In the father format the key fields are defined:

EDB-field | key | EDB start | EDB end | file line | file start | file end
@LOGINFO |
| 1 | 15 | 01 | 6 | 20
T_MASTER_DAT.PART_ID | yes | 1 | 15 | 01 | 6 | 20

In the son format the entry looks as follows:

EDB-field | key | EDB start | EDB end | file line | file start | file end
T_MASTER_DAT.PART_ID | yes | 1 | 15 | 01 | 21 | 35

### Reference entity (REF)

Reference entity have the same structure as structure entities. In this case the allocated entity can be a different entity than the father entity (e.g. item document relationship). If the file has no position number, a position number is generated by he read-in program if "@INDEX" is entered in the column "file line" (for integer numbers the position number). It is then only allowed to read in a file once as otherwise the same relationship would be created several times.

Generally required is that for relationships the father and the son must exist. With a setting it is possible to decide if whether the father or son found last is selected or if the data record is rejected.

### Naught reference entity

Naught references are relationships between one entity (father entity) and a naught entity (for implementing a 1:n relation, e.g. history). In addition to the reference format a format for searching for the father element must be defined. If no position number exists in the file, it is possible that the read-in program can generate a position number. ("@INDEX" in the column "file line" for integer values)

### Classifications

This format type enables the classification of data that means that the data of an entity (e.g. item) can be assigned to a classification group. The data records must exist in the master entity. The classification can be exported with the format type "TYP"
The format requires a son format (ENT) containing the key fields of the master entity. The simplest case is a copy of the key field in the GTM format.