The ERP is not being replaced — it is being elevated. SAP S/4HANA continues to own governance, accounting accuracy, and regulatory compliance. The intelligence layer — automation, AI reasoning, and workflow decisioning — runs on top through BTP and partner ecosystems. SAP ensures the core stays reliable. Skill agents ensure the knowledge around it never retires.
Innovation no longer lives inside the core. SAP provides the governed, compliant system of record. Skill agents deliver the intelligence on top — turning tribal consultant knowledge into a versioned, reusable asset.
Every rectangle is a pocket of API capability. Size is proportional to published OData endpoints. The highlighted cell is what one skill library has covered today — one submodule, FI-AR. Every other rectangle is the opportunity ahead.
The treemap makes the opportunity visible. 172 skill atoms covered one slice — cash application, dunning, disputes, collections, aging, write-off, credit, onboarding, invoice generation, payment exceptions. It works, and the architecture proved out on it.
But it's one submodule of one module. There are nine more submodules in FI alone — Accounts Payable, General Ledger, Asset Accounting, Banking, Treasury, Travel, Special Purpose Ledger, Legal Consolidation, Fund Management — each of comparable complexity. And eight more Lines of Business behind Finance.
Atomising one submodule is the hard part. Every subsequent one uses the same patterns: crawl, atom extraction, verification, skill authoring, policy calibration. The first submodule takes months. The tenth takes weeks. The hundredth takes days.
Click a persona to see the job-to-be-done, the skills that fire, and a real example interaction drawn from the live skill files.
Three layers. Every persona question flows top-down. Every answer is cited back to the skill file and the SAP system of record.
No framework. No bespoke DSL. Just versioned Markdown — diffable, reviewable, portable — carrying the exact knowledge a senior SAP consultant would bring to the workshop.
Declares the skill name, description, and version. The description is the router's matching surface — it tells the agent when this skill should fire.
Slash aliases like /aa-config, /aa-gap, and natural-language triggers ("fixed assets setup", "depreciation configuration") both route to the same file.
The first section frames what belongs here and what doesn't — upstream (MM, PS), downstream (FI-GL, CO), out-of-scope (REM, equipment catalogs).
Each section walks through a configuration area with the exact IMG path, the T-codes in order, and the critical decisions (e.g. "Chart of Depreciation is a go-live lock").
A complete T-code map at the bottom gives the agent instant recall — no hallucinated codes, no missed edge cases.
Every skill ends with integration hooks so the router can chain skills — AA calls CO for cost-centre allocation, CO calls FI for GL posting, FI calls BTP for interface routing.
Each skill is authored once, versioned in git, and composable with every other skill. Live skills are callable today; the rest ship on the quarterly roadmap.
The shape of the library: Finance leads because it's where IBM Client Zero proof points are strongest. Procurement catches up in Q2. HR closes out by Q4 — by which point every S/4 LoB has at least one reference skill.
Start with a single persona lane — Finance, Procurement, or HR. Wire up the 12 live skills against your S/4 and BTP tenants, and we'll benchmark time-to-answer against your current ticket queue in 30 days.