FIX: The generated XML files are much larger than expected when you try to split an EDI document that contains multiple sub-documents by using a "multiple" type schema in BizTalk Server 2006 R2 or BizTalk Server 2009

Article translations Article translations
Article ID: 967945 - View products that this article applies to.
Expand all | Collapse all

On This Page

SYMPTOMS

In Microsoft BizTalk Server 2006 R2 or BizTalk Server 2009, when you try to split an Electronic Data Interchange (EDI) document that contains multiple sub-documents by using a “multiple” type schema, the XML files that are generated are much larger than expected. Therefore, system performance when BizTalk Server 2006 R2 or BizTalk Server 2009 processes large EDI interchanges becomes severely degraded.

CAUSE

This problem occurs because of a design change in BizTalk Server 2006 R2 or BizTalk Server 2009. BizTalk Server 2006 R2 or BizTalk Server 2009 introduces a new splitting behavior for EDI documents that contain multiple sub-documents and that are used with “multiple” type schemas. The splitting behavior results in XML files that include not only the sub-document that you want, but also empty XML markup for all sibling sub-documents. Although the sibling sub-documents do not contain data, the behavior results in bloated output XML files and other inefficiencies that make processing very large EDI batches impossible.

RESOLUTION

Cumulative update information

For BizTalk Server 2009, the hotfix that resolves this issue is included in Cumulative Update 1 for BizTalk Server 2009. 

For more information about how to obtain the cumulative update package, click the following article number to view the article in the Microsoft Knowledge Base: 

2429050 Cumulative update package 1 for BizTalk Server 2009

Hotfix information

A supported hotfix is available from Microsoft. However, this hotfix is intended to correct only the problem that is described in this article. Apply this hotfix only to systems that are experiencing this specific problem. This hotfix might receive additional testing. Therefore, if you are not severely affected by this problem, we recommend that you wait for the next software update that contains this hotfix.

If the hotfix is available for download, there is a "Hotfix download available" section at the top of this Knowledge Base article. If this section does not appear, contact Microsoft Customer Service and Support to obtain the hotfix.

Note If additional issues occur or if any troubleshooting is required, you might have to create a separate service request. The usual support costs will apply to additional support questions and issues that do not qualify for this specific hotfix. For a complete list of Microsoft Customer Service and Support telephone numbers or to create a separate service request, visit the following Microsoft Web site:
http://support.microsoft.com/contactus/?ws=support
Note The "Hotfix download available" form displays the languages for which the hotfix is available. If you do not see your language, it is because a hotfix is not available for that language.

Prerequisites

You must have Microsoft BizTalk Server 2006 R2 installed to apply this hotfix.

Restart requirement

You do not have to restart the computer after you apply this hotfix.

Hotfix replacement information

This hotfix does not replace any other hotfixes.

File information

The English version of this hotfix has the file attributes (or later file attributes) that are listed in the following table. The dates and times for these files are listed in Coordinated Universal Time (UTC). When you view the file information, it is converted to local time. To find the difference between UTC and local time, use the Time Zone tab in the Date and Time item in Control Panel.
Collapse this tableExpand this table
File nameFile versionFile sizeDateTimePlatform
microsoft.biztalk.edi.messagecore.dll3.6.1512.2337,78416-Feb-200906:31x86
microsoft.biztalk.edi.pipelinecomponents.dll3.6.1512.2169,86416-Feb-200906:32x86
Note Because of file dependencies, the most recent hotfix that contains these files may also contain additional files.

The hotfix that is associated with this article enables a splitting behavior that is consistent with the splitting behavior of earlier versions of BizTalk and of BizTalk Accelerator for HIPAA.

As soon as the update is installed, the new splitting behavior is disabled by default. To enable the new splitting behavior, follow these post-setup instructions:
  1. Un-deploy any registered multiple schemas.
  2. Open the schema by using a text editor.
  3. Add the following attribute to the "b:schemaInfo" node:
        Split_Without_Sibling_Data="Yes"
This new attribute appears displayed under the "xs:annotation / xs:appinfo / b:schemaInfo" segment, just after the "subdocument_break="Yes" " segment.

The following is an example:
<xs:annotation>
  <xs:documentation xml:lang="en">HIPAA Schema TS834A1 - Washington Publishing Company (http://www.wpc-edi.com)</xs:documentation> 
  <xs:appinfo>
    <schemaEditorExtension:schemaInfo namespaceAlias="btsedi" extensionClass="Microsoft.BizTalk.Edi.SchemaEditorExtension.EdiSchemaExtension" standardName="EDI" xmlns:schemaEditorExtension="http://schemas.microsoft.com/BizTalk/2003/SchemaEditorExtensions" /> 
    <b:schemaInfo b:subdocument_break="yes" Split_Without_Sibling_Data="Yes" BiztalkServerEditorTool_Version="1.5" root_reference="X12_00401_834" displayroot_reference="X12_00401_834" version="3.0" standard="EDI" standards_version="00401" xmlns:b="http://schemas.microsoft.com/BizTalk/2003" X12ConditionDesignator_Check="Yes" /> 
  </xs:appinfo>
</xs:annotation>

STATUS

Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section.

MORE INFORMATION

For example, when you try to process an incoming Health Insurance Portability and Accountability Act of 1996 (HIPAA) 837D interchange that contains multiple claims, the XML output from BizTalk Server 2006 differs from the XML output from BizTalk Server 2006 R2. In BizTalk Server 2006, the BizTalk Accelerator for HIPAA splits the 837D EDI file. The EDI engine then translates the EDI file into multiple XML files. The EDI engine generates one XML file per claim. Each XML file contains only the data and the XML markup that pertains to the claim.

However, in BizTalk Server 2006 R2, the EDI engine splits the 837D EDI file. The EDI engine then translates the file to multiple XML files in which each claim file contains additional XML markup. In this case, the resulting XML file contains the expected data for the claim. The XML file also contains empty XML markup for all sibling claims that are found in the original interchange.

For more information about EDI support in BizTalk Server 2006 R2, visit the following Microsoft Developer Network (MSDN) Web site:
http://msdn.microsoft.com/en-us/library/bb226371.aspx
For more information about software update terminology, click the following article number to view the article in the Microsoft Knowledge Base:
824684 Description of the standard terminology that is used to describe Microsoft software updates

Properties

Article ID: 967945 - Last Review: December 8, 2010 - Revision: 2.0
APPLIES TO
  • Microsoft BizTalk Server 2006 R2 Standard Edition
  • Microsoft BizTalk Server 2006 R2 Enterprise Edition
  • Microsoft BizTalk Server 2006 R2 Developer Edition
  • Microsoft BizTalk Server 2006 R2 Branch Edition
  • Microsoft BizTalk Server 2009 Branch
  • Microsoft BizTalk Server 2009 Developer
  • Microsoft BizTalk Server 2009 Enterprise
  • Microsoft BizTalk Server 2009 Standard
Keywords: 
kbsurveynew kbautohotfix kbbiztalk2006r2sp1fix kbexpertiseinter kbHotfixServer kbqfe kbbiztalk2009presp1fix KB967945

Give Feedback

 

Contact us for more help

Contact us for more help
Connect with Answer Desk for expert help.
Get more support from smallbusiness.support.microsoft.com