Aribaadvanced

Managed Gateway for Spend Management and SAP Business Network: Current Integration Architecture (Part 6)

Key takeaway

Understand the current managed gateway naming and architecture for integrating SAP Ariba and SAP Business Network with SAP ERP or S/4HANA, replacing the retired CIG terminology.

Explanation

SAP's current product name is SAP Integration Suite, managed gateway for spend management and SAP Business Network. It replaced the earlier SAP Integration Suite, managed gateway name in January 2023, which had itself replaced the retired SAP Ariba Cloud Integration Gateway (CIG) name.

The managed gateway provides SAP-managed integration content and connectivity for SAP Business Network, SAP Ariba Sourcing, and SAP Ariba Buying and Invoicing scenarios with SAP ERP or S/4HANA. Existing UIs or legacy documentation can still show older naming, so support teams should recognize the continuity without treating CIG as the current product name.

Integration design includes realm/tenant connection, backend add-on or supported connectivity, master-data and transactional mappings, certificates/credentials and monitoring.

Do not customize standard integration content unless the business gap genuinely requires it. Excessive mapping changes increase upgrade/support effort.

When an interface fails, separate gateway transport/connectivity from application-document validation in Ariba/S/4HANA.

Real project scenario

A support team searched only for 'CIG' documentation and assumed a new product had replaced their integration. Mapping the retired names to the current Managed Gateway for Spend&Network clarified the upgrade and support path.

Common mistakes

Calling CIG the current product name.
Treating connectivity and business validation as one issue.
Customizing standard mappings unnecessarily.
Ignoring certificate lifecycle.
Monitoring only outbound messages from S/4HANA.

Best practices

Use current product terminology.
Preserve standard managed content where possible.
Monitor both integration and business document status.
Govern credentials/certificates.
Document custom mappings explicitly.

Interview angle

Explain the product-name evolution from CIG to the current managed gateway and its role between Ariba/Business Network and ERP.

Practice this lesson

Quick check

1. Scenario — A support team searched only for 'CIG' documentation and assumed a new product had replaced their integration. In this Cloud Integration Gateway situation, which response best addresses the underlying design risk?

2. What is the primary purpose of SAP Ariba Cloud Integration Gateway (CIG) in the context of SAP Ariba solution integration?

3. Which type of SAP-side component is typically required to enable direct communication between SAP ERP/S4HANA and SAP Ariba Cloud Integration Gateway?

Interview questions

1. A senior architect is reviewing Cloud Integration Gateway. The project situation is: A support team searched only for 'CIG' documentation and assumed a new product had replaced their integration. What design changes, validation evidence and production controls would you require before approving the solution?

Answer it in your own words first, then compare.

2. Using this SAP project situation — A mid-size manufacturer implementing SAP Ariba Buying and Invoicing alongside an existing S/4HANA on-premise system initially assumed they would need to install and maintain a local Ariba adapter, based on prior experience with older Ariba projects — explain What Is Cloud Integration Gateway and Why Ariba Projects Need It. What should happen, which concepts or process steps matter, and what common mistake would you avoid?

Answer it in your own words first, then compare.

Practice more with Interview AI →

Reference-verified: the steps are checked against official SAP documentation and tutorials, and object and field names in the sample code are checked for consistency. The code has not been compiled or run on an SAP system by ERPClimb. Syntax marked release-dependent varies by SAP release, so check it in your own system.