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 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 :

     <BAPIORDERS xmlns="<Placeholder>"/>


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.


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

Learn about BizTalk Server hotfixes and cumulative update support.

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.

Need more help?

Expand your skills
Explore Training
Get new features first
Join Microsoft Insiders

Was this information helpful?

Thank you for your feedback!

Thank you for your feedback! It sounds like it might be helpful to connect you to one of our Office support agents.