SAP Integration Suite is the cloud integration platform that SAP operates and that is subscribed to on SAP BTP. It reaches on-premise systems through SAP Cloud Connector, and Edge Integration Cell covers scenarios where data must never leave the company network.
SAP Integration Suite is an integration platform as a service (iPaaS) that SAP operates on SAP Business Technology Platform (SAP BTP), in the Cloud Foundry environment. SAP and non-SAP applications, whether in the cloud or on premise, connect to each other through the same platform.
01 / 05
SAP Integration Suite capabilities
SAP Integration Suite is not a single block; it consists of capabilities activated in the subaccount as they are needed:
SAP Business Accelerator Hub holds prepackaged integration content for SAP applications, for example flows between SAP SuccessFactors and SAP ERP or to the Ariba network. A package is copied into the tenant and used after configuration. A package whose parameters are only configured keeps receiving SAP's updates; a package whose content is modified cannot receive them.
02 / 05
Connecting to on-premise systems
The SAP Integration Suite cloud tenant reaches on-premise systems through SAP Cloud Connector. Cloud Connector opens the connection from the premises towards the cloud, so no inbound port is opened in the firewall; requests from the cloud then travel through this tunnel to on-premise systems. An on-premise SAP system sends IDoc or SOAP messages to the tenant over HTTPS. The cloud tenant has only a receiver adapter for RFC.
Where SAP Integration Suite sitsThe tenant runs on SAP BTP; it reaches on-premise systems through SAP Cloud Connector and connects to cloud applications with its own adapters.
For scenarios where data must never leave the company network, there is Edge Integration Cell. The flow is designed and monitored in the cloud but runs on the company's own Kubernetes cluster. SAP describes this option for security and compliance requirements and as a migration path for on-premise scenarios of SAP PI customers. Operating the cluster, the database and the updates is the customer's job.
03 / 05
Event-driven integration: Advanced Event Mesh
Event-driven integration is used when a change in one system has to reach several systems at once. A change in SAP S/4HANA or SAP ECC is captured as an event by the event add-on for ERP and published to a topic in Advanced Event Mesh. SAP CPI (Cloud Integration), non-SAP applications and CAP applications built on SAP BTP take the event from their own queues; a subscriber that is offline at that moment processes the event when it reconnects.
Event flow from ERP to Advanced Event MeshA change is captured as an event in SAP S/4HANA or SAP ECC, filtered in Advanced Event Mesh and delivered from each subscriber's queue.
Advanced Event Mesh is priced separately from the Event Mesh capability included in the SAP Integration Suite subscription; it carries larger messages and joins several brokers into one network. Like Edge Integration Cell, it can also be deployed on the company's own Kubernetes cluster.
04 / 05
What changes for teams coming from SAP PI/PO
Topic
SAP PI/PO
SAP Integration Suite
Where it runs
On premise, AS Java
Cloud tenant on SAP BTP; optional Edge Integration Cell
Design
ESR and Integration Directory
iFlow editor in the web UI
Mapping
Graphical mapping, XSLT, Java
Graphical mapping, XSLT, Groovy and JavaScript scripts
Publishing APIs
Services are exposed as SOAP or REST endpoints and can be published in the Services Registry
API Management: proxies, OAuth and quota policies, Developer Hub and API Analytics
Event-driven communication
No structure suited to an event-driven architecture; where needed, the JMS adapter connects to an external JMS provider
Publish and subscribe with Advanced Event Mesh; AMQP, Kafka and Advanced Event Mesh adapters in SAP CPI (Cloud Integration)
B2B partners
The B2B add-on brings the AS2, OFTP and X.400 adapters and the EDI separator; each partner is defined as a communication party in the Integration Directory
Trading Partner Management: partner profiles and agreements; agreements are pushed to the Partner Directory and messages run through one generic flow
Monitoring
Message monitor, alert rules
Monitor, message processing log (MPL), SAP Cloud ALM
Maintenance
7.5 mainstream maintenance ends at the end of 2027
SAP updates the service with regular software increments
From SAP PO to SAP Integration SuiteScenarios move from a server on the premises to a tenant that SAP operates, using SAP's assessment and migration tools.
