Reading Your Own Risk: The Readiness Assessment
Lesson 3 — A client asks 'how bad is it, really?' and the honest answer requires a number you don't currently have. Here's what a readiness assessment actually measures, and why the score matters less than what's underneath it.
Prerequisites
- Lesson 2: What Clean Core actually means
A client sponsor eventually asks the blunt version of the Lesson 1 question: “how bad is it, really?” Giving an honest answer requires a number you almost certainly don’t have yet — which is exactly what a readiness assessment produces.
What actually gets measured
A readiness assessment scans your custom ABAP objects against a rule set — deprecated tables, non-released function modules, direct SQL on cluster tables, and dozens of other S/4HANA compatibility patterns — and classifies every finding by severity.
Why the single score is the least useful part of the report
A client sponsor will fixate on “we scored 62 out of 100” — but that number, alone, tells you almost nothing actionable. The distribution underneath it is the real answer. A hundred Critical findings concentrated in three programs is a completely different project than a hundred Low findings scattered across four hundred programs — different timeline, different cost, different risk to the go-live date, even if both produce the identical overall score.
Insist on seeing the breakdown by severity and by object, not just the headline number, before you commit to a single word of a project plan.
Try it yourself
If you have access to a real scan output — or even a plausible hypothetical one — sort the findings by severity, then ask: are the Critical findings concentrated in a handful of programs, or spread thin across many? Write one sentence explaining what that concentration pattern means for how you’d sequence the remediation project.
Go deeper
For what the assessment actually checks against — the full rule set and the ECC-to-S/4 object mapping table — read The ABAP S/4HANA Readiness Assessment, or run one yourself with a free readiness scan.
Key takeaways
- A readiness assessment classifies every finding by severity — Critical, High, Medium, Low — against S/4HANA compatibility rules.
- The single overall score is the least useful number in the report. The distribution across severity and object is what actually shapes the project plan.
- Insist on the breakdown, not just the headline, before committing to any timeline or budget.
Next: you have the list. Now — how do you fix it without rewriting everything, and without a rewrite quietly ballooning the budget?