Skip to content
IT Canvass
Menu
ServiceNow
SailPoint
SAP
TutorialsContact
SAP integration · Lesson

Integration overview

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).

Want to learn this properly?

Our live, instructor-led SAP Training covers this hands-on, with real projects and a certification path.

See the courseAsk a question

Check your understanding

  1. Which statement is true of Integration overview?

    • A. A good SAP learning path takes you from business and system fundamentals, through a chosen specialisation, to…
    • B. SAP supports visual themes that change the look of the interface, in both SAP GUI and Fiori.
    • C. New integrations increasingly use Cloud Integration (CPI) and API Management, while classic IDoc/RFC remains…
    Show answer

    C. New integrations increasingly use Cloud Integration (CPI) and API Management, while classic IDoc/RFC remains…

    Covered in the “On-premise to cloud shift” section of this lesson.

  2. Which of these also applies to Integration overview?

    • A. Wrong planning strategy (MTS vs MTO).
    • B. SAP Integration Suite (cloud): the strategic iPaaS (includes Cloud Integration/CPI, API Management, more).
    • C. QAS drifting from PRD, tests then lie.
    Show answer

    B. SAP Integration Suite (cloud): the strategic iPaaS (includes Cloud Integration/CPI, API Management, more).

    Covered in the “The integration landscape” section of this lesson.

  3. Which part of the Learn SAP curriculum covers Integration overview?

    • A. SAP modules hub
    • B. SAP security
    • C. SAP integration
    Show answer

    C. SAP integration

    This lesson sits in the SAP integration section of the Learn SAP course.

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).
CallWhatsAppEnquire