Lesson 2 of 6
Integration architecture: managed gateway, add-ons and APIs
9 min
Listen to this lesson
SAP Integration Suite, managed gateway for spend management and SAP Business Network (the managed gateway) is SAP's integration component between SAP Ariba solutions, SAP Business Network and the ERP. SAP's learning material traces the name: SAP Ariba Cloud Integration Gateway (CIG) became SAP Integration Suite, managed gateway in May 2022, and was fully replaced by the current name in January 2023. The S/4HANA add-on followed the same path. The managed gateway runs on SAP BTP and comes with SAP-delivered mapping content between the ERP's formats and the network's native cXML.
Connection options
| Option | How it works | When it fits |
|---|---|---|
| Managed gateway with the add-on (on premise or private cloud) | An add-on in S/4HANA sends and receives documents (IDocs or proxies) and connects to the managed gateway on BTP | Standard scenarios from S/4HANA private cloud or on premise; Contoso's choice |
| Managed gateway, native connection (S/4HANA Cloud Public Edition) | Communication arrangements in the cloud ERP connect to the managed gateway | Public Edition subsidiaries |
| Managed gateway plus SAP Integration Suite (Cloud Integration) | Custom iFlows extend or route messages before or after the gateway | Several ERPs, custom routing, non-SAP systems |
| APIs | Ariba and Business Network APIs (REST, OAuth) for reporting and custom extensions | Analytics, special integrations, not core document flow |
| Legacy middleware | SAP Process Orchestration with older adapters | Not for new work; Contoso is retiring PO |
Integration options; the managed gateway is SAP's standard path.
Step by step: Contoso's connection setup
- Install and configure the managed gateway add-on in CMD, with the connection to the managed gateway test project.
- In the managed gateway portal, create a project for the test environment and connect Contoso's Ariba test realm and Business Network test account.
- Activate the scenarios in scope: guided buying requisition to S/4HANA, PO collaboration, invoicing, master data export, sourcing award.
- Map Contoso's cross-references: company code 1710, purchasing organization 1710, purchasing group 001, plants 1710 and 1720.
- Run the managed gateway's connection tests and send one test document per scenario; read the transaction monitor in the portal.
- Transport the add-on configuration to CMQ and repeat; production connects only after the cutover approval.
Where messages can fail
Each hop has its own monitor, and testers need access to all of them. In S/4HANA: the add-on's message monitor and the IDoc or proxy monitors. In the managed gateway portal: the transaction tracker with status per document and mapping errors. In Business Network: the buyer account's inbox and outbox, with document status and errors. On the supplier side: the supplier's test account. A test that finds a missing invoice should be able to say in which of these four places it stopped.
| Hop | Monitor | Typical failure |
|---|---|---|
| S/4HANA to add-on | Add-on message monitor; IDoc or proxy monitor | Output not triggered; partner not set up for network |
| Add-on to managed gateway | Managed gateway transaction tracker | Mapping error; missing cross-reference |
| Gateway to Business Network | Buyer account outbox | Supplier not enabled; trading relationship missing |
| Network to supplier | Supplier account inbox | Routing rule sends to wrong account or email |
Choosing between standard content and extensions
The managed gateway's strength is SAP-maintained mapping content: when SAP changes a document format on Business Network or in S/4HANA, the mappings are updated centrally. Every custom mapping or Cloud Integration extension takes some of that benefit away, because Contoso then owns its maintenance and its regression. Theo's rule is to use the gateway's own extension points (custom field mappings in the portal) before building an iFlow, and to document every extension with the test case that protects it.
| Need at Contoso | Solution | Ownership |
|---|---|---|
| Standard PO, confirmation, ship notice, invoice | Gateway standard content | SAP maintains mappings |
| Rotor line asset number on service POs | Custom field mapping in the gateway portal | Theo's team, with one regression case |
| Copy of every invoice to a document archive | Cloud Integration iFlow after the gateway | Theo's team, with monitoring and a regression case |
Extensions are owned, documented and tested by Contoso.
What would you do?
A test PO for an MRO supplier shows "sent" in S/4HANA but never appears in the supplier's test account. Where should Theo look first?
- The managed gateway (formerly CIG) is SAP's standard integration for Ariba and Business Network.
- Private cloud and on-premise S/4HANA connect through the add-on; Public Edition connects natively.
- Messages are mapped to cXML; Cloud Integration is for extensions, not the core path.
- Four hops, four monitors: S/4HANA add-on, gateway tracker, buyer account, supplier account.
Check your understanding · not graded
Lesson check
1. What was the managed gateway called before May 2022?
2. How does S/4HANA private cloud connect to the managed gateway?
3. Into which format does the managed gateway map POs for Business Network?
4. Where did Contoso's first Riverbend invoice fail?