Microsoft KB Archive Search

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.

  1. Home
  2. FIX: NCO BAPI response structure is different from ClassicRFC when BAPI response is empty

FIX: NCO BAPI response structure is different from ClassicRFC when BAPI response is empty

View products that this article applies to.

Symptoms

This issue occurs when you use a WCF-SAP NCO adapter in BizTalk Server. For example:

When you call BAPI_SALESORDER_GETLIST, the response is identical when orders are found. For a scenario in which no orders are found, if you use the ClassicRFC library, there is no record in the output. This is correct. However, when you use the WCF-SAP NCO adapter, you may see a record in the output that resembles the following : 
<SALES_ORDERS>
     <BAPIORDERS xmlns="<Placeholder>"/>
</SALES_ORDERS>


↑ Back to the top

Resolution

Cumulative update information

The fix that resolves this issue is included in the following cumulative update for BizTalk Server:

↑ 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

References

Learn about the service pack and cumulative update list for BizTalk Server.

Learn about BizTalk Server hotfixes and cumulative update support .

Third-party information disclaimer
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.

↑ Back to the top

Keywords: kbqfe, kbsurveynew, kbexpertiseadvanced, kbfix, kbbts, kb

↑ Back to the top

Article Info
Article ID : 3192680
Revision : 5
Created on : 8/16/2017
Published on : 8/16/2017
Exists online : False
Views : 264