SAP PI PO CPI and Integration Wizard-AI-powered SAP integration automation.

Example

Design a resilient procure-to-pay integration: Ariba → CPI (HTTPS OAuth2) → S/4HANA (OData for master data; IDoc for POs); CPI handles content-based routing (domestic vs international), exception subprocess for 4xx/5xx, and a JMS retry queue; confirmations flow back async via webhook → CPI → SAP. For on-prem orchestrations, PO BPMN coordinates multi-step approvals with timers and error branches.

Scenario

A global retailer needs synchronous product availability checks and asynchronous order fulfillment. The Wizard recommends: (1) synchronous OData call from commerce site to S/4 through CPI with short timeouts and circuit-breaker pattern; (2) async order submission via IDoc with ExactlyOnceInOrder; (3) a splitter iFlow to fan out line items to 3PLs; (4) an aggregator to collect shipment statuses; (5) monitoring via CPI’s Alerting plus SAP Cloud ALM. Deliverables include interface contracts, message models, retry/backoff policies, and BPMN/iFlow sketches.

Example

Adapters: IDoc/ALE, RFC/Proxy for SAP; SOAP 1.1/1.2; REST/OData; SFTP/FTP(S); AS2/OFTP2 for EDI; JMS/AMQP; JDBC; Mail; Cloud Connectors. Security: TLS mTLS, OAuth2 (Client Credentials, JWT Bearer), Basic (only when acceptable), PGP signing/encryption, certificate rollover planning. QoS: BestEffort, ExactlyOnce, ExactlyOnceInOrder; large payload handling via streaming and chunking.

Scenario

A manufacturer exchanges EDIFACT INVOIC via AS2 with a VAN. The Wizard outlines AS2 signing/encryption (SHA-256/AES-256), MDNs (sync vs async), trading partner profiles, and certificate rotation runbooks. On inbound, CPI converts EDIFACT → XML, validates against MIGs, enriches via a JDBC lookup, then maps to S/4 IDoc INVOIC02. A dead-letter JMS queue captures failed messages with correlation IDs for reprocessing.

Example

Typical transformations: IDoc↔XML↔JSON, EDI↔XML, CSV↔XML, OData payload shaping. Reusable libraries for date/number normalization, code mappings, and canonical models. Unit tests via CPI’s Simulation/Trace; PO’s Test tab; contract tests with Postman/Newman. Sample Groovy (CPI mapping helper, with correct imports): "import com.sap.gateway.ip.core.customdev.util.Message;\nimport groovy.xml.*\n\nMessage processData(Message message) {\n def body = message.getBody(String)\n def xml = new XmlParser().parseText(body)\n xml.'**'.findAll{ it.name() == 'Amount' }.each{ it.value = it.text().trim().replace(',', '.') }\n def sw = new StringWriter(); new XmlNodePrinter(new PrintWriter(sw)).print(xml)\n message.setBody(sw.toString()); return message\n}"

Scenario

A telco must normalize monetary values and add tax details before posting invoices to S/4. The Wizard proposes a canonical invoice schema, provides mapping templates (Graphical + Groovy helpers), and a test dataset with edge cases (empty decimals, different locales, huge payloads). It also suggests payload streaming and selective logging to stay under audit policies while keeping traceability.