SAP CPI: Cloud Platform Integration iFlows That Survive Production

SAP CPI (still searched as HCI) is the iFlow engine inside Integration Suite. Adapters, content modifier, Groovy, XSLT, JMS, exactly-once, certificate expiry. This is how S/4 talks to Vertex, banks, 3PLs, and the plant. An iFlow without idempotency is a duplicate payable waiting to happen. A certificate that expires on a Sunday is a filing miss. SR Soft staffs CPI developers who have on-called an iFlow at 2 a.m.

What programs get wrong

• No idempotency key — retries create money
• Secrets in Groovy, certificates in someone’s laptop
• Monitoring only a developer can read
• CPI used where Event Mesh should have been
• Mapping that only the original contractor understands

On S/4 we staff CPI next to FICO, Vertex, and PRA — those modules are only as true as their interfaces. Future: Advanced Event Mesh plus CPI. Same people, larger surface.

Exactly-once is a design, not a checkbox

JMS, idempotency keys, and a replay that does not create money — that is CPI in production. Certificates expire. OAuth tokens die. Groovy that holds a secret is a finding. Monitoring only a developer can read means tax will not see a failed Vertex call until the notice. We enforce a standard: idempotent, rotatable, visible, named on-call. Event Mesh when the pattern is an event. CPI when it is a document. Both when both.

PRA tickets, Vertex calls, bank statements, plant files — we staff CPI next to those modules because the module is only as true as the interface. A cert calendar is part of the runbook.