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

Velja za: Microsoft BizTalk Adapter Pack 2013BizTalk Server 2013 BranchBizTalk Server 2013 Developer


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>


Cumulative update information

The 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.