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: DBCS characters are corrupted in an IDOC that is sent by using the BizTalk Adapter for mySAP Business Suite


View products that this article applies to.

Symptoms

In Microsoft BizTalk Server 2004, when you use the Microsoft BizTalk Adapter 2.0 for mySAP Business Suite to send an Intermediate Document (IDOC) to a SAP system, the double-byte character set (DBCS) characters in the IDOC become corrupted. DBCS characters include Chinese characters and Japanese characters.

↑ Back to the top


Resolution

A supported hotfix is now available from Microsoft. However, this hotfix is intended to correct only the problem that this article describes. Apply this hotfix only to systems that are experiencing this specific problem.

To resolve this problem, submit a request to Microsoft Online Customer Services to obtain the hotfix. To submit an online request to obtain the hotfix, visit the following Microsoft Web site:Note If additional issues occur or 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. To create a separate service request, visit the following Microsoft Web site:

Prerequisites

This hotfix requires the SAP .NET Connector for visual studio .NET 2003 version 1.0.3.

Restart requirement

You do not have to restart your computer 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 tool in Control Panel.
   Date         Time   Version            Size    File name
   -----------------------------------------------------------------------
   16-Sep-2004  01:41  2.0.317.0         543,448  Sapadaptermanagement.dll  
   16-Sep-2004  01:41  2.0.317.0          84,688  Saptransmitter.dll  

↑ 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

For this hotfix to work, install the SAP .NET Connector for visual studio .NET 2003 version 1.0.3 installed. Then you must run BizTalkSAPConfig.exe with the /i option. To run BizTalkSAPConfig.exe, follow these steps:
1.Click Start, click Run, cmd, and then click OK.
2.At the command prompt, change the current folder to the adapter installation folder.
3.Type BizTalkSAPConfig /i, and then press ENTER.
4.Type exit, and then press ENTER to close the command prompt.
Note The adapter installation folder is typically located in the <install location>\Microsoft BizTalk Adapter v2.0 for MySAP Business Suite folder.

↑ Back to the top


References

For more information about Microsoft BizTalk Server 2004, visit the following Microsoft Web site: For additional information about the standard terminology that is used to describe Microsoft software updates, 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: kbbug, kbfix, kbqfe, kbprb, kbhotfixserver, KB884551

↑ Back to the top

Article Info
Article ID : 884551
Revision : 3
Created on : 11/15/2007
Published on : 11/15/2007
Exists online : False
Views : 413