Notice: This website is an unofficial Microsoft Knowledge Base (hereinafter KB) archive and is intended to provide a reliable access to deleted content from Microsoft KB. All KB articles are owned by Microsoft Corporation. Read full disclaimer for more details.

FIX: Outgoing 837 interchanges may contain incorrect GS and ST segment values in Microsoft BizTalk Server 2006 R2


View products that this article applies to.

Symptoms

Consider the following scenario:
  • You use Microsoft BizTalk 2006 R2 to send Electronic Data Interchange (EDI) messages.
  • On the GS and ST Segment Definition page, under the Party as Interchange Receiver node in the EDI Properties dialog box, you create rows under the "Transaction set specific group header" (GS) section. Then, you enter one of the following values into the For ST1 field of three rows:
    • 837_D - Health Care Claim: Dental
    • 837_I - Health Care Claim: Institutional
    • 837_P - Health Care Claim: Professional
  • You click to select the Default box for one of the rows.
In this scenario, the outgoing 837 interchanges may contain incorrect GS and ST segment values.

↑ Back to the top


Cause

This problem occurs because of an error in the EDI components of BizTalk Server 2006 R2. BizTalk Server does not map to the For ST1 field. Therefore, BizTalk Server does not produce the correct values for GS and ST segments for 837_D, 837_I, and 837_P interchanges. Instead, it always uses the values from the row that is selected as the default. Therefore, incorrect 837 documents are produced when the actual 837 document type does not match the default type.

↑ Back to the top


Resolution

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 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 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 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.
Collapse this tableExpand this table
File nameFile versionFile sizeDateTimePlatform
Microsoft.biztalk.edi.batchinghelper.dll3.6.1450.291,19218-Apr-200820:04x86
Microsoft.biztalk.edi.ediintpipelines.dll3.6.1450.283,00818-Apr-200820:04x86
Microsoft.biztalk.edi.edipipelines.dll3.6.1450.258,42418-Apr-200820:04x86
Microsoft.biztalk.edi.messagecore.dll3.6.1450.2341,04818-Apr-200820:04x86
Microsoft.biztalk.edi.pipelinecomponents.dll3.6.1450.2173,12018-Apr-200820:04x86
Note Because of file dependencies, the most recent hotfix that contains these files may also contain additional files.

↑ Back to the top


Status

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

↑ Back to the top


More information

To access the GS and ST Segment Definition, follow these steps:
  1. In the Parties node of the BizTalk Server Administration Console, right-click a party.
  2. Click EDI Properties.
  3. Under the X12 Properties, Party as Interchange Receiver, and X12 Interchange Envelope Generation nodes in the console tree, click GS and ST Segment Definition.

For more information about how to configure GS and ST Segment Definition under the X12 Interchange Envelope Generation node, visit the following Microsoft Web site:
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

↑ Back to the top


Keywords: KB951760, kbqfe, kbhotfixserver, kbfix, kbexpertiseinter, kbbiztalk2006r2sp1fix, kbautohotfix

↑ Back to the top

Article Info
Article ID : 951760
Revision : 3
Created on : 9/2/2009
Published on : 9/2/2009
Exists online : False
Views : 315