SAP integration careers: connecting the landscape

Written by an SAP Finance & Treasury practitioner working with SAP since 2008 · how the guides are written · Updated 9 October 2026

An SAP integration consultant is the specialist who designs, builds and runs the interfaces between SAP and everything around it. Today most of that work happens in SAP Integration Suite, whose Cloud Integration capability — formerly SAP Cloud Platform Integration — practitioners still call SAP CPI.

What does an SAP integration consultant do?

They make every conversation between systems reliable — SAP to SAP, SAP to banks, carriers, webshops, tax authorities and suppliers — across the whole lifecycle, not only the build. Adverts may call it SAP middleware consultant or CPI developer; the remit:

• Interface design. Agreeing with both sides what moves, in which direction, how often, and what happens when it doesn't arrive — the specification that outlives the project.
• Build and mapping. Turning that agreement into configured flows: field mappings, conversions, routing rules, connectivity, certificates.
• Testing with counterparties. Interfaces are the part of a programme you cannot test alone; an integration test wave moves at the speed of whoever chases the bank, the carrier or the partner's IT team.
• Cutover. Every interface has to be repointed, re-registered and re-verified during go-live — habitually the longest list on the cutover plan.
• Run and repair. Monitoring queues, reprocessing failed messages, and establishing which of the two systems is actually wrong.

What is SAP CPI?

SAP CPI is the Cloud Integration capability of SAP Integration Suite: a cloud service on SAP BTP that runs integration flows — iFlows — which receive a message through an adapter, transform and route it, and deliver it through another adapter. The name changed twice (HANA Cloud Integration, then SAP Cloud Platform Integration, then Cloud Integration), and job adverts use all three. The suite around it adds API Management for publishing and protecting APIs, Integration Advisor and Trading Partner Management for B2B and EDI message standards, Open Connectors for third-party SaaS applications, and a library of prepackaged content from SAP for common scenarios — the integration between S/4HANA and SuccessFactors is one of the busiest. A consultant's first question on any new requirement is whether delivered content already covers it, because a configured standard package is cheaper to run than a custom flow.

CPI is not the only way in. S/4HANA publishes OData and SOAP APIs, catalogued on the SAP Business Accelerator Hub, and raises business events — a sales order created, a business partner changed — that an event broker distributes to whoever subscribes. Good designs pick the pattern before the tool: a synchronous API call when the caller needs an answer now, an event when several systems need to know something happened, a batch file when volume matters more than speed, and an IDoc when the partner is another SAP system that already speaks it.

How do you move from SAP PI/PO to Integration Suite?

Interface by interface, after an assessment, and usually over more than one release. SAP Process Orchestration 7.5 is the last release of the on-premise middleware; as of October 2026 its mainstream maintenance runs to the end of 2027, and paid extended maintenance, priced like NetWeaver 7.5's, can stretch that to the close of 2030, the same horizon as ECC's extended maintenance. Most landscapes still run it beside Integration Suite. A typical migration runs in four steps:

1. Inventory and assess. The Migration Assessment capability in Integration Suite reads the PI/PO repository and sorts the scenarios by how much work each will need; the result is the scope, not a plan.
2. Decide each interface's fate. Retire it, replace it with prepackaged content, migrate it with the tooling, or rebuild it — often as an API or an event rather than a copy of the old pattern.
3. Migrate in waves. The migration tooling in Cloud Integration generates iFlows from PI/PO integrated configurations for supported patterns; mappings and adapters it cannot carry over are rebuilt by hand.
4. Choose the runtime. Flows that must stay inside the company network, for latency, data residency or security reasons, can run on Edge Integration Cell — the hybrid runtime deployed on the customer's own Kubernetes, designed and monitored from the cloud tenant.

Connectivity is the part that surprises teams: the Cloud Connector, certificates, technical users and firewall rules shared with Basis and authorizations colleagues take as long as the flows.

Do you need to code to work with SAP CPI?

Some, not much: most of an iFlow is modelled graphically, mappings are built in a graphical editor, and code appears where the graphical tools stop — Groovy or JavaScript scripts, XSLT mappings, and on the SAP side ABAP proxies or a function module someone has to read. People arrive from three directions: from ABAP development, wanting more contact with the business; from a functional SAP area, after owning one interface long enough to be handed the rest; or from middleware work outside SAP. The scarce skill is not the tool but holding both halves of an interface at once — the business document travelling through it, an order or an invoice or a payment, and the technical contract that carries it.

The other skill interviewers probe is designing for failure. Interfaces break when nobody is watching — overnight batches, period-end peaks, a certificate expiring on a weekend — so good flows process idempotently, separate "retry" from "wake someone", and tell a support colleague which document is stuck without making them decode a payload.

Which monitors do you use for SAP interfaces?

The one that belongs to the interface type, which is why an integration consultant has to know where each kind of message is logged. A support ticket that says "the interface failed" is answered by working through this list from the sending side to the receiving one.

Many S/4HANA landscapes add SAP Application Interface Framework on top, so business users can correct and restart their own failed messages instead of raising a ticket.

What do SAP CPI interviews ask?

Mostly scenarios from a live landscape, judged by the mechanism a candidate names rather than by definitions. Six come up again and again:

• "Walk me through an iFlow you built." A strong answer names the sender and receiver adapters, the mapping, and why the flow was split or kept whole.
• "A receiver is down for an hour. What happens to the messages?" An exception subprocess, a JMS queue holding the message for retry, and the point where retry stops and an alert goes out.
• "IDoc, SOAP or OData for this partner?" The choice argued from the partner system, synchronous versus asynchronous, and volume.
• "Where do credentials and certificates live?" Security material for user credentials and OAuth, the tenant keystore for keys and certificates, and who renews them before they expire.
• "How would you scope a PI/PO migration?" The Migration Assessment output first, then a fate per interface rather than a one-to-one copy.
• "Support reports a missing invoice. Where do you start?" The message processing log in the monitor, searched by a business identifier, then the sending system's own log.

Where does an SAP integration career lead?

Integration is the most techno-functional of the technical specialisms, so it reads well on both sides of the functional/technical divide and is the shortest path to solution architecture. The SAP Certified - Integration Developer exam is the credential the market recognises for Cloud Integration. Records build fastest where the landscape is complicated: greenfield builds create the interface catalogue, rollouts multiply it, and PI/PO migrations ask which interfaces survive.