Loading…
We have delivered Ariba Sourcing integration with SAP ECC in a live production environment. Sourcing events flow to ECC purchase orders — not in theory, in practice.
The Ariba Sourcing + SAP ECC integration is one of the most commonly requested and least commonly delivered integrations in the SAP ecosystem. Most implementations treat it as a future-phase item, or deliver a partial connection that requires manual intervention to complete the document flow. Navaastra has closed this loop in production.
Our implementation covers the full sourcing-to-PO cycle: sourcing event created and awarded in Ariba, purchase requisition created in ECC, requisition converted to purchase order, and PO confirmation synced back to Ariba. Vendor master is kept in sync via BTP iFlows — no dual maintenance, no manual re-keying.
We use SAP BTP Integration Suite as the middleware layer — the SAP-endorsed approach that positions your landscape for S/4HANA migration and avoids the technical debt of custom RFC connections or legacy PI/PO.
This integration has run in a live SAP ECC environment — sourcing events converting to real POs. Not a proof-of-concept, not a demo environment.
We use BTP Integration Suite as standard — not custom middleware, not legacy PI/PO. The architecture is SAP-endorsed and ready for S/4HANA migration.
Status updates flow both ways: PO confirmations and GR/IR from ECC surface in Ariba, giving procurement full visibility without dual-system maintenance.
Awarded sourcing events in Ariba trigger purchase requisitions in SAP ECC automatically — no manual creation, no re-keying.
Approved PRs convert to purchase orders in ECC via configured sourcing rules, contract references, and vendor assignment logic.
Supplier records maintained in Ariba SLP are synchronised to SAP vendor master (LFA1) — keeping both systems consistent without manual updates.
Ariba contracts serve as the source of truth for pricing and terms. Contract references flow to SAP POs, enforcing compliance automatically.
We use SAP BTP Integration Suite as the middleware layer — a clean, SAP-endorsed approach that avoids point-to-point connections and supports future extensions.
For on-premise ECC landscapes, BTP Cloud Connector provides a secure, audited tunnel — no firewall exceptions, no custom RFC exposure.
PO confirmation, goods receipt, and invoice status flow back from ECC to Ariba — giving procurement teams full visibility without switching systems.
Integration failures are captured, logged, and alerted through BTP monitoring — with clear error messages that procurement teams can act on without IT involvement.
We map the exact sourcing-to-PO flow, identify vendor master rules, contract reference logic, and document numbering requirements in your ECC system.
We configure BTP Integration Suite iFlows and Cloud Connector — establishing a secure, monitored channel between Ariba and your ECC landscape.
Each integration scenario — sourcing event, PR creation, PO sync, vendor master — is built and tested against your actual SAP system, not a generic sandbox.
End-to-end testing with your procurement team across real sourcing scenarios. Go-live with monitoring in place and hypercare support during stabilisation.
Yes. Our Ariba Sourcing + SAP ECC integration has been delivered in a live production environment — handling real sourcing events, vendor master synchronisation, and contract-to-PO flows.
We use SAP BTP Integration Suite as middleware, with BTP Cloud Connector for on-premise ECC connectivity. This is the SAP-endorsed approach — clean, auditable, and future-proof.
Yes. Our production delivery is on SAP ECC 6.0 EhP7. We also support S/4HANA landscapes using the same BTP middleware approach.
We support RFQ, RFP, reverse auction, and direct award scenarios. The resulting documents flow to ECC as purchase requisitions, which then convert to purchase orders through standard SAP sourcing rules.
Supplier records from Ariba SLP are synchronised to SAP vendor master via BTP iFlows. New suppliers, address changes, and banking details are propagated without manual re-entry in ECC.
BTP Integration Suite logs all failures with message content and error detail. Alerts are configured for procurement-critical failures. Most issues are self-service resolvable — we design the error messages for procurement teams, not IT administrators.
Talk to a consultant who has delivered this in production. We'll assess your current landscape and outline the integration approach — within 24 hours.