none
Getting Error while parsing EDI 834 file in Biztalk 2013 RRS feed

  • Question

  • hi,

    while parsing EDI message (834) following Error occured (Mandatory Segment missing) occurs.  Please help me in understanding:

    How to read following error (mean how to identify which line of the message is generating this problem)

    Secondly please help me how to rectify the issue.

    The X12 transaction set with id '6125' contained in functional group with id '6125', in interchange with id '000006125', with sender id 'CM             ', receiver id '650743730      ' is being suspended with following errors:
    Error: 1 (Segment level error)
     SegmentID: N4
     Position in TS: 27
     3: Mandatory Segment Missing

    Error: 2 (Segment level error)
     SegmentID: HD
     Position in TS: 27
     2: Unexpected segment

    Error: 3 (Segment level error)
     SegmentID: N4
     Position in TS: 31
     3: Mandatory Segment Missing

    Error: 4 (Segment level error)
     SegmentID: HD
     Position in TS: 31
     2: Unexpected segment

    Error: 5 (Segment level error)
     SegmentID: N4
     Position in TS: 35
     3: Mandatory Segment Missing

    Thanks and regards,

    Monday, September 23, 2013 6:32 PM

Answers

  • If you're receiving this from a trading partner, they are sending you invalid EDI.

    So you can see what's going on, you should open the interchange (the whole EDI message) in a text editor, VisualStudio, Notepad++, etc.

    Replace the Segment Terminator, the most common is the '~' character with '~/r/n'.  That's to put each segment on it's own line.

    The Position in TS is essentially the line number but because it's counted form the ST, you'll have to add 2 or delete the ISA and GS lines from the editor.

    As for the errors, the first means an N4 (probably the Subscriber City, State, Zip) is missing.

    The second means that an HD segment is found where the N4 should, but this also means a number of other segments, DMG, NM1, etc, have also been skipped.

    Monday, September 23, 2013 9:15 PM