FIX: NCO BAPI response structure is different from ClassicRFC when BAPI response is empty
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 the scenario where no orders are found, if you use ClassicRFC library, there is no record in the output, which is correct. However, when you use WCF-SAP NCO adapter, there may be a record that resembles the following in the output:
<SALES_ORDERS> <BAPIORDERS xmlns="<Placeholder>"/></SALES_ORDERS>
Cumulative update informationThe fix that resolves this issue is included in the following cumulative update for BizTalk Server:
Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section.
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.
Article ID: 3192680 - Last Review: 10/10/2016 21:46:00 - Revision: 1.0
Microsoft BizTalk Adapter Pack 2013, Microsoft BizTalk Server 2013 Branch, Microsoft BizTalk Server 2013 Developer, Microsoft BizTalk Server 2013 Enterprise, Microsoft BizTalk Server 2013 Standard
- kbqfe kbsurveynew kbexpertiseadvanced kbfix kbbts KB3192680