Contents - 6.3

Talend Data Mapper User Guide

Talend Big Data Platform
Talend Data Fabric
Talend Data Management Platform
Talend Data Services Platform
Talend MDM Platform
Talend Real-Time Big Data Platform
Design and Development
Talend Studio

This section describes the contents of the EDI specification project.

Project Name

The name of the project is the EDI standard name, followed by the version name, like X12_4010. If there is any additional qualification to the version it appears after the version name, like X12_4010_HIPAA.


The transactions are contained in a folder called Transactions.

Envelopes (Interchange, Functional Group)

The Envelopes folder contains a structure that defines the interchange. This is used if the interchange segments (ISA, GS, GE, IEA) are required. To use this, inherit from it in your own project (create a structure that customizes it). Then, in your custom structure, expand it until you see the Transaction element. You can then drag your custom transaction structure (like the 270-A1 for example) to the Transaction element which will cause it to inherit at that point. Then the custom interchange structure is ready to use.

Control Number Generation and Mapping

For X12 EDI, the control numbers (ISA13/IEA02, GS06/GE02, ST02/SE02) are automatically generated if they are not otherwise mapped. The automatic generation is handled for each element separately. So, for example, you can map the interchange control numbers (ISA/IEA) and use the automatic generation for the functional group (GS/GE) and transaction set (ST/SE) control numbers.

The interchange control number (ISA13/IEA02) is generated using the same logic as the GetSequenceFromLocalFile function and using the path ${user.home}/odtEdiControl.txt which is used to store the next sequence number in the local file system. If you wish, you can map the control number to another function, like DatabaseLookupAndUpdate to have more control over its generation.

The functional group control number (GS06/GE02) is generated by prepending the interchange control number multiplied by 100 and adding the sequence number of the group, starting with zero. So if the interchange control number is 17, the first group would have a control number of 1700. This is done because the X12 functional acknowledgment transaction (997) requires acknowledgment by uniquely identifying the functional group.

The transaction set control number is generated starting with one for the first set and increasing by one for each set in the group.

Automatic Mapping of the Sub Element (Composite) and Repetition Separator

For X12 EDI, if the ISA16 element is not mapped, the sub element separator will be automatically emitted. Also the repetition separator is also automatically emitted for the ISA11 element if not otherwise mapped. If you are using a version prior to 4030 where the repetition separator is not used for ISA11, then map it to its proper value.

Acknowledgment (997, 999, TA1)

There are three types of acknowledgment that you may need to process when using HIPAA transactions. The Functional Acknowledgment (997) transaction is used to report problems at the functional group or transaction set level. This is located in the Transactions/997. The Implementation Acknowledgment (999) is used to provide additional implementation specification validation reporting. This is located in the Transactions/999-A1. Both the 997 and 999 are provided with and without the X12 envelope segments. For problems with the interchange or functional group (ISA/GS), the TA1 segment is used. This is found at Segments/TA1.


There are other folders (Segments, Composites, Elements) that contain structure definitions for those EDI components. You should never need to use these directly as everything required is present in the transaction structure. They are provided because the specification metadata is created exactly it is specified by the EDI standard. You may also note that in the transaction structure some elements show the change indication icon (a small gold triangle in the icon). This represents the cases where the definition in the transaction specification overrides or augments that of the underlying segment/composite/element. Again, no action on your part is required, this is just for information.