none
Explain the Error Below RRS feed

  • General discussion

  • Hi,

    I am passing a X12 document as a string to a webservice which execute EDIReceive pieline.

    Whenever i have a "&" followed by space in any segment of the data in X12 ,the receive

    pipeline fails and gives the below error.If remove the space after & then the x12 passes thru

    the pipeline.I checked the xml when the port fails and the xml is only upto the & and further

    parsing is not done by the EDI engine.Any ideas why we should not have a space after & which

    is considering it as a transaction terminator.

     

    Thanks....

    SPN

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

    Error: 1 (Segment level error)
        SegmentID:
        Position in TS: 8
        7: Segment Not In Proper Sequence

    Friday, August 13, 2010 10:13 PM

All replies

  • Hi,

       Can you please an example or your input file such that we can repro here.

     

     

    Thanks

    Gyan


    If this answers your question, please mark it as "Answered".
    Monday, August 16, 2010 3:21 AM
  • The best way to troubleshoot this is by doing a passthrough and then looking at the segements to make sure they are in order. You will have to refer to the hipaa guides. It looks like you are missing a required segment. You could also test the map and disable the compliance check and go field by field to see which one you are missing. Make sure that you use the native output and then do a replace ont he "~" with a control line feed to you can view the output clearly.
    Please Indicate "Mark as Answer" if this Post has Answered the Question
    Monday, August 16, 2010 2:28 PM
  • Hi gyan,

    This is the file i am using

    The underlined segment is having a "&" followed by space .

     

    ISA*00*          *00*          *ZZ*123001         *30*123456789      *040310*1530*U*00401*123456789*0*T*:
    GS*HR*STUP*RAMAS*20040310*1530*20*X*004010X093A1
    ST*276*0001
    BHT*0010*13**20100101
    HL*1**20*1
    NM1*PR*2*HPOP*****AD*123456799
    HL*2*1*21*1
    NM1*41*2*TEST*****FI*123456789
    HL*3*2*19*1
    NM1*1P*2*SS & HOSP*****XX*1234567890
    HL*4*3*22*0
    DMG*D8*20100101*M
    NM1*QC*1*PPS*DOM****MI*123456789
    TRN*1*ALLVALUESVALID
    AMT*T3*104
    DTP*232*RD8*20100101-20100101
    SE*15*0001
    GE*1*20
    IEA*1*123456789

     

    As per the HIPAA gudieline the special character is allowed in the NM1 segment .

     

    and

     

    Hi Carlos,

     

    this file fails in the input EDI receive itself .So there is no question of validating .

     

     

    Thanks....

    SPN

    • Edited by SPN Biztalk Saturday, August 21, 2010 12:51 AM
    Monday, August 16, 2010 9:16 PM
  • Hi SPN,

              I tried it on BizTalk Server 2010 and it runs fine. May I know which version of BizTalk are you using?

    As far as I know in engine behavior there is no change so can you also check if you are pre-processing this file before dropping into Edi-receive pipeline.

     

     

    Thanks

    Gyan


    If this answers your question, please mark it as "Answered".
    Tuesday, August 17, 2010 4:31 AM
  • Hi Gyan,

     

    We are using Biztalk server 2009 with windows 2008 sp1 as OS on a VM.

    The only parsing i  do onthis is since we are passing this from a webservice

    there will be no line endings.i.e; no CRLF which is a non printable character.

    We pass this whole text as string to the orchestration where the EDI receive will be executed.

    I have coded aroung to replace the ampersand space with ampersand for now.but i am not satisfied with what i did and want to know why???

     

    FYI...This is a UTF-8 unicoded text.

    Thanks....

    SPN

    Saturday, August 21, 2010 12:06 AM