SAP integration

SAP is the system of record.
Kernos is the system of governance.

Most tools pipe data between systems and hope. Kernos wraps every SAP write-side action in the governance loop — staged, approved, audited — and never claims success until SAP itself confirms it.

Standard interfaces: OData · IDoc · BAPI · Events · CDC — no custom ABAP in your core.

The three iron laws

Boring rules. On purpose.

Integration failures destroy trust in AI faster than missing features ever will. Kernos encodes three non-negotiable laws into the runtime — they are not configurable away.

Law 01

A command is not a success

Kernos dispatches the command, then waits for SAP's authoritative result event. Until that event arrives, the action stays staged or pending — never optimistically marked done.

  • No optimistic write-back status
  • Intermediate states are explicit
Law 02

Degrade safely, never bypass

If SAP is unreachable, actions queue for recovery or hard-stop at critical control points. The approval loop is never bypassed to keep things moving.

  • Recoverable hold vs strict block, by control point
  • Governance continuity over throughput
Law 03

Every write is reconciled

Three-way reconciliation compares platform state, SAP state, and field evidence. Discrepancies become tracked items — not silent drift.

  • Idempotent retries with exponential backoff
  • Dead-letter queues, nothing lost
Coverage

Standard interfaces. Full write path.

Kernos connects through standard SAP interface families — read, write, and change-data-capture — and maps external keys to your ontology so agents act on the same objects your business runs on.

Read & write

OData services

Structured reads and governed writes against S/4HANA OData services — schema-aware, typed, and approval-gated on the write path.

Documents

IDoc

Document exchange with status tracking — intermediate states visible, failures land in the dead-letter queue with replay.

Functions

BAPI

Business API calls wrapped as governed actions: staged, approved, executed, reconciled.

Events

Event streams

SAP events land as authoritative confirmations — the signal that turns a staged action into a completed one.

Change capture

CDC

Change data capture keeps your ontology projections current without full-table polling.

Identity

MDM external-ID mapping

External keys map to ontology objects, so "customer 1000123" and your customer object are the same thing — with lineage.

Data & trust

Your SAP credentials never leave your perimeter.

Kernos deploys in your environment. Connection settings, credentials, and business data stay inside your instance; what crosses to us is a support conversation, not your data. Every connection is visible, every action is attributable, and the whole chain is auditable — because it is stored where you control it.