FIX: An update that adds a fourth option to process incoming EDI messages in BizTalk Server 2006 R2 is available

By default, the EDI Receive Pipeline supports the following three processing modes in Microsoft BizTalk Server 2006 R2:

• Split Interchange as Transaction Sets - Suspend Transaction Set on Error: This is the traditional processing model. If the interchange is validated successfully, the interchange is split into individual transaction sets. If one or more transaction sets in the interchange fails validation, only the incorrect transaction set is suspended.
• Preserve Interchange� Suspend Interchange on Error: A single XML interchange is generated for the whole batched interchange. If one or more transaction sets in the interchange fails validation, the whole interchange is suspended. In this processing mode, the interchange structure is always preserved.
• Preserve Interchange� Suspend Transaction Sets on Error: A single XML interchange is generated for the whole batched interchange. If one or more transaction sets in the interchange fails validation, only the incorrect transaction set is suspended. In this processing mode, the interchange structure may not be preserved.

This article describes an update that adds a fourth option to process incoming EDI messages:

• Split Interchange as Transaction Sets � Suspend Interchange on Error: This is the new processing model. If the interchange is validated successfully, the interchange is split into individual transaction sets. If one or more transaction sets in the interchange fails validation, the whole interchange is suspended.

These selections are enabled at the Party Level by using controls in the Party/EDI Properties in BizTalk Server 2006 R2 Administration.

Update 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: 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 BizTalk Server 2006 R2 installed to apply this hotfix.

Restart requirement

You do not have to restart the computer after you apply this hotfix. However, you have to restart the BizTalk services after you apply this hotfix.

Hotfix replacement information

This hotfix does not replace a previously released hotfix.

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.

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

For more information about the three processing modes, visit the following Microsoft Web site: