Batch Versus Interactive EDIFACT Messages Print this Topic Previous Page Up One Level Next page

Home >  Data Sources and Targets > EDI > UN/EDIFACT >

Batch Versus Interactive EDIFACT Messages

MapForce supports mapping data to or from both batch and interactive UN/EDIFACT messages. In other words, the UN/EDIFACT component in MapForce provides the necessary structure required to read or write syntactically valid UN/EDIFACT format files (meant for either batch or interactive interchange). Also, some basic validation and auto-completion rules are enforced when reading or writing UN/EDIFACT format files, as further described in this documentation. Note that MapForce does not actually transmit files between parties that take part in the UN/EDIFACT interchange process; the role of MapForce is to generate such files or convert them to other formats.


There are no special requirements in MapForce to map data to or from batch EDIFACT messages. However, in order to map data to or from Interactive EDIFACT messages, the following requirements apply:


1.MapForce 2018 or later is required.
2.The MapForce configuration files required for supporting Interactive EDI messages must be installed separately. The installation file can be freely downloaded and installed from the Altova MapForce Libraries page ( Once you do this, the required collections and message types become available on the "Browse EDI Collections" dialog box illustrated below.


To add to the mapping either a batch or an interactive UN/EDIFACT component, select the corresponding collection from the "Browse EDI Collections" dialog box. To open this dialog box, run the Insert | EDI menu command (or click the Insert EDI File btn_insert_edi toolbar button), see also Adding EDI Components to the Mapping.


Browse EDI Collections dialog box

Note:On the dialog box above, the suffix "INTERACTIVE" denotes a collection applicable for Interactive EDIFACT structure, for example "EDIFACT.D.2016A.INTERACTIVE". Collections applicable to batch structure include only the UN/EDIFACT directory version in their title, for example "EDIFACT.D.2016A". The same convention applies to the configuration directories (collections) available in the EDI configuration folder of MapForce (C:\Program Files\Altova\MapForce2019\MapForceEDI\).


The structure of UN/EDIFACT batch files is different from that of files meant for interactive interchange. Therefore, an EDIFACT component in MapForce can be either batch OR interactive (and thus include either batch OR interactive messages), not both simultaneously. Likewise, the validation and auto-completion rules differ for both scenarios, as further described in the following topics:


UN/EDIFACT Validation Rules (Batch)
UN/EDIFACT Auto-Completion Rules (Batch)
UN/EDIFACT Validation Rules (Interactive)
UN/EDIFACT Auto-Completion Rules (Interactive)

© 2019 Altova GmbH