Automation for SAP.Released APIs only.
Corin resolves your SAP work through released public APIs you can verify on the SAP Business Accelerator Hub.
On S/4HANA the rehearsal is a released API — Sales Order – Simulate (A2X), service API_SALES_ORDER_SIMULATION_SRV. On ECC it is the BAPI your basis team already runs: BAPI_SALESORDER_SIMULATE.
Illustrative rail — sample data (Nordwind Aero, an anonymized sample customer), not a customer record.
Agentic AI for SAP: the dry run comes first.
Priced and availability-checked inside SAP, with nothing posted — then a person approves, and Corin commits through the released write path.
Three commitments before any write.
SAP's API policy asks how an outside agent behaves in your system. Corin's answer fits in three lines.
- Released, upgrade-stable APIs only
- Corin connects through the APIs SAP publishes as released and upgrade-stable — no screen-scraping, no private endpoints, clean core intact.
- Every write policy-authorized
- Nothing posts to your ERP without a rule that allowed it and a record that proves it. Autonomy is set per workflow, per amount, per counterparty — and you set the pace.
- The ledger maps each commit to its approval
- The ledger — a record of every decision: what changed, who approved it, when — binds every SAP document number to the rule and the person that authorized it.
Corin integrates with SAP® S/4HANA® Cloud via released public APIs.
SAP® and S/4HANA® are registered trademarks of SAP SE. Corin is not an SAP partner, and nothing on this page implies partnership or certification — the integration claims describe released public APIs.
The released SAP surface, enumerated.
Corin's SAP claims come from the same discipline as the Infor catalog: we counted the source of truth.
Methodology: SAP Business Accelerator Hub content catalog (api.sap.com catalog service), product 'SAP S/4HANA Cloud Public Edition', snapshot 29 Aug 2026. Deprecated items excluded from released counts. On-prem/private editions are a different, larger surface — never conflated.
The whole released surface, mapped. These four carry the money.
Corin reads SAP's full released catalog — 874 live services, 147 event definitions, 8,678 CDS views, counted from api.sap.com, not estimated — and pins every workflow to the exact services it calls. The RFQ-to-order loop runs on these four.
- Sales Order (A2X)
- The sales write path: create, read, and change sales orders through the released OData service (API_SALES_ORDER_SRV) and its communication arrangement. Every quote and order decision ends here.
- Sales Order – Simulate (A2X) anchor
- Evaluates a sales order — pricing, availability, credit-relevant totals — without posting anything (API_SALES_ORDER_SIMULATION_SRV). Corin's dry run builds on exactly this released capability: rehearse the decision inside the ERP, commit only after a person confirms.
- Journal Entry – Post (SOAP)
- The finance write path: journal entries posted through the released synchronous/asynchronous SOAP services. In the Public Edition this interface is SOAP, not OData — we name it precisely because the distinction matters to your integration team.
- Supplier Invoice
- The AP surface (API_SUPPLIERINVOICE_PROCESS_SRV): read, validate, and post supplier invoices — where the three-way match writes its answer.
Same loop, same gate.
S/4HANA — released OData and SOAP
Sales Order (A2X) writes the order, Sales Order – Simulate (A2X) rehearses it, Supplier Invoice carries the three-way match. Every call is verifiable on the SAP Business Accelerator Hub.
ECC — BAPI, RFC, IDoc
The agent era didn't skip your ECC. Corin runs the same loop over BAPI, RFC, and IDoc ORDERS05 — the same dry run, the same gate — while ECC mainstream maintenance runs out in 2027.
Event Mesh keeps the graph current.
S/4HANA Cloud publishes business events through SAP Event Mesh in the CloudEvents format. Corin subscribes instead of polling — a blocked order becomes work the moment it blocks.
Webhooks into the work graph
Events arrive over AMQP, MQTT, or webhook subscriptions and land on the work graph — one live view of every job — never a nightly sync. A stuck order is work exactly like a new email.
Sales order events
Order created, changed, released — the events the sales loop re-checks its dry runs against.
Delivery and billing events
Shipments and invoices stream in as they post — the ground truth behind ATP answers and cash forecasts.
SAP's agent surface, used as designed.
Joule lives inside SAP screens. Corin lives where work arrives — and commits to SAP through the same governed surface SAP ships for agents.
- MCP servers via the SAP gateway
- Released SAP APIs, iFlows, and RFCs exposed as governed MCP servers through the SAP MCP Gateway in Integration Suite. Corin consumes S/4HANA capabilities through that gateway — never by screen-scraping.
- API Management as the boundary
- OAuth scopes, rate limits, and quotas on the released APIs — the layer that decides what an agent may call. Corin's scoped permissions map onto it one to one.
- Event Mesh as the trigger
- Business events streamed to agents the moment SAP state changes. Corin's work graph subscribes instead of polling — context stays continuous.
- Joule interop via A2A
- SAP co-stewards the open Agent2Agent protocol. Outbound 'Bring Your Own Agent' (Joule calling third-party agents) is documented today; the inbound Agent Gateway is not yet GA as of August 2026.
SAP, Salesforce, Dun & Bradstreet — SAP's MCP surface joins 100+ MCP connections in Corin's catalog as of August 2026, every tool call policy-gated, approved, and audited. Corin speaks MCP in both directions — a governed client of 100+ servers, and an MCP server your own copilots can call, behind the same policy gates.
Built for Infor and SAP. Not connected to them — fluent in them.
Fluent means the released-API catalog above, the simulate service by name, and a dry run before every write — not a logo on a slide.
The connection surface, as spec.
Every system Corin touches: the interface it connects through, the surface that carries the work, and what stays untouched in your landscape.
| System | Interface | Surface | Preserved |
|---|---|---|---|
| SAP S/4HANA Cloud | Released public APIs — OData V4/V2, SOAP | Sales Order A2X · Simulate A2X · Supplier Invoice · Journal Entry Post · Event Mesh · MCP Gateway | Clean core — released APIs and events only, no modifications |
| Infor M3 | ION API — REST + SOAP | Verified tenant catalog — 44,216 M3 operations across 3,143 services | Custom fields and Mongoose screens untouched |
| Infor CSI / SyteLine | ION / IDO (Mongoose) | IDO methods exposed through the ION API gateway | Approval rules and configurations stay in CSI |
| Microsoft 365 | Microsoft Graph + Entra ID | Shared mailboxes · Outlook drafts · Teams approvals | Mail stays in your tenant — nothing is auto-sent |
| EDI network | X12 850 / 855 / 856 / 810 / 820 | Orders · acknowledgements · ship notices · invoices · remittance | One network partner — no per-partner mapping projects |
| Bank & lockbox | BAI2 · camt.053 | Statements in · remittance matched · NACHA staged | Payments released only with human confirmation |
| D&B | Direct+ | Credit reports · proposed limits · monitoring | Credit policy stays yours — bureau data informs, procedures decide |