You have a computer that is running Microsoft BizTalk Server 2006 R2 or Microsoft BizTalk Server 2009.
You use a Windows Communication Foundation (WCF)-based SAP adapter from Microsoft BizTalk Adapter Pack 2.0 to connect to an SAP system.
You configure one receive location to receive different kinds of intermediate documents (IDOCs) from SAP by using the WCF-SAP adapter. Additionally, you set the value of the ProgramID property in the uniform resource identifier (URI) of the SAP connection.
You process each kind of IDOC by using a custom pipeline that includes multiple Flat file disassembler pipeline components.
In this scenario, the IDOCs are not processed correctly. Additionally, you receive an error message that resembles the following:
Unexpected data found while looking for: '<segment>' The current definition being parsed is idocData. The stream offset where the error occurred is <offset number>. The line number where the error occurred is <line number>. The column where the error occurred is <column number>.
This problem occurs because the first Flat file disassembler pipeline component in the custom pipeline tries to disassemble all the IDOCs that are received. However, the IDOCs should be processed by different Flat file disassembler components that have different schemas.
Cumulative update information
The hotfix that resolves this issue is included in Cumulative Update 1 for BizTalk Adapter Pack 2.0.
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:
2444952 Cumulative update package 1 for BizTalk Adapter Pack 2.0
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.
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, submit a request to 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: -
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.
You must have BizTalk Adapter Pack 2.0 installed to apply this hotfix.
You do not have to restart the computer after you apply this hotfix.
Hotfix replacement information
This hotfix does not replace any other hotfixes.
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.
For all supported 32-bit versions of BizTalk Adapter Pack 2.0
For all supported 64-bit versions of BizTalk Adapter Pack 2.0
Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section.
For more information about using BizTalk Server to receive IDOCs from SAP, visit the following Microsoft Developer Network (MSDN) Web site: