Microsoft KB Archive/925851
Article ID: 925851
Article Last Modified on 11/15/2007
- Microsoft BizTalk Adapter 2.0 for mySAP Business Suite
When you use Microsoft BizTalk Adapter 2.0 for mySAP Business Suite to generate a schema for a custom intermediate document (IDoc), the schema is not validated as expected.
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:
You must have Microsoft BizTalk Adapter 2.0 for mySAP Business Suite or Microsoft BizTalk Adapter 2.0 for mySAP Business Suite Service Pack 1 installed to apply this hotfix.
You do not have to restart the computer after you apply this hotfix.
Hotfix replacement information
This hotfix does not replace any other hotfixes.
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|
Note Because of file dependencies, the most recent hotfix that contains these files may also contain additional files.
Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section.
This problem may occur if an SAP data type is not mapped correctly in the schema. For example, this problem may occur if the SAP QUAN data type is mapped as the string data type instead of as the decimal data type.
For more information, 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
The third-party products that this article discusses are manufactured by companies that are independent of Microsoft. Microsoft makes no warranty, implied or otherwise, about the performance or reliability of these products.
Keywords: kbbtsadapters kbbts kbbug kbfix kbpubtypekc kbhotfixserver kbqfe KB925851