Now accepting guest editorial from SAP, Oracle, Workday and ServiceNow practitioners.Pitch a guide
The Sign-Off Table

Lesson 1 of 6

Integration Suite overview

10 min

Listen to this lesson

0:00 / 5:01

SAP Integration Suite is SAP's integration platform as a service on SAP Business Technology Platform (BTP). It is not one tool but a set of capabilities you enable as you need them, all reached from one Integration Suite home page in a BTP subaccount. For most integration specialists, the daily work happens in Cloud Integration, where you build and run integration flows (iFlows). The other capabilities matter because they change where a piece of integration logic should live.

Contoso Motor Co. is converting from SAP ECC 6.0 EHP 8 to SAP S/4HANA Private Edition under RISE, with a Q3 go-live. Its integration team, led by Theo, already sends purchase orders to Lakeside Components and receives orders from Great Lakes Fleet Services. In this course you will follow one of those interfaces, the outbound order to Lakeside, as it moves from Process Orchestration to Cloud Integration after go-live.

The capabilities

Cloud IntegrationDesign, deploy and run integration flows: adapters, mappings, routing, error handling. The core of process integration.
API ManagementExpose, secure and govern APIs through proxies, policies, products and a developer hub, with analytics.
Event MeshPublish-and-subscribe event brokering between SAP and non-SAP systems. It succeeds the standalone SAP Event Mesh service; SAP Integration Suite, advanced event mesh is a separate, larger-scale broker service for high volumes and multi-region networks.
Integration Advisor and Trading Partner ManagementB2B: message implementation guidelines (MIGs) and mapping guidelines (MAGs) in Integration Advisor; partner profiles, agreement templates and agreements in Trading Partner Management, activated into the Partner Directory for generic B2B flows.
Open ConnectorsPrebuilt connectors to third-party cloud applications.
Integration Assessment and Migration AssessmentChoose the right integration technology per interface, and rate each SAP Process Orchestration scenario Ready to migrate, Adjustment required or Evaluation required. The separate migration tool in Cloud Integration then converts supported integrated configurations into integration flows.
Main SAP Integration Suite capabilities as SAP Learning describes them. Your subscription and edition decide which ones you can enable.
The Sign-Off Table · thesignofftable.com/academy/sap-int-203

SAP Learning's administration course also lists OData Provisioning, Data Space Integration and Graph (part of API Management). And there is a deployment option worth knowing early: Edge Integration Cell, an optional hybrid runtime that lets you design and monitor in the cloud while running integration flows and APIs inside your own private landscape, so messages between two on-premise systems never leave your network.

Tenants, packages and artifacts

Cloud Integration runs in a tenant: an isolated runtime with its own content, security material and monitoring. Most programs use at least two tenants, one for development and test and one for production, and transport content between them. Inside a tenant, artifacts live in integration packages; an integration flow must belong to a package. Packages also hold value mappings, script collections and message mappings that several flows reuse.

Inside a Cloud Integration tenant, every flow belongs to a package, and flows reach secrets only by alias to the tenant's security material.
The Sign-Off Table · thesignofftable.com/academy/sap-int-203

The home page groups the work into Discover (prebuilt packages from the SAP Business Accelerator Hub), Design (your packages and artifacts), Monitor (message processing, deployed content, security material, stores and logs) and Settings. Before building anything, check Discover: SAP publishes ready-made packages for many SAP-to-SAP and SAP-to-cloud scenarios, and a configured standard package is cheaper to own than a custom flow.

  1. Does SAP publish standard content for this scenario?Yes → copy and configure the package from Discover · No → next question
  2. Is it mainly exposing an existing API to consumers with keys, quotas and a portal?Yes → API Management · No → next question
  3. Should many receivers react to a business event without the sender knowing them?Yes → Event Mesh · No → next question
  4. Is it a B2B exchange built on partner message standards?Yes → Integration Advisor and Trading Partner Management, with Cloud Integration runtime · No → build an integration flow in Cloud Integration
A first pass at where a new Contoso interface belongs. Integration Assessment formalizes this kind of decision.
The Sign-Off Table · thesignofftable.com/academy/sap-int-203

Where Contoso starts

Contoso's ECC landscape runs its interfaces through SAP Process Orchestration, and the conversion program keeps them there until hypercare ends, to limit go-live risk. After that they move to Cloud Integration in migration waves, well before PO 7.5 mainstream maintenance ends on December 31, 2027 (optional extended maintenance runs to the end of 2030). The Lakeside order flow, which runs on PO today and writes a file to Lakeside's SFTP server, is rebuilt here and switched in Wave 1 (procure to pay). Genuinely new interfaces, such as those for the planned Mexican acquisition, are built in Cloud Integration from the start. The S/4HANA systems CMD, CMQ and CMP connect to the cloud tenants through SAP Cloud Connector, which publishes selected on-premise endpoints to BTP without opening inbound firewall ports.

Contoso's hybrid landscape after the Lakeside flow's Wave 1 switch: S/4HANA calls the tenant over HTTPS, the tenant reaches back in only through Cloud Connector, and interfaces not yet migrated stay on Process Orchestration.
The Sign-Off Table · thesignofftable.com/academy/sap-int-203

What would you do?

Theo's team must send supplier master data changes from Contoso's S/4HANA system to a cloud procurement application. SAP publishes a standard integration package for that pair of systems. Kenji suggests building a custom flow because the team already knows how. What should Theo decide?

Key points
  • SAP Integration Suite is a set of capabilities on SAP BTP; Cloud Integration is where integration flows run.
  • API Management, Event Mesh, B2B tooling and the assessment capabilities change where logic should live.
  • Edge Integration Cell runs flows inside your own landscape while design and monitoring stay in the cloud.
  • Check prebuilt content in Discover before building a custom flow.

Check your understanding · not graded

Lesson check

  1. 1. In which Integration Suite capability do you design and run integration flows?

  2. 2. What does Edge Integration Cell add to SAP Integration Suite?

  3. 3. Where should an integration specialist look first for SAP-published integration content?

  4. 4. Every integration flow in Cloud Integration must belong to which container?