Cloud Integration
The core. You design integration flows in the browser, map fields between systems, and deploy them to SAP's runtime. It was called SAP Cloud Platform Integration, and many teams still say CPI.
A partner's S/4HANA quote has a line for it, or someone asked whether the old PI/PO server can finally go. SAP Integration Suite is SAP's integration platform as a service, run on SAP Business Technology Platform (BTP). It's a bundle: Cloud Integration for building and running integration flows, API Management for publishing and securing APIs, and smaller tools for B2B partners, prebuilt connectors and migration planning. Whether you need it depends on how many connections you'll run, not on the fact that you run SAP.
What it is: SAP's cloud integration platform, sold as a service on SAP BTP. It's the successor SAP recommends to SAP Process Integration and Process Orchestration (PI/PO).
What it does: runs integration flows between SAP and other systems, cloud or on-premise, built from prebuilt packages on the SAP Business Accelerator Hub or designed from scratch.
Who it suits: companies with many flows, a PI/PO landscape to retire, or several SAP cloud products to connect. For one or two connections, a direct build is often less to license and run.
SAP Event Mesh and advanced event mesh, for event-driven messaging, are separate BTP services, often bought alongside the suite.
The core. You design integration flows in the browser, map fields between systems, and deploy them to SAP's runtime. It was called SAP Cloud Platform Integration, and many teams still say CPI.
One gateway for APIs from SAP or anything else, with policies for API keys, OAuth and rate limits, usage analytics, and a developer portal for the teams calling them.
For B2B and EDI work: message guidelines and mappings for standards like EDIFACT and X12, plus an agreement for each trading partner.
Prebuilt connectors to third-party cloud apps, such as CRMs and file storage, exposed through one common API style. Confirm it's still offered on your contract before planning around it.
Planning tools. One helps choose an integration approach per scenario. The other sizes how much of an existing PI/PO landscape can move across as it is.
An optional runtime you host yourself, so flows designed in the cloud can run inside your own network when the data has to stay there.
Count the flows you expect to run in two years, not the one in front of you. A handful that's likely to grow leans toward the suite. One Salesforce sync that will stay one sync rarely needs it.
Integration Suite is licensed through BTP, either as its own subscription or from a BTP credit contract. The model decides what extra flows and usage will cost you later.
Search the SAP Business Accelerator Hub. A package still needs mapping and testing against your own fields, but it's a head start over a blank flow.
Orders or invoices created in SAP through an interface can count under SAP's usage-based licensing. Confirm it with your account team before volumes grow.
The suite is a designer and a runtime, not a team. Someone still needs to know your SAP data and the other system's API.
If it does, ask about Edge Integration Cell, which runs flows on infrastructure you host.
It's SAP's integration platform as a service on SAP BTP. Its main parts are Cloud Integration for building and running flows between SAP and other systems, API Management, B2B tools for EDI partners, and planning tools for moving off older middleware. Many flows start from prebuilt packages on the SAP Business Accelerator Hub.
No, it's the successor. PI/PO (Process Integration and Process Orchestration) is SAP's older middleware, installed on your own servers. SAP has said mainstream maintenance for Process Orchestration 7.5 runs to the end of 2027, with extended maintenance after that, and it points PI/PO customers to Integration Suite. Migration Assessment helps size the move.
Two routes. If you already run Integration Suite, or plan to for other flows, build it there, starting from a prebuilt package on the Business Accelerator Hub if one fits. If Salesforce is the only connection, a direct build against SAP's APIs and Salesforce's API is usually lighter. n-frames builds that direct sync for accounts, orders or opportunities, logged and retried inside the integration itself.
No. It earns its license once you're running several flows and want one place to deploy them, handle errors and alert on failures. A business with one integration need often gets the same result sooner from a direct build.
That's integration between SAP's own modules, not with an outside system. It's how Materials Management, Financial Accounting and Sales and Distribution are configured to post to each other, so a goods receipt updates stock and creates the accounting entry, for example. It's configuration inside SAP, and Integration Suite doesn't touch it.