IT CanvassTalk to an advisor
SAP integration · LessonBy , SAP Solution Architect · Published · SAP S/4HANA 2023 · all levels

Integration overview

SAP integration connects SAP systems to each other and to non-SAP applications, through middleware and protocols, so data and processes flow across the enterprise. This hub maps SAP’s integration technologies old and new.

Quick answer

Match the technology to the need: synchronous APIs (OData/SOAP) for real-time, IDoc/ALE for robust async document exchange, events (Event Mesh) for decoupled notifications, and Integration Suite/PI-PO as the middleware orchestrating and transforming between systems.

Key takeaways
  • Integration is shifting from on-premise middleware (PI/PO) to the cloud SAP Integration Suite, aligning with cloud ERP and hybrid…
  • SAP Integration Suite (cloud): the strategic iPaaS (includes Cloud Integration/CPI, API Management, more).
  • SAP PI/PO (on-premise): the classic middleware, being succeeded by Integration Suite.
  • Watch out: Wrong integration style (sync vs async) for the need.

The integration landscape

  • SAP Integration Suite (cloud): the strategic iPaaS (includes Cloud Integration/CPI, API Management, more).
  • SAP PI/PO (on-premise): the classic middleware, being succeeded by Integration Suite.
  • IDoc/ALE & RFC/BAPI: classic SAP-to-SAP mechanisms.
  • OData/REST & SOAP: service-based integration.
  • Event-driven (Event Mesh): asynchronous events.

On-premise to cloud shift

Integration is shifting from on-premise middleware (PI/PO) to the cloud SAP Integration Suite, aligning with cloud ERP and hybrid landscapes. New integrations increasingly use Cloud Integration (CPI) and API Management, while classic IDoc/RFC remains important for existing SAP-to-SAP flows.

Choosing an approach

Match the technology to the need: synchronous APIs (OData/SOAP) for real-time, IDoc/ALE for robust async document exchange, events (Event Mesh) for decoupled notifications, and Integration Suite/PI-PO as the middleware orchestrating and transforming between systems.

Common pitfalls

  • Wrong integration style (sync vs async) for the need.
  • Point-to-point sprawl instead of using middleware.
  • Ignoring the cloud direction (Integration Suite).

Practice challenge

+0 XPStreak ×0
Question 1 of 3
Which statement is true of Integration overview?

Frequently asked questions

What does the term Integration overview refer to in SAP?
SAP integration connects SAP systems to each other and to non-SAP applications, through middleware and protocols, so data and processes flow across the enterprise. This hub maps SAP’s integration technologies old and new.
What is worth remembering about Integration overview in practice?
Match the technology to the need: synchronous APIs (OData/SOAP) for real-time, IDoc/ALE for robust async document exchange, events (Event Mesh) for decoupled notifications, and Integration Suite/PI-PO as the middleware orchestrating and transforming between systems.
What is another point to note about Integration overview?
Integration is shifting from on-premise middleware (PI/PO) to the cloud SAP Integration Suite, aligning with cloud ERP and hybrid landscapes.
What tends to go wrong with Integration overview?
Wrong integration style (sync vs async) for the need. Point-to-point sprawl instead of using middleware. Ignoring the cloud direction (Integration Suite).
Already working on SAP and stuck on a live ticket?Get an expert SAP developer on screen-share to finish your daily tasks with you. Deliver on time, protect your reputation and your job. Monthly support only, no task-wise plans.Task assigned · no idea where to startStill stuck · your job on the lineExpert joins your screenDelivered on timeExplore On Job Support