Assume that you want to run Business Application Programming Interface (BAPI) transactions in SAP by using Microsoft BizTalk Server. Accordingly, you have set up a BizTalk orchestration to send messages one after another to an SAP server by using the same connection. In this situation, you notice that these messages are sent to different SAP transactions. This breaks BAPI transaction.
This issue is fixed in the following cumulative updates for BizTalk Server:
Cumulative Update 5 for BizTalk Server 2016
Cumulative Update 6 for BizTalk Adapter Pack 2013
Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section.
For information about the service packs and cumulative update list for BizTalk Server, click the following article number to view the article in the Microsoft Knowledge Base:
2555976 Service pack and cumulative update list for BizTalk Server
For more information about BizTalk Server hotfixes, click the following article number to view the article in the Microsoft Knowledge Base:
2003907 Information about BizTalk hotfixes and Service Pack support