none
BizTalk Server 2009 EDIFACT Party Errors RRS feed

  • Question

  • Hello,

    I am using BizTalk Server 2009 and getting the following errors in event viewer while processing an EDI Orders D01B file. I notice data value ORDERS:D:01B:UN:EAN010 is being considered in UNB segment (Error: 6). Wonder if its something to do with segment delimiter settings? I would appreciate if anyone could help me resolve this error.

    Error: 1 (Miscellaneous error)
    47: Envelope functionality not supported

    Error: 2 (Field level error)
    SegmentID: UNB
    Position in TS: 1
    Data Element ID: UNB8
    Position in Segment: 8
    Data Value: 1
    37: Invalid character(s) found in data element

    Error: 3 (Field level error)
    SegmentID: UNB
    Position in TS: 1
    Data Element ID: UNB9
    Position in Segment: 9
    Data Value: 
    21: Invalid character found

    Error: 4 (Field level error)
    SegmentID: UNB
    Position in TS: 1
    Data Element ID: UNB9
    Position in Segment: 9
    Data Value: 1
    UNH
    39: Data element too long

    Error: 5 (Field level error)
    SegmentID: UNB
    Position in TS: 1
    Data Element ID: UNB11
    Position in Segment: 11
    Data Value: 
    37: Invalid character(s) found in data element

    Error: 6 (Field level error)
    SegmentID: UNB
    Position in TS: 1
    Data Element ID: UNB11
    Position in Segment: 11
    Data Value: ORDERS:D:01B:UN:EAN010
    BGM
    37: Invalid character(s) found in data element

    Error: 7 (Field level error)
    SegmentID: UNB
    Position in TS: 1
    Data Element ID: UNB11
    Position in Segment: 11
    Data Value: 
    16: Too many elements

    Error: 8 (Field level error)
    SegmentID: UNB
    Position in TS: 1
    Data Element ID: 
    Position in Segment: 6
    Data Value: 
    12: Invalid value in data element

    Following is my EDI message.

    UNB+UNOA:3+123456789:ZZ+ABCD:ZZ+140526:0515+11451++++1’
    UNH+11449+ORDERS:D:01B:UN:EAN010’
    BGM+220+R-42210287A+9’
    DTM+137:20140526:102’
    DTM+2:20140529:102’
    NAD+BY+9313938000631::9’
    NAD+ST+9321GR::92’
    NAD+SU+967228::92’
    LIN+1++59314057007490:SRV’
    QTY+21:8’
    PRI+1E:144.936’
    LIN+2++09330130000627:SRV’
    QTY+21:48’
    PRI+1E:155.7124’
    LIN+3++09330130009989:SRV’
    QTY+21:132’
    PRI+1E:149.632’
    UNS+S’
    MOA+86:28385.1072’
    CNT+2:3’
    UNT+20+11449’
    UNZ+1+11451’


    Thanks,

    Tarun

    Saturday, June 7, 2014 5:20 AM

Answers

  • Your segment delimiter is not working (you can see that the UNH and BGM segment is being interpreted in the UNB segment).

    You have posted a ’ but the EDIFACT default is ' and you need to use the defaults when the UNA segment is not supplied in the input.

    Morten la Cour

    Saturday, June 7, 2014 5:35 AM
  • That's because your document don't have a UNA segment and are using Carriage returns (which again is not EDIFACT standard).

    So you need to change the EFactDelimiters property on the EDIReceive Pipeline to:

    0x3A, 0x2B, 0x2E, 0x3F, 0x20, 0x27, 0x0D, 0x0A

    Notice I have also changed the decimal delimiter from , (default) to .

    But again: You should consider having the people sending you this EDIFACT supplying a UNA segment, this is not required, but when you don't supply it, you need to conform with the EDIFACT standards (which they are not).

    Morten la Cour

    Sunday, June 8, 2014 11:01 AM

All replies

  • Your segment delimiter is not working (you can see that the UNH and BGM segment is being interpreted in the UNB segment).

    You have posted a ’ but the EDIFACT default is ' and you need to use the defaults when the UNA segment is not supplied in the input.

    Morten la Cour

    Saturday, June 7, 2014 5:35 AM
  • I changed the segment delimiter to a ' in the message. While rest of the errors have gone I have started getting the following new error. Do you know the reason for this error?

    Error: 1 (Miscellaneous error)
    33: Invalid occurence outside message, package or group

    Thanks,

    Tarun

    Sunday, June 8, 2014 10:55 AM
  • That's because your document don't have a UNA segment and are using Carriage returns (which again is not EDIFACT standard).

    So you need to change the EFactDelimiters property on the EDIReceive Pipeline to:

    0x3A, 0x2B, 0x2E, 0x3F, 0x20, 0x27, 0x0D, 0x0A

    Notice I have also changed the decimal delimiter from , (default) to .

    But again: You should consider having the people sending you this EDIFACT supplying a UNA segment, this is not required, but when you don't supply it, you need to conform with the EDIFACT standards (which they are not).

    Morten la Cour

    Sunday, June 8, 2014 11:01 AM
  • Thanks Morten!
    Sunday, June 8, 2014 1:26 PM
  • The latest error now is as below even though minoccurs of UNH3 is 0. Any idea of this error?

    Error encountered during parsing. The Edifact transaction set with id '11449' contained in interchange (without group) with id '11451', with sender id '123456789', receiver id 'ABCD' is being suspended with following errors:
    Error: 1 (Field level error)
    SegmentID: UNH
    Position in TS: 1
    Data Element ID: UNH3
    Position in Segment: 3
    Data Value: 
    76: Too few data elements

    Sunday, June 8, 2014 1:32 PM
  • Because your unh3 is still present in the document and it is not allowed to be empty
    Sunday, June 8, 2014 3:32 PM
  • I don't see UNH3 is present in the message. See the excerpt below.

    UNH+11449+ORDERS:D:01B:UN:EAN010’

    Thanks,

    Tarun

    Monday, June 9, 2014 1:57 AM
  • Didn't you say you changed the ’ to '????

    Then why are you still copy/pasting a ’. That would be the reason the interpreter thinks there are a UNH3 segment?

    Morten la Cour 

    Monday, June 9, 2014 5:33 AM
  • I actually copied the excerpt from my original message in this post which has a . However, even after ’ is changed to to ' in the message I am still getting this error of UNH3.
    Tuesday, June 10, 2014 2:12 AM
  • Well you must be doing something else wrong. With your example after changing all the delimiters and the EFactDelimiters on the Pipeline, it works on my end. Please post the EXACT EDIFACT Message that is causing you this error.

    Morten la Cour

    Tuesday, June 10, 2014 4:13 AM