Symptom
- When creating purchase orders ( PO ) in held status from SAP Ariba Sourcing through Managed Gateway for Spend&Network in SAP S/4HANA using the MEMORY_UNCOMPLETE parameter, the PO is not persisted in SAP S/4HANA.
- BAPI_PO_CREATE1 returns a purchase order number and the message Held purchase order XXXXX was created, but the PO is not saved and cannot be found in the system afterward.
- Direct execution of BAPI_PO_CREATE1 followed by BAPI_TRANSACTION_COMMIT successfully creates and saves the held PO, indicating the issue occurs during post-processing in the integration flow of Managed Gateway rather than within the BAPI itself.
Read more...
Environment
- SAP Ariba Sourcing via Managed Gateway for Spend&Network
- SAP S/4HANA
- SAP ERP
Product
SAP Ariba Sourcing, cloud edition all versions ; SAP Integration Suite, managed gateway all versions ; SAP Integration Suite, managed gateway for spend management and SAP Business Network all versions ; SAP Integration Suite, managed gateway for spend mgmt and SAP Business Network for SAP S/4HANA all versions
Keywords
Return structure, commit work, po number cleared, ariba sourcing, cig, erp, badi, postprocessing, quote order, held purchase order, commit prevention , KBA , BNS-ARI-CI-SRC-QMO , Managed Gateway for Sourcing - Quote Order , BNS-ARI-CI-SRC-CSUR , Managed Gateway for Sourcing - Contract Status , 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