none
Error with Repetition Separator in EDI send Pipeline RRS feed

  • Question

  • I am trying to generate a 271 EDI file in 5010 version using BizTalk Server 2010. I have the 5010 version of 270/271 BizTalk Schema deployed. The EB segment in 271 schema has been changed in 5010 version. If there are more than one EB segment containing similar information except for EB03 which is the service type code, then there should be only one EB segment with delimited EB03 element (such as EB*1**1#86#98#47#MH#AL#35#88#UC#33#48#50#52#BY#BZ*PR*MEDICARE PLAN~ ). When I pass this kind of xml to the EDI Send Pipeline, I get an error in the pipeline as follows.

    Unable to read the stream produced by the pipeline.
     Details: Error: 1 (Field level error)
        SegmentID: EB
        Position in TS: 16
        Data Element ID: EB03_ServiceTypeCode
        Position in Segment: 3
        Data Value:
        6: Invalid character in data element
       
    I have specified the ISA11 as "#" and did all the party setup to support 5010 version. I have also setup the X12 fallback settings.    
       
    Am I missing anything or Is this not handled by the updated EDI pipelines in BizTalk Server 2010 to handle 5010 transactions?  

    Thanks,

    BdBiz

    Tuesday, August 30, 2011 9:50 PM

Answers

  • "When I pass this kind of xml to the EDI Send Pipeline"

    are you passing repeating

    ...

    <EB02_BenefitCoverageLevelCode></EB02_BenefitCoverageLevelCode>

    <EB03_ServiceTypeCode>1</EB03_ServiceTypeCode>

    <EB03_ServiceTypeCode>86</EB03_ServiceTypeCode>

    <EB03_ServiceTypeCode>98</EB03_ServiceTypeCode>

    ...

    <EB04_InsuranceTypeCode>PR</EB04_InsuranceTypeCode>

    ....

     

    or are you passing in 

    ...

    <EB02_BenefitCoverageLevelCode></EB02_BenefitCoverageLevelCode>

    <EB03_ServiceTypeCode>1#86#98#47#MH#AL#35#88#UC#33#48#50#52#BY#BZ</EB03_ServiceTypeCode>

    <EB04_InsuranceTypeCode>PR</EB04_InsuranceTypeCode>

    ...


    Eric Stott [http://blog.biztalk-info.com] - Mark as Answer if this reply does.
    • Marked as answer by BdBiz Wednesday, August 31, 2011 4:37 PM
    Wednesday, August 31, 2011 4:22 PM
  • Please mark my response as an answer then.
    Eric Stott [http://blog.biztalk-info.com] - Mark as Answer if this reply does.
    • Marked as answer by BdBiz Wednesday, August 31, 2011 4:55 PM
    Wednesday, August 31, 2011 4:50 PM

All replies

  • Have you installed the Cumulative update package 1 for BizTalk Server 2010. Also just confirming whether you have checked the EDI properties / X12 Properties / Party as Interchange Sender / X12 Interchange Processing Properties / Check box "Use ISA11 as repetition separator".


    Cheers,
    Bali
    MCTS: BizTalk Server 2010,BizTalk Server 2006 and WCF
    -----------------------------------------------------
    Mark As Answer or Vote As Helpful if this helps.
    Wednesday, August 31, 2011 2:48 AM
  • Yes. I have installed the update, restarted the system and ran the process again. I still get the same error "Invalid character in data element" error.

    Any more suggestions?

     

    -BdBiz

     


    bd
    Wednesday, August 31, 2011 3:05 PM
  • Can you send the ISA segment for this interchange?
    Eric Stott [http://blog.biztalk-info.com] - Mark as Answer if this reply does.
    Wednesday, August 31, 2011 3:26 PM
  • HI Eric,

    Here is the ISA segment when a 271 is generated without any repetition separator in the EB segment. But the generation fails when I pass the one with the repetition separator. 

    ISA*00*          *00*          *ZZ*TEST-SENDER    *ZZ*TEST-RECEIVER  *110711*0914*#*00501*110914370*0*T*:~


    Thanks,
    BdBiz
    bd
    Wednesday, August 31, 2011 3:43 PM
  • "When I pass this kind of xml to the EDI Send Pipeline"

    are you passing repeating

    ...

    <EB02_BenefitCoverageLevelCode></EB02_BenefitCoverageLevelCode>

    <EB03_ServiceTypeCode>1</EB03_ServiceTypeCode>

    <EB03_ServiceTypeCode>86</EB03_ServiceTypeCode>

    <EB03_ServiceTypeCode>98</EB03_ServiceTypeCode>

    ...

    <EB04_InsuranceTypeCode>PR</EB04_InsuranceTypeCode>

    ....

     

    or are you passing in 

    ...

    <EB02_BenefitCoverageLevelCode></EB02_BenefitCoverageLevelCode>

    <EB03_ServiceTypeCode>1#86#98#47#MH#AL#35#88#UC#33#48#50#52#BY#BZ</EB03_ServiceTypeCode>

    <EB04_InsuranceTypeCode>PR</EB04_InsuranceTypeCode>

    ...


    Eric Stott [http://blog.biztalk-info.com] - Mark as Answer if this reply does.
    • Marked as answer by BdBiz Wednesday, August 31, 2011 4:37 PM
    Wednesday, August 31, 2011 4:22 PM
  • Thats interesting.. I have been passing it like,

    <EB02_BenefitCoverageLevelCode></EB02_BenefitCoverageLevelCode>

    <EB03_ServiceTypeCode>1#86#98#47#MH#AL#35#88#UC#33#48#50#52#BY#BZ</EB03_ServiceTypeCode>

    <EB04_InsuranceTypeCode>PR</EB04_InsuranceTypeCode>

    Now I created multiple EB03 elements as you mentioned above and it worked.

    Thanks very much Eric!!


    bd
    Wednesday, August 31, 2011 4:37 PM
  • Please mark my response as an answer then.
    Eric Stott [http://blog.biztalk-info.com] - Mark as Answer if this reply does.
    • Marked as answer by BdBiz Wednesday, August 31, 2011 4:55 PM
    Wednesday, August 31, 2011 4:50 PM