none
BizTalk Server 2009 - Sub Document Processing Hot Fixes RRS feed

  • Question

  • I am working on a BizTalk Server 2009 project using the Muliptle Schema for 4010 X12 837 claims processing. I am using the EDIReceive pipeline to "split" the document into multiple messages and then writting the "split" messages in XML to a Receive port. When I look at the XML messages that are created, it appears that there is additional information in the messages. Information from other claims appears to have been associated with the claim I am trying to view. I believe that this is similar to the hot fixes for "bloated XML" in BizTalk Server 2006 R2 [http://support.microsoft.com/kb/967945 ]. Does anyone know if there is a hot fix for this in BizTalk Server 2009?

    When processing an 837i file that contains one (1) Transaction Set with multiple claims. We are processing an EDI file against the 837I Multiple schema to create separate messages for each claim. We are using the EDIReceive pipeline to process the file. The EDI pipeline splits the document into multiple messages and outputs the information into XML documents. The XML documents appear to have information from both claims in each document.

     

    Example:

    Claim 1 has all of the information associated with Claim 1 but also includes some of the information associated with Claim 2

    Claim 2 has all of the information associated with Claim 2 but also includes some of the information associated with Claim 1

     

    I would expect that the message for Claim 1 would only have information associated with Claim 1 and that the message for claim 2 would only have information associated with claim 2.

    Friday, November 13, 2009 5:55 PM

Answers

  • OK, it looks like I have it working. Here is what I did.

    1) Downloaded the Hotfix for 5010 and followed the directions provided with the download.
    2) Un-deployed (removed) the schema from the BizTalk application that used the X12 4010 837 Mulitple Schema using the BizTalk Admin console.
    3) Manually modified the original X12 4010 837 Multiple schema by adding Split_Without_Sibling_Data ="yes" to the "b:schemaInfo" node after the "subdocument_break="Yes"  statement.
    4) Modifed my VS2008 project to use the manually modified X12 4010 837 Multiple schema.
    5) Validated my test EDI file against the manually modified X12 4010 837 Multiple schema.
    6) Rebuilt and Deployed the VS 2008 project
    7) Dropped input file in the Receive folder
    8) Verified that the files sent to the Send folder were no longer bloated.


    Thank you all for the help. I hope this thread will help others that run into this problem.
    • Marked as answer by Obach2u Monday, November 16, 2009 7:54 PM
    Monday, November 16, 2009 7:54 PM

All replies

  • This is an issue, I have opened up a ticket with MS, ticket number: 109110379284723 you can reference it and receive the hotfix when available.
    Eric Stott [http://blog.biztalk-info.com] - Mark as Answer if this reply does.
    Saturday, November 14, 2009 7:23 PM
  • Hi,
        This has been fixed as a part of Hipaa 5010 support in Biztalk 2009. It's in Beta phase you can download it from:
    http://blogs.msdn.com/biztalkb2b/archive/2009/07/10/hipaa-5010-public-beta-available.aspx

    Thanks
    Gyan
    If this answers your question, please mark it as "Answered".
    Monday, November 16, 2009 1:10 PM
  • Yes, the problem however is for the customers who are using the BTS 2009 product for the 4010 transactions.
    Eric Stott [http://blog.biztalk-info.com] - Mark as Answer if this reply does.
    Monday, November 16, 2009 2:11 PM
  • That is correct, this is for BTS 2009 using 4010. It appears that the hot fix for 5010 does not address the issues with 4010 in BTS 2009. Eric, how do I follow that support ticket?
    Monday, November 16, 2009 3:01 PM
  • Hi,
       In this fix "Bloated XML" problem is fixed for 4010 as well.
    For this you need to change the schema for X12 manually: You need to add following annotation to schema:
    <!-- /* Font Definitions */ @font-face {font-family:"Cambria Math"; panose-1:2 4 5 3 5 4 6 3 2 4; mso-font-alt:"Calisto MT"; mso-font-charset:0; mso-generic-font-family:roman; mso-font-pitch:variable; mso-font-signature:-1610611985 1107304683 0 0 159 0;} @font-face {font-family:Calibri; panose-1:2 15 5 2 2 2 4 3 2 4; mso-font-alt:"Electra LH Regular"; mso-font-charset:0; mso-generic-font-family:swiss; mso-font-pitch:variable; mso-font-signature:-1610611985 1073750139 0 0 159 0;} @font-face {font-family:"MS Shell Dlg"; panose-1:2 11 6 4 2 2 2 2 2 4; mso-font-charset:0; mso-generic-font-family:swiss; mso-font-pitch:variable; mso-font-signature:-520082689 -1073741822 8 0 66047 0;} /* Style Definitions */ p.MsoNormal, li.MsoNormal, div.MsoNormal {mso-style-unhide:no; mso-style-qformat:yes; mso-style-parent:""; margin:0cm; margin-bottom:.0001pt; mso-pagination:widow-orphan; font-size:11.0pt; font-family:"Calibri","sans-serif"; mso-fareast-font-family:Calibri; mso-fareast-theme-font:minor-latin; mso-bidi-font-family:"Times New Roman";} .MsoChpDefault {mso-style-type:export-only; mso-default-props:yes; font-size:10.0pt; mso-ansi-font-size:10.0pt; mso-bidi-font-size:10.0pt;} @page Section1 {size:612.0pt 792.0pt; margin:72.0pt 72.0pt 72.0pt 72.0pt; mso-header-margin:36.0pt; mso-footer-margin:36.0pt; mso-paper-source:0;} div.Section1 {page:Section1;} --> Split_Without_Sibling_Data ="yes".




    Thanks
    Gyan


    If this answers your question, please mark it as "Answered".
    Monday, November 16, 2009 4:33 PM
  • Can you please reply without all of the formatting in your reply? Also, where is this documented in the KB?
    Monday, November 16, 2009 4:35 PM
  • OK, it looks like I have it working. Here is what I did.

    1) Downloaded the Hotfix for 5010 and followed the directions provided with the download.
    2) Un-deployed (removed) the schema from the BizTalk application that used the X12 4010 837 Mulitple Schema using the BizTalk Admin console.
    3) Manually modified the original X12 4010 837 Multiple schema by adding Split_Without_Sibling_Data ="yes" to the "b:schemaInfo" node after the "subdocument_break="Yes"  statement.
    4) Modifed my VS2008 project to use the manually modified X12 4010 837 Multiple schema.
    5) Validated my test EDI file against the manually modified X12 4010 837 Multiple schema.
    6) Rebuilt and Deployed the VS 2008 project
    7) Dropped input file in the Receive folder
    8) Verified that the files sent to the Send folder were no longer bloated.


    Thank you all for the help. I hope this thread will help others that run into this problem.
    • Marked as answer by Obach2u Monday, November 16, 2009 7:54 PM
    Monday, November 16, 2009 7:54 PM
  • Microsoft is still working to provide an official hotfix for those who can't install Beta bits in production, correct?
    Eric Stott [http://blog.biztalk-info.com] - Mark as Answer if this reply does.
    Tuesday, November 17, 2009 7:55 PM
  • It is my understanding that Microsoft is working to provide an official hotfix. I am working in a test environment, so this is OK for now.

    Tuesday, November 17, 2009 10:23 PM
  • Has anyone noticed if Microsoft has released an offical hot fix for this problem yet?
    Monday, January 4, 2010 8:56 PM