Mapping - Data Mapper - EDIFACT/X12 - Functions 'Number of segments in
Hi,
I have a question about Data Mapper component.
In the EDI File (EDIFACT):
- segment ?UNT? describe the number of segment in a message,
- and segment ?UNZ? describe the number of message in a interchange.
Example UNT and UNZ:
In this example, 531 numbers of segment and 5 messages in this interchange 00073487
UNT+531+0001614907'
UNZ+5+00073487'
I would like to know if there are a function to get :
- Number segment in a message
- Number message in a interchange
Corresponding EDIFACT/X12 :
EDIFACT -> X12
UNT (UNT.E0074) -> SE (SE1)
UNZ (UNZ.E0036) -> IEA (IEA1)
IEA - Interchange Control Trailer
? IEA01 - Number of Included Functional Groups - This is used for message integrity, developed before such things as check sums were widely implemented.
? IEA02 - Interchange Control Number - Must match the control number in the IEA.
In the EDI File (EDIFACT): - segment ?UNT? describe the number of segment in a message, - and segment ?UNZ? describe the number of message in a interchange.
Exemple UNT : Talend-Data-Mapper-1.png
Example UNZ : In this example, five message in this interchange 00073487 Talend-Data-Mapper-2.png
I would like to know if there are a function to get : - Number segment in a message - Number message in a interchange
Corresponding EDIFACT/X12 :
EDIFACT -> X12 UNT (UNT.E0074) -> SE (SE1) UNZ (UNZ.E0036) -> IEA (IEA1) IEA - Interchange Control Trailer ? IEA01 - Number of Included Functional Groups - This is used for message integrity, developed before such things as check sums were widely implemented. ? IEA02 - Interchange Control Number - Must match the control number in the IEA.
There is no easy way to do this for EDIFACT EDI, these are automatically calculated for X12 EDI, but not at present for EDIFACT. You should submit a JIRA to have this addressed. We can provide a patch for this in 5.4.1 if necessary.
Hi Benjamin, I would suggest you to connect to the Support portal: https://support.talend.com/otrs/customer.pl and log your request, so that we treat it with priority, through the support cycle. If you have any trouble logging in to the Support portal, just let me know here and contact support.eu@talend.com Many thanks Elisa
Hi Benjamin,
What about having a PreJob done using the DI components and not the Talend Data Mapper using some regular expression to find out the segment 'UNT' and 'UNZ' and then be able to count those.
That way you could perform this check before trying to parse your EDIFACT; and accept or reject those files which can be Invalid.
Let us know if that approach could help and if you could provide a Sample file and the expected result in the number of Segment; we could try to guide and deliver direction to implement this PreJob in Talend.
Best regards.
@esabot wrote:
Hi Benjamin,
I would suggest you to connect to the Support portal:
https://support.talend.com/otrs/customer.pl and log your request, so that we treat it with priority, through the support cycle.
If you have any trouble logging in to the Support portal, just let me know here and contact support.eu@talend.com
Many thanks
Elisa
Has this functionality been added to data mapper yet?
