Docs / Connectors / SAP Ariba
SAP Ariba Connector
The ASAPIO connector for SAP Ariba handles master data integration between SAP ERP or S/4HANA and SAP Ariba. It operates alongside SAP Cloud Integration (CIG) or SAP Integration Suite, which manages transactional document flows — ASAPIO takes responsibility for keeping master data consistent across all connected systems. SAP certified.
This connector is configured via SAP GUI only. Event Studio is not supported. Detailed setup documentation is available to licensed customers — contact your ASAPIO representative.
Overview
| Layer | Handled by | Scope |
|---|---|---|
| Master data | ASAPIO Integration Add-on | Supplier master, accounting references, catalog data, user management synchronization |
| Transactional documents | SAP CIG / SAP Integration Suite | Purchase requisitions, purchase orders, and related procurement document flows |
Integration Scope
The ASAPIO Ariba connector covers the following integration scenarios:
- Connects multiple SAP ERP and S/4HANA backend systems to single or multiple Ariba realms
- Manages non-harmonized master data across backends using prefixing concepts
- Integrates supplier master data from sources including SAP MDG
- Supports user management integration via SAP IDM or Active Directory
- Operates in coexistence with SAP CIG or SAP Cloud Integration where already active
Master Data Objects
| Domain | Scope | Integration Focus |
|---|---|---|
| Supplier & core master data | Master data harmonization across backends | Consistent supplier records in all connected Ariba realms |
| Accounting references | Cost object and GL account validation | Prevent downstream posting errors in Ariba |
| Catalog & procurement references | Catalog management | Sourcing and buying process continuity |
| User management | SAP IDM / Active Directory integration | Synchronized user provisioning in Ariba |
Multi-System Support
A key differentiator of the ASAPIO Ariba connector is native support for multi-backend landscapes — multiple SAP ERP and S/4HANA systems feeding into one or more Ariba realms. The prefixing concept ensures master data records from different backends remain identifiable and non-conflicting within Ariba.
Boehringer Ingelheim implemented SAP Ariba as a global buying platform and selected ASAPIO to integrate their multiple SAP backend systems during an S/4HANA transformation. ASAPIO managed the cross-system master data complexity while SAP CIG handled transactional flows.
Deployment Guidance
- Plan for multi-system rollout and data governance from the start — master data harmonization is an explicit workstream, not an afterthought.
- Define coexistence boundaries clearly when SAP CIG or SAP Integration Suite is already active; ASAPIO and CIG handle distinct layers and operate in parallel.
- Include a duplicate-handling strategy for supplier master data when multiple backends feed the same Ariba realm.
- Post go-live, managed support and optimization cycles ensure ongoing data quality and process consistency.