IQN Consulting
← All work
Plant-based food · Danone

Modernising SAP integration at Alpro

A cloud-first integration architecture for a business whose SAP landscape keeps growing through acquisition — retiring legacy interfaces and bringing every implementation partner onto one standard.

Client
Alpro
Role
SAP Integration Architect
Period
2025 – present
Stack
Integration Suite · BTP · Event Mesh · ABAP Proxy
Ongoing
architect engagement since 2025
2 days / week
embedded with the business
Cloud-first
legacy interfaces moved to Integration Suite
How the pieces connect
Business & functional owners
SAP Integration Suite
S/4HANA · legacy apps
Event Mesh · downstream

Context

Alpro’s integration landscape is shaped by growth. Each acquisition adds applications, partners and interfaces, while older systems stay directly in the path of every change.

The result is a landscape that becomes more expensive to extend each year — and harder to keep consistent when several implementation partners work on it at once.

The challenge

Define a target integration architecture that absorbs new applications quickly, retires legacy systems safely, and holds external implementation partners to one set of standards — without pausing day-to-day delivery.

What we did

  1. 01

    Integration strategy with the business

    Workshops with business stakeholders and functional owners to agree the short- and long-term direction of the landscape.

  2. 02

    Migration to Integration Suite

    Legacy interfaces moved onto SAP CPI, with PI iFlows designed, developed and deployed.

  3. 03

    Interface engineering

    ABAP proxies, IDoc and CDC interfaces, complex Java mappings, adapter modules and sequencing flows.

  4. 04

    Event-driven propagation

    Event Mesh queues push events into Integration Suite instead of relying on point-to-point polling.

  5. 05

    Backend services

    OData services developed in the SAP backend so cloud applications can consume them directly.

  6. 06

    Partner governance

    Directing the implementation partner against Alpro’s integration standards, rather than letting each team invent its own.

The outcome

  • — A cloud-first integration landscape with a defined path off legacy systems.
  • — One integration standard, applied by internal teams and external partners alike.
  • — An ongoing architect role — the engagement continues at two days per week.

Facing a similar integration problem?

Tell us what the landscape looks like today and we will tell you, honestly, what it would take.

Schedule a consultation See more work