AI strategy, transformation, and fluency, with governance and evals built in.See the full operating read →
An enterprise SAP estate facing the ECC end-of-support deadline
Proving Nothing Regressed In An ERP Migration
A reference design for software-led ECC→S/4HANA ABAP transformation that proves equivalence by replaying real production data — so you can migrate the highest-variance code line and prove nothing regressed.
The proof
The number, kept honest.
01
The challenge.
Every SAP customer must finish the ECC→S/4HANA migration before support ends, and custom-ABAP remediation is the most heavily-staffed, highest-variance part of it. The real risk isn’t writing new code — it’s proving the migrated code behaves exactly as the old code did. Brittle, manual remediation can’t prove equivalence at scale.
02
The approach.
Static anti-pattern detection across the ABAP estate, then a deterministic codemod core with a scoped LLM edge for the cases that genuinely need it — deterministic-first, LLM-second.
Prove equivalence by replaying historical production data: reconciliation parity plus branch-coverage acceptance gates (“no green, no ship”).
Hand validated code back through the customer’s own transport, with a tamper-evident, attributable decision trail for audit.
03
What shipped.
A reference architecture and engine design: anti-pattern detection, deterministic codemod core + scoped LLM edge, the replay-based parity and coverage gates, customer-transport handback, and the tamper-evident decision trail.
AI built across the board
Start with the AI work that moves the number. Keep the proof built in.
Start with Strategy, Transformation, or Fluency; use Quick Audit when the first need is an independent read on what is already running.