FIX: When the BizTalk Server SAP adapter reads a valid SAP sequence of zeros, the adapter throws an exception and ends the current operation

The current implementation of the Microsoft BizTalk Server SAP adapter that is included in the Microsoft BizTalk Adapter Pack 1.0 has a configuration property that is named the EnableSafeTyping property. The EnableSafeTyping property is a Boolean property. The EnableSafeTyping property controls the behavior of the adapter when the adapter handles values of the following SAP data types:

• DATS
• TIMS
• NUMC

By default, the value of the EnableSafeTyping property is false. Therefore, values of the SAP data types are converted to strongly typed variables in the Microsoft .NET Framework. In SAP, empty values of the DATS SAP data type and of the TIMS SAP data type are represented by a sequence of zeros. However, when the adapter reads a valid SAP sequence of zeros, the adapter throws an exception and ends the current operation. The adapter does this instead of converting the valid SAP sequence of zeros to a valid null value in the .NET Framework.

For example, you have an empty DATS SAP data type value of 00000000 and an empty TIMS SAP data type value of 000000. When the adapter reads these values, the adapter throws an exception and ends the current operation.

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 the problem described in this article. 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 the BizTalk Adapter Pack 1.0 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 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.

BizTalk Server 2006 R2, 32-bit version

BizTalk Server 2006 R2, 64-bit version

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 hotfix adds a new binding property that is named the DataTypesBehavior property to the adapter. The DataTypesBehavior property is a complex property that contains the following sub-properties:

• DateTimeMaxToDats
• DateTimeMinToDats
• DateTimeMaxToTims
• DateTimeMinToTims
• DatsMaxToDateTime
• DatsMinToDateTime
• TimsMaxToDateTime
• DateTimeNullToDats
• DateTimeNullToTims
• InvalidDatsToDateTime
• InvalidNumcToInt
• InvalidTimsToDateTime
• EmptyDatsToDateTime

Therefore, when you use the EnableSafeTyping property set to false, you can manually control how the data types are converted.

For example, the DateTimeMaxToDats property controls the behavior when the adapter converts the DateTimeMax value (the .NET DateTime.MaxValue value) to the DATS SAP data type. The .NET DateTime.MaxValue value can be present only in a request message. The adapter must convert the value to the DATS SAP data type when it sends the value to SAP. Therefore, the DateTimeMaxToDats property controls the behavior of how the adapter parses the request message.

As another example, the DatsMaxToDateTime property controls the behavior when the adapter converts the DatsMax value (the SAP DATS MaxValue value) to the DateTime data type. The other properties follow the same logic.

For more information about software update terminology, click the following article number to view the article in the Microsoft Knowledge Base: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.