SAP Readiness Check for S/4HANA Conversion
SAP Readiness Check analyzes uploaded source-system data to highlight S/4HANA conversion topics such as simplification-item relevance, add-ons/business functions, custom code, sizing/data volume, interfaces and other checks supported by the current assessment version. It is a planning and scoping accelerator, not the production conversion gate by itself; mandatory Simplification Item Check, consistency checks and project-specific remediation still have to be completed.
Practitioner guide to SAP Readiness Check for S/4HANA Conversion, covering architecture, when to use it, operational evidence, decision criteria, common failure modes, S/4HANA context, ownership and production review checkpoints.
Reviewed by an ERPClimb SAP consultant on 20 Sept 2026· 730 words
What it is
Readiness Check is a SAP cloud-based assessment service. A source ERP/S/4 system runs SAP-provided data collectors, then the generated data is uploaded to a Readiness Check analysis where dashboards summarize conversion-relevant areas. The exact check catalog evolves by version and scenario, but the purpose is consistent: make technical/business impact visible early enough to plan work. Findings can identify relevant simplification items, unsupported or impacted add-ons/business functions, custom-code volume/usage, data volume, interfaces and Fiori-related opportunities. Results are based on collected snapshot data and rules for a chosen target; they must be interpreted by application owners.
When to use it
Run Readiness Check early during S/4HANA assessment and refresh it as source landscape/data/custom code change materially. Use it to size workstreams, assign owners and identify blockers that require deeper SAP/application analysis. Do not use a green dashboard as permission to skip Simplification Item Check, CVI validation, add-on certification, ATC or rehearsal conversion. Readiness Check is most valuable when findings are converted into a tracked remediation backlog.
How it fits the stack
Readiness Check complements Maintenance Planner, Simplification Item Catalog/Check, ATC/custom-code migration, sizing tools and SUM/DMO. It aggregates assessment signals but does not execute the technical conversion. Application teams investigate simplification findings, Basis resolves add-ons/technical prerequisites, developers assess custom code, and project management uses the dashboard for planning. Because results are point-in-time, months of development after collection can make parts stale.
A worked example
A program plans conversion in nine months. Readiness Check flags business functions, 12 relevant add-ons, high custom-code volume and several large tables. The team assigns each to an owner and discovers one third-party add-on will not support the target release, a true schedule blocker. Six months later they rerun the collection because the source has changed significantly and confirm custom-code usage/remediation improved. Production readiness is still decided by mandatory checks and rehearsal conversion, not by the dashboard alone.
How to choose
- Run early enough that add-on or data-model blockers can change the program plan.
- Choose the intended target release/scenario accurately.
- Assign every material finding to an application/technical owner.
- Rerun after major remediation or long assessment-to-conversion gaps.
- Use findings to prioritize deeper checks, not as a replacement for them.
Common pitfalls
- Treating Readiness Check as a one-time PDF rather than a remediation input.
- Assuming a finding marked relevant means every listed business process is broken.
- Assuming no finding means every custom interface is safe.
- Using stale collection data after months of source-system change.
- Confusing Readiness Check planning with the mandatory Simplification Item Check executed for conversion.
ECC, S/4HANA and clean core
Readiness Check is specifically intended to support SAP transformation/conversion assessment and evolves with SAP's target releases and cloud/private scenarios. Always use the current collector instructions and check catalog. Selective transition or Public Edition migration may use different assessments in addition to or instead of classic system-conversion checks.
Whose problem this is
Architecture/program management coordinates the assessment; Basis runs collectors and technical checks; functional leads interpret simplification/business findings; ABAP owns custom code; vendors own add-on readiness; data teams own volume/archiving candidates.
Related SAP objects
Reviewed pages this object connects to in the ERPClimb knowledge graph.
Source: ERPClimb — https://erpclimb.com/sap-technical-topics/sap-readiness-check-s4hanaERPClimb is an independent platform and is not affiliated with SAP SE. Reference pages are written and reviewed by SAP consultants for learning and troubleshooting.