Sundown for SAP PI/PO: Setting the course for integration

For many years, SAP Process Integration (PI) and SAP Process Orchestration (PO) were the central tools when it came to connecting SAP systems with third-party systems and mapping complex business processes across system boundaries. The tools have done their job reliably and are deeply rooted in many companies. 

However, the requirements for modern IT landscapes have changed significantly, with a clear trend towards the cloud, hybrid operating models and API-controlled communication. Business processes need to become more flexible, new digital business models are emerging and IT must be able to react more quickly to changes. Against this backdrop, it is no surprise that SAP has discontinued the further development of PI/PO and limited and discontinued support until 2027 or, optionally, until 2030 at the latest. Companies are therefore faced with the task of fundamentally rethinking their integration strategy - not only out of technical necessity, but also as an opportunity for structural modernization.

Integration Suite: Cloud-native 

The SAP Integration Suite is a successor that is not simply a replacement for PI/PO, but enables a completely new approach to integration. The Integration Suite is completely cloud-native and part of the SAP Business Technology Platform (BTP). It connects different systems, data sources and applications - regardless of whether they are operated on-premises, in the cloud or hybrid. It is not just about the technical connection, but also about the logical and organizational control of integration processes. The platform follows principles such as API first, event-driven integration and DevOps enablement.

This means that integration is no longer just planned centrally in IT, but is moving closer to the specialist departments. It is becoming more agile, faster and - if implemented correctly - a real enabler for digital business models.

Everything is different

Nevertheless, many companies find the changeover difficult. The operation of PI/PO is familiar. The processes are well established, the interfaces documented - at least in theory. The new world, however, brings with it new requirements. The technologies are different, the security model is different, the interface is new. It is not enough to simply copy old interfaces; a real migration requires a strategic approach. It is worth taking a closer look at the building blocks of the Integration Suite: Cloud Integration enables the mapping of A2A and B2B processes with ready-made content and graphical modeling. API Management controls the use and security of interfaces. Event Mesh supports event-driven architectures based on messaging and event brokers - crucial for real-time processes and loosely coupled systems. Open Connectors enable the simple connection of over 160 SaaS applications such as Salesforce, Microsoft Dynamics or Workday. And the Integration Advisor uses machine learning to generate mapping suggestions and speed up integration creation, which is particularly helpful in classic EDI and B2B scenarios.

 Think hybrid - with the EIC

A widespread misconception is that the Integration Suite is only suitable for cloud scenarios. This is not true. It was developed specifically for hybrid architectures. This is where the Edge Integration Cell comes into play. It allows integration flows to be executed locally, even though they are managed centrally from the cloud. This is crucial in many situations - for example, for particularly sensitive data that cannot be transferred to the cloud for regulatory reasons or at locations with a poor network infrastructure. The Edge Integration Cell also offers a practical solution for connecting older systems that are not internet-capable. Companies retain control over their data and processes, but at the same time benefit from the advantages of central cloud control. A genuine hybrid approach that is not only technically convincing, but also makes sense from an organizational perspective.

More than just a technology change

When migrating from PI/PO to the Integration Suite, a fundamental mistake is made time and again: many organizations try to transfer their existing interfaces one-to-one. This sounds logical at first - but is rarely sustainable. The new tools bring new paradigms with them. Those who simply adopt old flows risk giving away the advantages of the new platform. That's why every migration should start with a thorough analysis: Which interfaces actually exist? Which of them are still in use? Which ones could be consolidated or replaced by standard functions? And are there perhaps processes that are currently integrated individually at great expense but can now be mapped much more easily using connectors or APIs? These questions are crucial when it comes to understanding the migration as a strategic modernization - not just a technical conversion.

The changeover also poses new challenges for the organization. The SAP Integration Suite is not just a tool for integration experts. It touches many areas: Architecture, operations, development and governance. Roles need to be redefined, responsibilities clarified and the necessary know-how built up. Without targeted training and internal coaching, it will be difficult to fully exploit the new possibilities. It is also important to note that the Integration Suite comes with different tools, concepts and interfaces than PI/PO. 

It is not enough just to familiarize yourself with the technology. The mindset must also change - away from the purely technical integrator and towards the strategic designer of data flows.

What works - and what doesn't

Clear success factors can be derived from project experience. A comprehensive integration assessment is the first step. This involves documenting, evaluating and categorizing all interfaces - according to criticality, complexity and future viability. This is the only way to develop a migration plan that is based on sound data and does not aim for the blue sky. It is then helpful to proceed iteratively - a big bang is rarely practicable. Instead, migration waves that are implemented step by step, starting with pilot projects that are clearly defined and easy to manage, are a good option. 

These early phases are not only important from a technical perspective, but also for internal acceptance. If the first use cases work well, trust in the new platform is established. At the same time, valuable experience is gained that can be incorporated into the subsequent steps.

Another success factor is the targeted development of expertise within the team. Many companies underestimate how much new knowledge is required. It's not just about technical training, the methodical approach to integration is also changing. 

Dealing with APIs, understanding event handling or the use of ready-made integration content - all of this requires new thinking. Those who invest in qualifications at an early stage will benefit in the long term. This is because internal expertise makes you independent, agile and reduces your dependency on external partners.

Starting instead of waiting

Against this backdrop, it is advisable not to wait until 2027 or 2030. If you start too late, you run the risk of having to make poor decisions under time pressure - with consequences for the stability and security of processes. If they haven't already done so, companies should start planning now, set up a dedicated team and implement initial pilot projects. The experience gained from these projects will help to shape the further migration process efficiently. The migration should not be viewed in isolation. As part of SAP BTP, the Integration Suite only really comes into its own in conjunction with other components such as API Management, Event Mesh or Business Process Management. Those who take this into account not only create a modern integration architecture, but also lay the foundation for holistic digital transformation and innovation.

The replacement of PI/PO is therefore not only necessary, but also sensible. It opens up the opportunity to question existing structures, rethink processes and make your own IT landscape fit for the future. 

The SAP Integration Suite provides the technical tools for this. However, the decisive factor is how companies deal with it. Those who take action early on, approach migration strategically and see integration as an opportunity rather than a chore can benefit in the long term - through greater flexibility, less complexity and the ability to react more quickly to new requirements.

To the partner entry: