What's behind a verdict
When you paste a scope and get a fit/gap answer, this is what it was checked against. Every figure below is counted live from the database — nothing here is a marketing estimate — and every requirement carries its provenance tier in the open.
Provenance, by tier
We don't collapse provenance into one "vetted" number. Each requirement carries the tier it has actually reached, and the ladder is visible to every role on the platform.
Plus 9,460 candidates in the intake queue that have not reached the live corpus at all. 421 live requirements are already mapped to the outcome documents they produce.
Not just knowledge — delivered work
Behind the corpus sits an indexed archive of 35,139 documents from real implementation programs — functional specs, process flows, configuration guides, design decisions. When a verdict says a requirement is standard, the validate view can show the actual deliverable that was shipped for it.
Where the depth is
- Finance6,144
- Treasury1,751
- Procurement680
- Order to Cash556
- Supply Chain313
- Analytics & Reporting110
- Manufacturing68
- HR & Payroll48
Top workstreams by live requirement count, of 30. Finance-led, by design — that is where the field archive is deepest.
Release coverage
The Upgrade Advisor keeps a version matrix across 11 releases (ECC 6.0 through S/4HANA 2025) and a line-by-line layer of 1,334 documented changes from SAP's Simplification Lists and What's New guides — 692 citing an SAP Note.