SAP Cloud Integration
SAP Integration Suite is the strategic integration platform for every SAP cloud landscape — replacing SAP PI/PO and consolidating process integration, API management, event-driven architecture, B2B/EDI, and on-premise connectivity under one managed service on BTP. We design, develop, and operate Integration Suite landscapes that are secure, observable, and built to scale.
Architecture
SAP Integration Suite — Capability Map
SAP Integration Suite bundles seven integration capabilities under one BTP subscription. Together they replace dedicated middleware (SAP PI/PO), standalone API gateways, and bespoke B2B adapters — consolidating the entire integration landscape onto a single managed platform.
Platform Architecture
SAP Integration Suite mediates all message flows between source and target systems — cloud-to-cloud, cloud-to-on-premise, and on-premise-only — as a managed multi-cloud service on BTP with a static set of public IP addresses for firewall allowlisting. On-premise connectivity runs over the standard Cloud Connector tunnel; we reference that mechanism rather than re-explain it here.
iFlow Design Patterns
Every integration is built as one of four standard patterns — synchronous request/reply, asynchronous fire-and-forget with guaranteed delivery, event-driven publish/subscribe via Advanced Event Mesh, or scheduled batch processing. We select the pattern based on your latency, coupling, and volume requirements rather than defaulting to one approach.
Adapter Ecosystem
Cloud Integration ships with over 50 technology adapters covering SAP protocols, standard web service standards, file transfer, messaging, and B2B EDI. For third-party SaaS platforms, Open Connectors extends the ecosystem to 170+ pre-built connectors with a normalised REST API.
- IDoc — SAP Intermediate Document (inbound & outbound)
- RFC / BAPI — Remote Function Call to ABAP systems
- OData V2 / V4 — SAP OData services (S/4HANA, BTP)
- SOAP — SAP web services (ABAP, PI/PO interfaces)
- SuccessFactors — SFAPI & OData for HCM payloads
- Ariba — cXML & Ariba Network connectivity
- Concur — SAP Concur REST APIs
- S/4HANA Cloud — dedicated inbound/outbound adapter
- HTTP — REST/HTTP sender & receiver
- OData — Generic OData V2/V4 (non-SAP)
- SFTP — Secure file transfer (poll & push)
- Mail (SMTP / IMAP) — Email-based integration
- AMQP 1.0 — Message queue connectivity
- MQTT — IoT / lightweight pub/sub messaging
- Kafka — Apache Kafka topic producer/consumer
- JDBC — Direct database connectivity
- JMS — Internal message queuing (guaranteed delivery)
- AS2 — Applicability Statement 2 (EDI over HTTPS)
- AS4 — ebMS 3.0 / AS4 profile (e-SENS, Peppol)
- EDIFACT — UN/EDIFACT message parsing & generation
- ANSI X12 — North American EDI standard
- EANCOM — EAN variant of EDIFACT (retail/grocery)
- Odette — Automotive EDI (VDA, OFTP2)
- Open Connectors — 170+ SaaS (Salesforce, ServiceNow, Workday, NetSuite, Zendesk, Hubspot…)
Edge Integration Cell — On-Premise Runtime
The Edge Integration Cell (EIC) runs the same iFlow runtime as cloud Integration Suite, deployed on Kubernetes inside your private network — for data sovereignty, compliance, or latency-sensitive on-premise-to-on-premise flows where messages can’t leave the network boundary. A single iFlow deploys to either runtime without duplication, and both are managed centrally from the BTP cockpit.
SAP PI/PO Migration
SAP PI/PO on NetWeaver reaches end of standard maintenance in 2027 and extended maintenance in 2030. SAP Integration Suite is the designated migration target. We run SAP’s Migration Assessment and Migration Tooling against your PI/PO landscape to score interfaces, estimate effort, and scope the manual rework that BPM workflows and complex mappings typically need — before committing to a timeline.
API Management
API Management in Integration Suite provides a full API gateway and developer portal — governing how backend services and integration endpoints are exposed to internal and external consumers.
Security Architecture
Cloud Integration handles credentials, certificates, and message-level security through a built-in Keystore — keeping sensitive material out of iFlow artefacts and enabling rotation without redeployment. This covers TLS/mTLS transport security, PGP and XML message-level encryption for AS2/EDI, OAuth 2.0 via BTP’s XSUAA service, and principal propagation to on-premise ABAP systems — standard SAP integration-security mechanisms that we configure for your landscape rather than re-explain here.
What We Deliver
Integration Architecture & Foundation
Integration Suite tenant provisioning, capability activation, Cloud Connector high-availability installation, Destination Service configuration, and security baseline — Keystore setup, OAuth clients, credential stores. Integration domain model: which flows run in Cloud Integration vs Edge Integration Cell, API vs event vs process integration.
iFlow Development & Delivery
End-to-end iFlow design and development using SAP’s Integration Content Catalog pre-built packages where available, custom development where not. Adapter configuration (IDoc, SOAP, OData, SFTP, AS2, HTTP), XSLT and graphical message mapping, Groovy scripting, exception subprocesses, and JMS-based async queuing with dead-letter handling.
API Management & Developer Portal
API proxy design and policy configuration (rate limiting, OAuth 2.0, mTLS, quota enforcement). API product bundling and Developer Portal setup for self-service consumer onboarding. API versioning strategy, lifecycle governance, and analytics dashboard configuration. OpenAPI / Swagger specification import and maintenance.
Event-Driven Architecture (Advanced Event Mesh)
Advanced Event Mesh broker provisioning, topic hierarchy design, S/4HANA Business Event Handling configuration, and AMQP/MQTT consumer iFlow development. Event schema registry setup, publisher and subscriber configuration, and dead-letter topic handling for undeliverable messages.
PI/PO Migration
Migration Assessment execution and readiness scoring across your existing PI/PO interface landscape. Migration Tooling-assisted artefact conversion for standard ICO-based interfaces. Manual rework scoping for BPM, multi-mapping, and ABAP proxy scenarios. Parallel-run test strategy and production cutover planning.
Monitoring, Alerting & DevOps
Message processing log configuration, trace-mode activation for debugging, alert rules for failed messages and adapter disconnections. Cloud Transport Management integration for iFlow package promotion (DEV→TEST→PROD). SAP Cloud ALM integration for centralised integration health monitoring and operational dashboards.
How Customers Benefit
How We Work
Landscape Analysis & Scope
We inventory your existing integration landscape — PI/PO ICOs, point-to-point connections, middleware components, error rates, and ownership gaps. For PI/PO migrations, we run Migration Assessment to produce an effort estimate, readiness score, and prioritised migration backlog.
Architecture & Pattern Design
Integration domain model (Cloud vs EIC), API strategy (which services get proxied), event topology (Advanced Event Mesh topic hierarchy), B2B partner onboarding model, security architecture (mTLS, OAuth, PGP), and Cloud Connector HA placement — documented and approved before any iFlow is built.
Foundation Setup
Integration Suite tenant and capability activation, Cloud Connector HA installation and system mapping, Destination Service configuration, Keystore and credential store population, Alert Notification Service rules, and CI/CD pipeline + Cloud Transport Management node setup for integration package promotion.
Iterative iFlow Delivery
Critical business interfaces are prioritised and delivered sprint by sprint — each iFlow starting with a pre-built catalog package where available, built custom otherwise. Every iFlow includes exception subprocess, dead-letter handling, retry logic, and message processing log configuration before it goes to TEST.
Cutover & Go-Live
Parallel-run period with both old and new integration handling flows, cutover checklist validation, production promotion via Cloud Transport Management, and hypercare monitoring in the first weeks after go-live. PI/PO decommission checklist delivered after stable production operation is confirmed.
Knowledge Transfer & Governance
Integration developer workshops (iFlow patterns, adapter configuration, error handling, Groovy scripting), operational runbooks for monitoring and error reprocessing, naming conventions and package governance standards, and a validated onboarding checklist for future interface development.
Ready to connect your systems?
Let’s build your integration layer.
Tell us about your current middleware landscape, PI/PO footprint, and integration requirements — we’ll design a secure, scalable Integration Suite architecture that consolidates your entire integration estate.
Get in touch →