Symptom
- The RFC receiver interface in SAP Cloud Integration is unable to maintain transactional integrity when calling multiple BAPIs in sequence within the same Logical Unit of Work (LUW). Specifically, the "BAPI_TRANSACTION_COMMIT" does not persist the transaction after successful creation of sales orders due to the calls being made in different sessions.
- The issue occurs when the input to SAP Cloud Integration results in multiple orders, and the "Send Confirm Transaction" option in the RFC adapter commits individual order creations instead of committing all orders collectively after successful creation.
- Attempts to use HTTP session reuse and Transaction Handling options in the integration flow did not resolve the issue, as the RFC calls continue to go through different sessions.
Read more...
Environment
Product
Keywords
LOD-HCI-PI-CON-RFC; RFC Adapter; BAPI_TRANSACTION_COMMIT; LUW; Logical Unit of Work; JCo Session; Transactional Integrity; Wrapper Function Module; Sales Order; SAP Integration Suite. , KBA , LOD-HCI-PI-CON-RFC , RFC Adapter , Problem
About this page
This is a preview of a SAP Knowledge Base Article. Click more to access the full version on SAP for Me (Login required).Search for additional results
Visit SAP Support Portal's SAP Notes and KBA Search.
SAP Knowledge Base Article - Preview