Do not input private or sensitive data. View Qlik Privacy & Cookie Policy.
Skip to main content

Announcements
See why IDC MarketScape names Qlik a 2025 Leader! Read more
cancel
Showing results for 
Search instead for 
Did you mean: 
Anonymous
Not applicable

Not found mapping model in EDIFACT parsing

I try to parse an EDIFACT file and get the following error:

Mapping Model 'DELFOR:D:96A:ZZ:EDIEL2' not found in supplied set of Mapping model.

 

What does this error mean and how do I solve the problem?

Labels (2)
6 Replies
Anonymous
Not applicable
Author

Hello,

Could you please give us a sample data of  your EDI file? Are you trying to translate an EDI message to XML?

Best regards

Sabrina

Anonymous
Not applicable
Author

Description https://www.ediel.fi/sites/default/files/Implementation%20Guide%20for%20DELFOR%20versio%202.3%20H.pd...

UNA:+.? '
UNB+UNOB:2+82800:ZZ+102965662952:82+990413:1049+22++++++1'
UNH+1+DELFOR:D:96A:ZZ:EDIEL2'
BGM+241+828000842601112+9+AB'
DTM+137:199905131048:203'
DTM+163:199905132100:203'
DTM+164:199905132300:203'
DTM+ZZZ:1:805'
NAD+DO+965662952:NO3:82++++OSLO+++NO'
NAD+FR+82800:160:SVK++++HARJAVALTA+++FI'
CTA+MS+:MR. POWER'
UNS+D'
NAD+XX'
LOC+90+FIPVO-TVS000ISH::SLY+:::TVS000ISH'
LIN+++1027:::SVK'
MEA+AAZ++Z01'
QTY+136:-33.020'
DTM+324:199905132100199905132200:Z13'
QTY+136:-38.090'
DTM+324:199905132200199905132300:Z13'
NAD+XX'
LOC+90+FIPVO-IVS000MP::SLY+:::IVS000MP'
LIN+++1027:::SVK'
MEA+AAZ++Z01'
QTY+136:-505.000'
DTM+324:199905132100199905132200:Z13'
QTY+136:-454.900'
DTM+324:199905132200199905132300:Z13'
UNS+S'
CNT+1:-13725.071'
UNT+29+1'
UNZ+1+22' 
Anonymous
Not applicable
Author

I looked through the attached PDF, and it looks like your sample file is in the correct format. What structure are you using to read the file? The error message indicates that the file contains data that the structure isn't expecting to find.
Anonymous
Not applicable
Author

I am using both tEDIFACTtoXML and tExtractEDIField and they both give this error. Both are set to D96A as EDI version

Anonymous
Not applicable
Author

The reason is that the sample EDI file (and Word Document) are actually an extension to the D96A standard, and they have a different identifier that the Talend component doesn't recognize. Change the third line of the sample file you provided to:

 

UNH+1+DELFOR0683p000009MACJ.png:96A:UN'

 

Then the job runs (see screenshot)

 

Here's the D96A standard:

 

https://www.stylusstudio.com/edifact/D96A/DELFOR.htm


Capture.PNG
Anonymous
Not applicable
Author

that emoji was not intended.