KPT logo KPT
EN ES PT
← Back to Trust

SAP / ERP integration · full transparency

How KPT integrates with SAP S/4HANA — today, in 90 days, and certified.

Industrial-AI buyers rightly ask: does this thing actually talk to my system of record? Here is the honest answer in three phases — what runs today against a real SAP S/4 sandbox, what we ship in 90 days for production-grade write-back, and what we earn as an SAP-certified ICC partner over 12 months. Full transparency on cost and timeline.

TODAY

Read-only ingestion + planner-approved write-back via standard APIs

Already running at PVM, validated against their non-prod sandbox.

  • Standard REST + OData reads of SAP production orders, work centers, BOM, and master data — on a polling schedule the customer controls.
  • Aurora-backed tenant store with row-level security; every read is scoped to the customer's tenant ID.
  • Optimization engine (CP-SAT) computes the plan; recommendations surface in Lighthouse with predicted KPI deltas.
  • Planner approves, edits, or rejects each suggestion in the UI — no auto-apply.
  • Approved actions write back to SAP via the same standard REST surface; every read + write is logged to an append-only audit_log.
90 DAYS

Custom RFC + SAP Cloud Connector + hardened write-back path

From signed PoC to production-grade write-back, no certification yet.

  • Custom ABAP RFC modules for write-back fields without a clean REST equivalent.
  • SAP Cloud Connector wired up so on-prem S/4 stays inside the customer's network perimeter.
  • OData v4 batch reads to replace per-table polling for large catalogs.
  • Idempotency keys + two-phase commit (stage in KPT, confirm in SAP, reconcile).
  • /api/v1/sap/health upgraded with per-table lag, last write success, queue depth; customer SAP admin dashboard included.
12 MONTHS

SAP-certified ICC partner status

Series-A use-of-funds line item — we are stating the cost openly.

  • Months 1–2 — enroll in SAP Integration & Certification Center (ICC) program; scope to the relevant certified scenario.
  • Months 3–5 — implement against SAP's certified API set (OData, BAPI, SOAP); prepare test scenarios per SAP's checklist.
  • Months 6–9 — execute ICC remote validation: connectivity, error handling, performance, security review; address findings.
  • Months 10–12 — earn SAP-certified integration logo + SAP Store listing; large-enterprise procurement paths unlock.
  • Indicative budget: USD 130–220k across ICC fees, SAP-specialist engineering, audit, listing — final figure TBD at kickoff.
WE WILL NOT

What is deliberately out of scope

Per the VC's explicit ask: be super transparent.

  • Claim SAP-certified ICC partner status before the program is complete (target: 12 months from kickoff).
  • Promise real-time bi-directional sync. Reads are scheduled; writes are planner-gated. That is a design choice, not a limitation.
  • Auto-execute suggestions. Every write requires a human in the loop, today and at full certification.
  • Modify customer-owned ABAP source. RFC modules sit alongside, not inside, customer code.
  • Operate the customer's SAP system or migrate data out of it. SAP remains the system of record for everything.

For an NDA-gated walkthrough of the architecture, the certification roadmap, or the use-of-funds breakdown, email trust@kpt.tech.