none
EDI Root Node not matching - maybe EDI version issue? RRS feed

  • Question

  • Part 1 - dropped EDI 850 file into Receive.  Had default EDI pipeline, and trying to route XML version of the EDI to a disk Send Port.

    Error encountered during parsing. The X12 transaction set with id '' contained in functional group with id '850009661', in interchange with id '850009661', with sender id '9333516114     ', receiver id '956837686      ' is being suspended with following errors:

    Error: 1 (Miscellaneous error)

                    6: Finding the document specification by message type "http://schemas.microsoft.com/BizTalk/EDI/X12/2006#X12_00401_850" failed. Verify the schema deployed properly.

     

    The schema from the c:\Program Files (x86)\Microsoft BizTalk Server 2010\XSD_Schema\EDI had this root: X12_00204_850. That's the one I put in my project and deployed.

    First line of EDI file:

    ISA^00^          ^00^          ^ZZ^9333516114     ^ZZ^956837686      ^150430^1530^U^00401^850009661^1^T^:~

    So is 00401 vs 00204 the version of the EDi standard?  What should I do?

    This blog suggests running the Cumulative Updates (I'm on BT2010):

    http://maytonsupport.blogspot.com/2012/07/biztalk-2010-verify-schema-deploy.html


    Part 2- I changed the root node and TypeName, to see what would happen.  I was just sending XML version of data to disk, and this is what came out.

    <ns0:X12_TA1_Root IsGeneratedAck="true" xmlns:ns0="http://schemas.microsoft.com/Edi/X12">
        <TA1>
            <TA101>850009661</TA101>
            <TA102>150430</TA102>
            <TA103>1530</TA103>
            <TA104>A</TA104>
            <TA105>000</TA105>
        </TA1>
    </ns0:X12_TA1_Root>

    (Was getting same data out even with the errors above, when root node was X12_00204_850.)I don't even see a TA1 element in the schema, where is it coming from?

    Now Getting Errors as follows (From EventLog): 

    Error encountered during parsing. The X12 transaction set with id '0001' contained in functional group with id '850009661', in interchange with id '850009661', with sender id '9333516114     ', receiver id '956837686      ' is being suspended with following errors:
    Error: 1 (Miscellaneous error)
        4: Number of included segments do not match

    Error: 2 (Field level error)
        SegmentID: BEG
        Position in TS: 2
        Data Element ID: BEG05
        Position in Segment: 5
        Data Value: 20150430
        8: Invalid Date

    Error: 3 (Field level error)
        SegmentID: REF
        Position in TS: 7
        Data Element ID: REF01
        Position in Segment: 1
        Data Value: BA
        7: Invalid code value

    Error: 4 (Field level error)
        SegmentID: DTM
        Position in TS: 8
        Data Element ID: DTM02
        Position in Segment: 2
        Data Value: 20150430
        8: Invalid Date

    Error: 5 (Field level error)
        SegmentID: TD5
        Position in TS: 9
        Data Element ID: TD511
        Position in Segment: 11
        Data Value:
        3: Too many data elements

    Error: 6 (Segment level error)
        SegmentID: TD5
        Position in TS: 9
        6: Segment has trailing delimiter(s) at component or sub-component level

    Error: 7 (Field level error)
        SegmentID: N1
        Position in TS: 11
        Data Element ID: N103
        Position in Segment: 3
        Data Value: TE
        7: Invalid code value

    Error: 8 (Segment level error)
        SegmentID: N1
        Position in TS: 11
        6: Segment has trailing delimiter(s) at component or sub-component level

    Error: 9 (Segment level error)
        SegmentID: N3
        Position in TS: 12
        6: Segment has trailing delimiter(s) at component or sub-component level

    Error: 10 (Field level error)
        SegmentID: N1
        Position in TS: 14
        Data Element ID: N103
        Position in Segment: 3
        Data Value: TE
        7: Invalid code value

    Error: 11 (Segment level error)
        SegmentID: N3
        Position in TS: 15
        6: Segment has trailing delimiter(s) at component or sub-component level

    Error: 12 (Field level error)
        SegmentID: PO1
        Position in TS: 17
        Data Element ID: PO104
        Position in Segment: 4
        Data Value: 148.00
        6: Invalid character in data element

    Thanks,

    Neal Walters
    http://MyLifeIsMyMessage.net





    • Edited by Neal Walters Tuesday, May 19, 2015 3:06 PM Added EventLogErrors
    Tuesday, May 19, 2015 1:40 PM

Answers

  • The EDI Schemas ship in the XSD_Schema directory.  For that particular transaction, you should find the schema at:

    %\XSD_Schema\EDI\MicrosoftEdiXSDTemplates[.zip]\X12\00401\X12_00401_850.xsd

    If they're not there, either the EDI Subsystem was not installed or they were removed.

    • Marked as answer by Neal Walters Wednesday, May 20, 2015 1:14 PM
    Tuesday, May 19, 2015 10:10 PM

All replies

  • You need to deploy a version of X12_00401_850.xsd.  Your Trading Partner is sending you a 4010 version transaction.

    The proper way is to take the supplied X12_00401_850.xsd and change the TargetNamespace to something you own.  Then configure the resolution to that namespace in the Agreement.

    The methods for Schema Resolution are described here: https://msdn.microsoft.com/en-us/library/bb246089.aspx?f=255&MSPPError=-2147217396

    Tuesday, May 19, 2015 2:56 PM
  • The supplied schema was 00204.  Do I need to find a newer schema?  If so where?
    Neal
    Tuesday, May 19, 2015 3:08 PM
  • Well, if you're receiving EDI, all the schemas ship with BizTalk Server and are found in the XSD_Schema folder in the BizTalk install folder.

    In this case, the developer takes the EDI Schemas from there, no one would supply this to you.

    Tuesday, May 19, 2015 3:57 PM
  • boatseller - not sure what you are adding or trying to say in your last post.

    I originally said "The schema from the c:\Program Files (x86)\Microsoft BizTalk Server 2010\XSD_Schema\EDI had this root: X12_00204_850. That's the one I put in my project and deployed.".

    So, please tell me what 204 means, and how do I find a 401 (4.01) schema?

    Neal


    Tuesday, May 19, 2015 9:59 PM
  • The EDI Schemas ship in the XSD_Schema directory.  For that particular transaction, you should find the schema at:

    %\XSD_Schema\EDI\MicrosoftEdiXSDTemplates[.zip]\X12\00401\X12_00401_850.xsd

    If they're not there, either the EDI Subsystem was not installed or they were removed.

    • Marked as answer by Neal Walters Wednesday, May 20, 2015 1:14 PM
    Tuesday, May 19, 2015 10:10 PM
  • Okay, it's there.  I don't know why I didn't see it before.

    As a matter of fact, there are 16 versions of the 850 there.

    Thanks,
    Neal

    Wednesday, May 20, 2015 1:14 PM