SAP Integration Suite — Interface Consulting for SAP Landscapes
SAP Integration Suite is the integration platform of the SAP Business Technology Platform and the successor to SAP PI and SAP PO. We design, build and support interfaces on it — from a single iFlow to the integration blueprint for a full S/4HANA programme.
What we build on the platform
Cloud Integration for the interfaces themselves, API Management where systems are exposed to partners, and Event Mesh where processes react to events rather than polling for them. Which of the three is the right answer is an architecture decision, not a licence decision.
Most of the work is not the iFlow. It is agreeing on the contract: which system owns which field, what happens to a message that cannot be delivered, and who is told about it.
Error handling belongs in the design
An interface that only works on the happy path is not finished. Retry behaviour, dead-letter handling and monitoring decide whether an operations team can run the landscape without calling the person who built it. We design these paths before go-live, not after the first incident.
Working alongside SAP PI and PO
Very few landscapes switch over in one step. In practice both platforms run in parallel for a while, which raises the question of which interface moves when and how the two are kept consistent in the meantime. We plan that sequence so the parallel period stays short and predictable.
Frequently Asked Questions
Is SAP Integration Suite the same as SAP CPI?
In everyday use, yes. SAP Cloud Platform Integration, still widely called CPI, is the Cloud Integration capability inside SAP Integration Suite. Job descriptions and project briefs use both names interchangeably, so a requirement asking for CPI is asking for Integration Suite experience.
Can Integration Suite connect non-SAP systems?
Yes, and that is a large part of the work in practice. The platform speaks the common protocols and formats, so third-party applications, partner endpoints and legacy systems are connected the same way SAP systems are. The difficulty is rarely the protocol, it is the data contract behind it.
How long does a typical interface take?
A straightforward interface along an established pattern is a matter of days. What extends a timeline is not the build but the clarification: which system is authoritative, how errors are handled, and who signs off on the mapping. We keep those questions at the start rather than at the end.
Do you also take over operations?
We support running interfaces and hand over to your own operations team where you have one. The aim is an interface your team can run without us, which is why monitoring and documentation are part of the build rather than an afterthought.