SAP Process Integration / Process Orchestration (PI/PO)

SAP's on-premise middleware for mediated integration between SAP and non-SAP systems using adapters and mapping.

PI/PO questions come up in interviews for organizations that haven't yet fully moved to cloud integration, and interviewers use it to check whether a candidate understands mediated, broker-based integration architecture as a distinct pattern from either direct point-to-point RFC/API calls or the newer cloud-native CPI approach.

PI/PO is like a universal translator and mail-sorting hub at the center of a multinational conference - instead of every attendee needing to personally learn every other attendee's language and hand-deliver messages (point-to-point integration), everyone just hands their message to the hub, which translates and routes it to the correct recipient in their own language.

Key Concepts

PI/PO acts as a central integration broker sitting between systems: an inbound adapter (Sender Adapter - could be IDoc, SOAP, HTTP, JDBC, file, and many others) receives a message from the source system, the Integration Engine routes it based on configured interface determination and receiver determination rules (which can fan a single message out to multiple receivers), a mapping step (graphical message mapping, or XSLT/Java mapping for more complex transformations) converts the source message structure into the format the target expects, and an outbound adapter (Receiver Adapter) delivers it to the destination system. This mediated, hub-and-spoke architecture is precisely the point - rather than every system needing to know how to talk directly to every other system it integrates with (an N-squared point-to-point integration nightmare), each system only needs to know how to talk to PI/PO, which handles the translation and routing centrally.

Sender AdapterReceiver Adapter

A key architectural distinction is Integration Directory (the runtime configuration - which sender/receiver combination uses which adapter, connection details, communication channels) versus Enterprise Services Repository / ESR (the design-time repository of message types, interfaces, and mappings, reusable across multiple runtime configurations) - candidates should be able to explain why this separation matters (the same designed interface/mapping can be reused across dev/QA/prod runtime configurations without redesigning it each time). Process Orchestration additionally adds BPM (Business Process Management, for human-task-involving multi-step business processes) and BRM (Business Rules Management) capabilities layered on top of the core integration engine, extending PI beyond pure system-to-system message routing into human-workflow-involving orchestration.

A senior-level answer positions PI/PO honestly in SAP's current roadmap: it remains supported and heavily used in existing on-premise landscapes, but SAP's strategic direction for new integration development is Cloud Integration (CPI) on BTP, and a mature answer can explain both the conceptual similarities (adapters, mapping, routing are common to both) and the practical migration considerations organizations face moving from PI/PO to CPI as part of a broader S/4HANA and cloud transformation.