Hotfix to add the "ReceivedIdocRelease" binding property for the WCF-SAP adapter to BizTalk Adapter Pack 2.0 and Microsoft BizTalk Adapter Pack 2010

Article translations Article translations
Article ID: 2388784
Expand all | Collapse all

On This Page

This article applies to the following product:
  • BizTalk Adapter Pack 2.0
  • BizTalk Adapter Pack 2010

Introduction

This article describes a hotfix for Microsoft BizTalk Adapter Pack 2.0 and Microsoft BizTalk Adapter Pack 2010. This hotfix adds the ReceivedIdocRelease binding property to the Microsoft Windows Communication Foundation (WCF)-based SAP adapter. This property is used to resolve the following issue.

Symptom

Consider the following scenario:
  • You have a computer that is running Microsoft BizTalk Server 2006 R2, Microsoft BizTalk Server 2009 or Microsoft BizTalk Server 2010.
  • You use the WCF-based SAP adapter that is from Microsoft BizTalk Adapter Pack 2.0 or from Microsoft BizTalk Adapter Pack 2010 to connect to SAP.
  • You create a BizTalk application that uses the SAP adapter to receive intermediate documents (IDOCs) from SAP. Some schemas are generated when the application connects to SAP. The BizTalk application receives the IDOCs by using these schemas.
  • You upgrade SAP.
In this scenario, the IDOCs are not received after you upgrade SAP. Additionally, you receive the following error message:
Event Type: Error
Event Source: <BizTalk Server version>
Event Category: <BizTalk Server version>
Event ID: 5719
Description:
There was a failure executing the receive pipeline: "Microsoft.BizTalk.DefaultPipelines.XMLReceive, Microsoft.BizTalk.DefaultPipelines, Version=3.0.1.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35" Source: "XML disassembler" Receive Port: "<Receive Port>" URI: "<URI>" Reason: Finding the document specification by message type "<schema namespace>" failed. Verify the schema deployed properly.
If you configure SAP to send an earlier version of the IDOCs, the IDOCs are suspended. Additionally, you receive the following error message:
A message sent to adapter "WCF-SAP" on send port "<send port>" with URI "<URI>" is suspended. Error details: Microsoft.ServiceModel.Channels.Common.XmlReaderParsingException: The segment name is not valid for the IDOCTYP, Release, or CIMTYP. Segment name: <Segment name> IDOCTYP: <IDOCTYP> Release: <release> CIMTYP: . Ensure that your message xml validates against the operation schema.

Cause


This issue occurs because the WCF-based SAP adapter incorrectly uses the DOCREL property of the IDOCs to determine the release number of the IDOCs that are sent.

SAP populates the DOCREL property with the current value of SYSEREL. When SAP is upgraded, the WCF-based SAP adapter uses this new value of DOCREL to determine the IDOC release number. However, the release number from this new value is the previous release number. Therefore, the release number from this new value is incorrect for the IDOCs that are sent.

NoteDOCREL is an SAP release number for IDOC.

RESOLUTION

To resolve this issue after you apply the following hotfix, edit the ReceivedIdocRelease binding property. For more information about how to edit the ReceivedIdocRelease binding property, see the "More Information" section.

Cumulative update information

BizTalk Adapter Pack 2010

The hotfix that resolves this issue is included in Cumulative Update 1 for BizTalk Adapter Pack 2010. 

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:
     2539794 Cumulative update package 1 for BizTalk Adapter Pack 2010


BizTalk Adapter Pack 2.0

A specific hotfix is available to resolve this issue. This hotfix is available individually and 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

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.

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 website:
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

To apply this hotfix, you must have BizTalk Adapter Pack 2.0 installed.

Restart requirement

After you apply this hotfix, you do not have to restart the computer.

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.
For all supported x86-based versions of BizTalk Adapter Pack 2.0
Collapse this tableExpand this table
File nameFile versionFile sizeDateTimePlatform
Microsoft.adapters.sap.dll3.5.5310.0374,64007-Sep-201017:50x86
For all supported x64-based versions of BizTalk Adapter Pack 2.0
Collapse this tableExpand this table
File nameFile versionFile sizeDateTimePlatform
Microsoft.adapters.sap.dll3.5.5310.0345,96807-Sep-201017:52x64

MORE INFORMATION

How to edit the ReceivedIdocRelease binding property


To edit the ReceivedIdocRelease binding property, use the appropriate value that meets one of the following conditions:
  • If the value of the DOCREL property is the actual release number for the IDOCs, do not set any value for the ReceivedIdocRelease binding property.
  • If the release number of all received IDOCs is lower than the value of the DOCREL property, set the actual release number in the ReceivedIdocRelease binding property.

    For example, assume that the release number is 640 and that this number is lower than the value of the DOCREL property. In this scenario, set the value of the ReceivedIdocRelease binding property to 640.
  • If some types of the received IDOCs have a lower release number, and if the other IDOCs have a release number that is equal to SYSREL, each type must be set. To do this, use the following syntax to specify the value of the ReceivedIdocRelease binding property:

    DOCTYPE1=DOCREL1;DOCTYPE2=DOCREL2
    For example, assume that the release number of MATMAS05 is 620, that the release number of DEBMAS05 is 640, and that the release number of other types of IDOCs is 710. For this example, SYSREL is 710. In this scenario, set the ReceivedIdocRelease binding property to the following value:
    MATMAS05=620;DEBMAS05=640
  • If the release numbers for the different types of IDOCs are not the same and are lower than SYSREL, each type must be set. To do this, use the following syntax to specify the value of the ReceivedIdocRelease binding property:

    DefaultRelease;DOCTYPE1=DOCREL1;DOCTYPE2=DOCREL2
    For example, assume that the release number of MATMAS05 is 620, that the release number of DEBMAS05 is 640, and that the release number of other types of IDOCs is 700. For this example, SYSREL is 710. In this scenario, set the ReceivedIdocRelease binding property to the following value:
    700;MATMAS05=620;DEBMAS05=640

STATUS

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

REFERENCES

For more information about how to receive SAP IDOCs in BizTalk Server, visit the following Microsoft Developer Network (MSDN) website:
How to receive SAP IDOCs in BizTalk Server
For more information about how to use BizTalk Server to send IDOCs to SAP, visit the following MSDN website:
How to use BizTalk Server to send IDOCs to SAP

Properties

Article ID: 2388784 - Last Review: May 7, 2011 - Revision: 4.0
Keywords: 
kbautohotfix kbqfe kbhotfixserver kbfix kbbtsadapters kbsurveynew kbexpertiseadvanced kbbiztalk2009presp1fix KB2388784

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