BizTalk: Date format (YYMMDD) not working properly with EDI Interchange

When you set the date format to YYMMDD for an EDI interchange, BizTalk changes the format to CCYYMM especially when sending batched EDI interchange. This is a known bug that Microsoft has identified and released a hot fix for the issue.
 
 

FIX: The BizTalk Server native EDI functionality swaps the GS02 field and the GS03 field in BizTalk Server 2006 R2

 
Article ID

:

954557

Last Review

:

August 29, 2008

Revision

:

1.0
 

SYMPTOMS

In Microsoft BizTalk Server 2006 R2, you configure the BizTalk Server native Electronic Data Interchange (EDI) functionality to receive 997 functional acknowledgements from a trading partner. However, when a functional acknowledgement is received from a trading partner, the BizTalk native EDI functionality swaps the code field of the sender (GS02) and the code field of the receiver (GS03).

Note This problem also occurs with generated 997 technical acknowledgements when the 997 technical acknowledgements are batched by using the BizTalk Server 2006 R2 batching functionality.

 

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. 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 and the BizTalk EDI/AS2 Runtime installed to apply this hotfix.

Restart requirement

You do not have to restart the computer after you apply this hotfix. However, you must restart the BizTalk Server services 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.

File name

File version

File size

Date

Time

Platform

Microsoft.biztalk.edi.batchinghelper.dll

3.6.1471.2

91,192

29-Jul-2008

00:28

x86

Microsoft.biztalk.edi.batchmarkerpipelinecomponent.dll

3.6.1471.2

58,456

29-Jul-2008

00:28

x86

Microsoft.biztalk.edi.ediintpipelines.dll

3.6.1471.2

83,008

29-Jul-2008

00:28

x86

Microsoft.biztalk.edi.edipipelines.dll

3.6.1471.2

58,424

29-Jul-2008

00:28

x86

Microsoft.biztalk.edi.messagecore.dll

3.6.1471.2

341,048

29-Jul-2008

00:28

x86

Microsoft.biztalk.edi.partneragreementmanager.dll

3.6.1471.2

414,800

29-Jul-2008

00:28

x86

Microsoft.biztalk.edi.pipelinecomponents.dll

3.6.1471.2

173,120

29-Jul-2008

00:28

x86

Microsoft.biztalk.ediint.pipelinecomponents.dll

3.6.1471.2

128,072

29-Jul-2008

00:28

x86

STATUS

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

MORE INFORMATION

This hotfix guarantees that the GS02 and GS03 fields are preserved correctly on incoming 997 functional acknowledgements. Additionally, those fields are set correctly on outgoing 997 functional acknowledgements. If you have already built applications that use the GS02 and GS03 fields for incoming 997 functional acknowledgements in reverse, apply this hotfix only after you remove that logic.

This hotfix also contains the following hotfixes:

942733 (http://support.microsoft.com/kb/942733/) FIX: Error message when you try to verify the signature of an incoming AS2 message or of an incoming MDN message on a computer that is running BizTalk Server 2006 R2
948747 (http://support.microsoft.com/kb/948747/) FIX: You may receive an event ID 5753 error message when you try to use the BizTalk Server 2006 R2 EDI functionality
953388 (http://support.microsoft.com/kb/953388/) FIX: You may experience poor performance when you try to split large EDI interchanges in BizTalk Server 2006 R2
947459 (http://support.microsoft.com/kb/947459/) FIX: The GS04 header value uses the CCYYMM format instead of the YYMMDD format in BizTalk Server 2006 R2
 
 
 
 
This entry was posted in BizTalk. Bookmark the permalink.

1 Response to BizTalk: Date format (YYMMDD) not working properly with EDI Interchange

  1. Pingback: Biztalk gs03 | Jdunplugged

Leave a comment