Now accepting guest editorial from SAP, Oracle, Workday and ServiceNow practitioners.Pitch a guide
The Sign-Off Table
All guides

The complete guide · Strategy & transition paths

SAP Readiness Check for S/4HANA: Step-by-Step Guide

Run SAP Readiness Check for S/4HANA step by step, read each results tile, and turn the findings into scope, estimates and test conditions.

Matt Angerer
November 16, 2026 · 27 min read · 22 sources

SAP Readiness Check for SAP S/4HANA is the self-service analysis you run against an existing SAP system to see what a move to S/4HANA will touch. It is available to all customers with an active SAP maintenance agreement, and it is reached through SAP for Me or directly at me.sap.com/readinesscheck. You implement a set of data collectors in the source system, run them, download a ZIP file, and upload that file to create an analysis. The dashboard then shows the results.

For a test manager or CoE lead, the value is timing. The findings are the cheapest scope signal you will get before the first mock conversion. Each relevant simplification item, custom code hit and interface finding is a candidate test condition. If you read the report only after the test plan is locked, you are testing against assumptions that the data could have corrected.

This part covers what the tool is, how it differs from the Simplification Item Check and the custom code ATC run, where to run it, the prerequisites, the step-by-step run, and a tile-by-tile reading of the results. Part 2 covers turning the findings into scope, test conditions, re-runs, common errors and the FAQ.

Key takeaways
  • SAP Readiness Check is a planning analysis. The Simplification Item Check and custom code checks are separate, and the SI-Check is the one you have to run.
  • Access depends on SAP for Me with an active maintenance agreement, or an SAP Cloud ALM tenant. Analyses do not sync between the two platforms.
  • Implement SAP Note 2913617 in DEV, then run the collectors against production or a copy that carries the right workload history.
  • The effort ranking leaves out custom code and user training. Treat it as a floor, not a total.
  • Every relevant simplification item, custom code finding and interface finding should become a traceable test condition before the first mock conversion.

1. What SAP Readiness Check is, and what it is not

Readiness Check is an analysis. It reads your system, reports what it finds and gives you a view of effort. It does not convert anything, and it is not the check that gates the technical conversion. SAP provides the Simplification Item Check and custom code checks that you need to run before doing the conversion. Readiness Check sits upstream of those checks as the planning view.

The tool covers more than one target. The scenarios SAP lists include SAP Readiness Check for SAP BW/4HANA conversion, SAP ERP usage and data profiling, and SAP Readiness Check for SAP Cloud ALM, along with SuccessFactors, Customer Experience and Datasphere/BW Bridge. For S/4HANA, the target can be an on-premise release or a private cloud edition, which SAP confirmed in an update dated 4/11/2025 stating that SAP Readiness Check for SAP S/4HANA can be used for SAP S/4HANA on premise and SAP S/4HANA private cloud (PCE/RISE) as the target product version. Choose the target version deliberately, because the results are calculated against it.

SAP's guidance is to start early. The check should be run very early in a transition project, during the Discover phase, and then repeated to track how system preparation progresses as the conversion date approaches. A Q4 baseline is a sensible use of the tool if a 2027 budget depends on the number. Treat that first run as a baseline, not a verdict.

2. Readiness Check, SI-Check and custom code ATC: which is which

Most confusion on a project comes from treating these three as one tool. Section 2.4 of the Conversion Guide for SAP S/4HANA 2025 separates them, and the tools SAP Readiness Check and Simplification Item-Check (SI-Check) are used to support the conversion process. The custom code work is a third activity with its own tooling.

CheckWhere you run or see itMandatory?Called by SUM?What it tells you
SAP Readiness CheckWeb application on SAP for Me or SAP Cloud ALM, fed by a collector ZIPNo. It is a planning analysis.NoRelevant simplification items and their effort ranking, add-on and business function compatibility, sizing, financial data quality, CVI and custom code overview
Simplification Item Check (SI-Check)Report run in the ABAP system through /SDF/RC_START_CHECK and background jobsYes. SAP provides the Simplification Item Check (SI Check) and custom code checks that you need to run.Yes. The Simplification Item-Check (SI-Check) is called by the Software Update Manager.Which simplification items are relevant to this system and whether the system is consistent with them
Custom code ATC or Custom Code Migration appABAP Test Cockpit with the S/4HANA readiness variant, or the Fiori Custom Code Migration appYes for custom code. You need to check your custom code against the SAP S/4HANA simplifications with the Custom Code Migration tool or the ABAP test cockpit (ATC).No. It runs as a separate step.Which custom objects hit simplified or changed functionality, and how many
Figure 1. The three checks, who runs them and what each one answers

I built the table from the text of section 2.4 that I could access, with the SUM column taken from the 2025 upgrade guide. Confirm each row in the current PDF before you quote it to a steering committee.

The Simplification Item-Check is the operational tool. The Simplification Item-Check (SI-Check) identifies all simplification items relevant for the current system. Readiness Check uses that same catalog to build a picture for planning, and it adds sizing, add-ons, business functions and data quality on top. Custom code is handled through the simplification item concept as well, since the custom code migration checks are based on the simplification item concept.

A simplification-item tile with a High effort ranking, its effort drivers opened, and an arrow to a test condition in the tracker.

3. Where to run it: SAP for Me, SAP Cloud ALM and the deployment note

There are two front doors to the same tool. On SAP for Me it is reached through the Service & Support menu, under ALM, or directly at me.sap.com/readinesscheck. On SAP Cloud ALM it is available to customers with a tenant and is accessed through the Implementation and Service app catalogs. Your landing page is the same tool either way, so pick the platform your programme already uses for governance.

The deployment rules are in SAP Note 3344480. For more information, refer to SAP Note 3344480 – SAP Readiness Check Deployment Options. Read it before you commit to a platform, because the two environments behave differently in one important way. SAP Readiness Check analyses processed on one platform are not automatically replicated to the other.

The Cloud ALM route has a practical benefit. Customers can use an extended integration option with project and task management in SAP Cloud ALM. If you run from SAP for Me, you can manually generate tasks and upload them to SAP Cloud ALM. Each scenario is its own analysis, so a BW/4HANA or other scenario alongside the S/4HANA conversion needs its own run.

  1. Do you hold an active SAP maintenance agreement?Yes → continue · No → resolve access with your SAP account team before you plan the run
  2. Do you have an SAP Cloud ALM tenant with the Implementation and Service catalogs?Yes → run in Cloud ALM and create follow-up tasks there · No → run on SAP for Me and upload tasks to Cloud ALM once the tenant is live
  3. Does the steering committee need both views?Yes → create one analysis per platform from the same ZIP, using the same data archive generated by the data collector · No → keep one platform as the system of record and note its analysis ID in the RAID log
Figure 2. Choosing where to run Readiness Check and how to keep the results aligned

4. Prerequisites before you start

Start with the central note. SAP Note 2913617 is the framework for the data collection, and it is frequently updated with tips and changes. Read it in full before you implement anything, and check its version again on the day you run, because the collector list moves with the note.

Next, prepare the Note Assistant. Community guidance for the readiness setup asks you to implement the current version of SAP note 1668882 to update the Note Assistant. Use SNOTE to compare your system against SAP's current note versions. Before you address the findings, use the Check SAP Note Version option to confirm that the latest version of each SAP Note is considered. This feature uses the communication channel to the SAP support backbone to pull the most recent note version number. Also watch for version warnings. In one reported case, a note that did not support the private cloud edition triggered a warning that strongly recommended upgrading to the latest SAP Notes version and performing the check again.

Sizing depends on support package levels. The note says that to include sizing on the dashboard, it is recommended to have min ST-PI 740/SP07 or 700,710/SP17. If your levels are lower, clear the HANA sizing option when you schedule the run. Confirm the exact thresholds in the note before you schedule anything, since community posts quote them from earlier versions.

Workload history matters more than most teams expect. Several simplification item checks depend on what the system actually uses. For simplification items, the check is based primarily on table contents and used transactions. Check in ST03N that the workload history covers the period the note expects. If you run on a copy, the usage data has to travel with it. If using copy addition step is required to download usage data (st03n) from production system and upload into the copy system following the SAP Note 2913617.

Run it on production when you can. The guidance note recommends explicitly analyzing the production system, as the results from this system are the results that should be used during the scoping and planning of the conversion project. A recent copy is acceptable when production is off-limits, but then the copy has to match production closely.

Authorizations are narrow but easy to miss. For scheduling the data collectors, a user needs the S_PROGRAM object with the RC_COLL program group and the SUBMIT, BTCSUBMIT and VARIANT actions. For scheduling SAP Readiness Check data collectors, a user requires the authorization object S_PROGRAM with values P_GROUP = RC_COLL and P_ACTION = SUBMIT, BTCSUBMIT, VARIANT. SAP also revised the authorization concept, documented in SAP Note: 3310759 - Revised Authorization Concept for SAP Readiness Check.

5. Step by step: prepare, collect, upload and analyze

The run has four phases and four owners. The Basis team implements and runs the collectors, the project team reads the output, and the platform owner handles the upload. The flow below shows the sequence from note implementation to re-run.

  1. Basis teamImplement 2913617 and dependencies in DEV, then transport to production
  2. ECC production systemRun the collectors and background jobs, and watch them in SM37
  3. Basis teamDownload the ZIP after the last job finishes, and complete the sensitive data review
  4. SAP for Me or Cloud ALMUpload the ZIP; the analysis moves from In Preparation to Available
  5. Project teamTriage findings by owner: functional, ABAP, Basis, finance, integration
  6. Project teamCreate follow-ups as Cloud ALM tasks with the analysis ID attached
  7. Project teamRe-run before each mock conversion and compare against the baseline
Figure 3. Swimlane view of the run, with the owning lane in bold on each step

Prepare: notes and transport

  1. In DEV, implement SAP Note 2913617 and the notes it lists as dependencies. Implement the notes mentioned in SAP Note 2913617, as well as their dependencies, in your ERP landscape.
  2. Transport the collectors to the system you will analyze. Transport the collectors to the system being analyzed, i.e. production or a recent copy of production.
  3. Check the target version list. If your target release is missing, update the local catalog. If the data collectors for SAP Readiness Check were initially implemented before the official release date, you may need to update your local replica of the simplification item catalog. To determine whether any action is required, run report RC_COLLECT_ANALYSIS_DATA in transaction SA38.

Collect: run the collectors in production

  1. Run RC_COLLECT_ANALYSIS_DATA in the productive client. Select the target S/4HANA version, schedule the analysis, choose Immediate and confirm. Use SM37 to follow the jobs.
  2. For the detailed simplification list and the SI data, run /SDF/RC_START_CHECK. Report /SDF/RC_START_CHECK is for detailed simplification list and RC_COLLECT_ANALYSIS_DATA is for Readiness Check.
  3. Expect several jobs in sequence. There are various jobs launched in order, and you must check the job logs to ensure the data was collected properly.
  4. Schedule sub-checks one at a time or in small groups, and wait for each one. Once the data collection has started for the sub-check(s) you have chosen, you must wait for the relevant job(s) to complete before scheduling the next sub-check or next batch of sub-checks, otherwise you will overwrite the existing .zip file data.
  5. Schedule the financial data quality check in an active client, not client 000. Keep in mind that the FDQ check should be scheduled in your active client, not in client 000. The FDQ check is an optional box on the scheduling screen. To include the Financial Data Quality check in the SAP Readiness Check analysis results, select the checkbox prior to scheduling the analysis.

Download, review, upload and analyze

  1. Download the ZIP after the job finishes. Execute program RC_COLLECT_ANALYSIS_DATA in transaction SA38 in the production system to download all checks except the consistency check in the zip file by clicking the button "Download Analysis Data" after the job is completed.
  2. Review the file before it leaves your network. The note explains in detail what data is extracted from your system and how you can review it if you are interested in this security related information. Have your security team sign off on that review. It is a control we recommend, not an SAP requirement.
  3. Upload it. After data collection, launch the landing page of the SAP Readiness Check application, choose Start New Analysis, and name the analysis. Upload the ZIP file generated from RC_COLLECT_ANALYSIS_DATA, review the terms, and select Create.
  4. Wait for processing. The status changes from In Preparation to Available, which lets you explore the results on an interactive dashboard.

6. Reading the results, tile by tile

The dashboard has many tiles, but they answer three questions in order. What blocks the start? How much work is ahead? What data needs cleanup? Compatibility, or what blocks the start: simplification items, compatibility scope analysis, active business functions, add-on compatibility. Effort, or the work ahead: activities related to simplification items, custom code analysis, integration, app availability and recommended SAP Fiori apps. Data: financial data quality, customer vendor integration with the Business Partner record, and target system sizing. Read the tiles in that order.

Simplification items and effort ranking

Each relevant simplification item carries an effort ranking. The Effort Ranking bar chart assigns a priority to each of these issues: low, medium, potentially high, and further assessments required. Some items explicitly need an expert assessment rather than a number. The ranking is a starting point. The effort ranking does not take into account custom code and user training activities in the analyzed system.

Effort drivers explain the ranking for the items that need them. This section provides visibility for those identified effort drivers related to the selected simplification item. These effort drivers and associated thresholds are based on previous SAP S/4HANA project experiences. Open the drivers for every Potentially High item and record the driver values in your tracker. Those values are what you will argue about in the estimate review.

Compatibility scope, add-ons and business functions

The compatibility scope view shows which simplification items sit inside the compatibility packages you are moving through. Use the compatibility scope entry as the reference for the term. Add-ons and business functions are the blockers that do not show up in a normal test plan. Three kinds of finding stop an SAP S/4HANA conversion before it starts: incompatible add-ons, active business functions incompatible with the target release, and simplification items that require an expert assessment. For an active business function that is incompatible, SAP recommends raising a support incident, because the project team has no workaround available on its side.

Sizing and transactional backlog

Sizing answers how big the target database will be. SAP Readiness Check performs a system sizing of the target S/4HANA, taking into consideration future data growth, potential new requirements, and archiving. The useful part is the before-and-after view. Preview how the sizing requirements will change after a data cleanup. The transactional backlog tile flags old, open and overdue documents. If these documents are unnecessarily migrated, it can impact S/4HANA processes such as Fast Close or MRP run. Those documents are test data decisions as much as cleanup decisions.

Custom code

The custom code tile combines results from two sources. The custom code analysis in SAP Readiness Check shows the results of the custom code analyzer (SYCM) and the ABAP test cockpit (ATC) or the SAP Fiori Custom Code Migration app. Results are grouped by simplification item and by the type of remediation needed. The results are grouped by simplification item and type of remediation (that is, functional redesign versus technical code adaptation). Scope is a separate question. The scope information, meaning the split between in-scope and out-of-scope objects, appears only if you ran the SAP Fiori Custom Code Migration app.

Integration, CVI and financial data quality

The integration view surfaces interfaces that the target release changes. Older SAP material cites examples such as an overview of BW extractors and blacklisted iDoc interfaces that are affected when converting to S/4HANA. Feed those into your Interface Inventory & Test Tracker. For CVI, the tile shows the master data for your customers, vendors, and contacts that need to be synchronized before your conversion to S/4HANA. The CVI entry explains the mapping model behind that synchronization.

Financial data quality checks the general ledger, asset accounting and material ledger. The Financial Data Quality check within SAP Readiness Check has been extended to provide further finance insights, and it has been enhanced to give further insights into general ledger and asset accounting. The support component tied to that analysis is named in SAP's note listing, where 2972792 acts as a central SAP Note for delivering the financial reconciliation reports used by the Financial Data Quality analysis, which provides insight into the level of effort to prepare for the financial data conversion.

Fiori apps and Business Process Discovery

The Fiori tile lists recommended apps for the target release. The following checks are available in SAP Readiness Check for SAP S/4HANA upgrades: Simplification Items, Recommended SAP Fiori Apps, Integration, Custom Code Analysis, SAP Innovative Business Solutions, and Add-on Compatibility. Business Process Discovery assigns the identified apps to status categories. The check provides visibility for potentially relevant SAP Innovative Business Solutions that need to be considered in the scope and planning of a conversion project to SAP S/4HANA. Treat app recommendations as scope inputs for the fit-to-standard workshops, not as test cases in their own right.

7. Turning findings into scope, estimates and a backlog

A dashboard does not plan the project. After upload, each finding needs one of three outcomes: a backlog item, a remediation task or a test condition. A finding with no owner and no artifact becomes a warning that nobody reads twice.

Sort simplification items by business area first. Then split them into two buckets in our convention. Mandatory items are changes the conversion cannot finish without. Conditional items matter only where the business runs the function, so the business owner decides them and the decision goes into the RAID log with a date. The effort ranking sets the order of work. It does not set scope.

Move follow-ups into the project tool early. Cloud ALM now supports raising follow-up items from the Transition Activities detail pages across all ALM areas, according to SAP's Readiness Check release notes. Attach the analysis ID and the collector run date to every task. A task that cannot be traced to a specific run will be argued about at the steering committee. For how the Cloud ALM project structure works, see our getting-started guide for Cloud ALM.

For estimates, use the effort drivers rather than the ranking alone. Effort drivers for Potentially High ranked simplification items were released as generally available in November 2020, per SAP's Community post on that release. Open the driver values for each Potentially High item and write them next to the hours they justify. Then add the lines the ranking leaves out: custom code remediation, business process training and test execution by cycle. The SAP Test Estimation Model has a line for each, and the academy course Estimating and Planning Testing and Data Migration Effort walks through the method.

Result tileOwnerArtifact it produces
Simplification itemsFunctional lead for the business areaTest condition in the Simplification Item Test Impact Tracker; mandatory or conditional backlog item
Custom codeABAP leadRemediation task and retest entry in the custom code retest tracker
Add-onsBasis leadCompatibility decision and an upgrade or replacement task with a vendor date
Business functionsFunctional lead with the business ownerKeep, switch off or replace decision logged in the RAID register
IntegrationIntegration leadRow in the Interface Inventory & Test Tracker
CVIMaster data lead with the functional teamBusiness Partner mapping task and a cutover estimate line
Financial data qualityFinance leadReconciliation test condition and a data cleanup task
Planned downtimeCutover lead with BasisCutover estimate and a downtime window to confirm with the business
Figure 4. Findings-to-action map: which owner takes each result tile and what artifact it should produce

8. Turning findings into test scope

Every relevant simplification item becomes a test condition. A condition row needs five things: the simplification item number, the transaction or Fiori app it touches, the business process it sits in, the expected behavior after conversion and the test case IDs that prove it. If an item has no business process in scope, record "not applicable" with a reason. Silence is not a decision.

Consistency errors need a separate track. The SI-Checks verify the data consistency that the conversion of existing data depends on. Those results belong in your data migration reconciliation plan, not only in SIT. Where an error can be exempted, the exemption is created as a logged exception in the system, and the report flags it in an "Exemption Possible" column. Treat each exemption as a test condition as well. Someone has to prove that the business accepts the consequence, and the Data Migration Reconciliation Checklist is where that proof sits.

Interface findings go into the interface inventory, one row per interface, with the test type that proves it works after conversion. Our guide on testing migrated PI/PO interfaces in Integration Suite covers the middleware side. Custom code findings feed the retest tracker. A remediated object is changed code, so it gets its own regression slice. Our piece on turning ATC clean core results into regression scope shows how to build that slice.

Sequence the work by effort and risk, not by tile order. Put the high-risk items in the first mock so the fixes have time to land before the second mock.

Low effort, low riskBatch into the next cleanup sprint and confirm with a smoke test.
Low effort, high riskFix now and prove it with a targeted test condition in the first mock.
High effort, low riskSchedule it, record the driver values and confirm the business window.
High effort, high riskName an expert owner, run a dedicated SIT condition and add it to the go/no-go evidence.
Figure 5. Triage matrix for simplification-item test conditions, used to choose what runs first in each mock

9. Using Readiness Check for S/4HANA upgrades

An upgrade moves a system from one S/4HANA release to a later one. It does not start from ECC, so the scope and the collector note both change. Conversions follow SAP Note 2913617, while upgrades follow SAP Note 3059197. Check the note version on the day you run, because SAP updates the target list and the collectors as new releases and feature packs ship.

The results differ too. SAP's Community walkthrough for the upgrade scenario lists active business functions, add-on compatibility, custom code, recommended Fiori apps, simplification items, compatibility scope, integration analysis and innovation potential. That list does not name sizing, CVI or financial data quality. The conversion walkthrough includes those, along with planned downtime and Customer Vendor Analysis. Confirm the tile list in your own analysis before you plan around a tile that may not be there.

Test the upgrade differently from the conversion. The simplification set is usually smaller, but each feature pack can change standard behavior in the areas your users run every day. Build the regression slice from the business process list and use the feature pack notes as the trigger. Our guide on S/4HANA Private Edition upgrade cadence and regression covers the rhythm, and the academy course Testing SAP S/4HANA Upgrades and Feature Pack Stacks covers the method.

10. Common errors and how to fix them

SAP's walkthroughs direct problems during preparation or execution to the support component SV-SCS-S4R. Open a case there with the analysis ID, the collector version and the job log. Most failures in the sources below fall into a short list of causes, so start with the decision path.

  1. Did the upload fail with a "not valid" or "could not be performed" message?Yes → confirm the ZIP came straight from RC_COLLECT_ANALYSIS_DATA on the same system, unedited, and re-run · No → go to the next question
  2. Does the analysis stay In Preparation?Yes → check the SAP KBA for that status, then open a case under SV-SCS-S4R if it persists · No → go to the next question
  3. Is a tile empty or showing "No data available"?Yes → check the authorizations and the ST03N workload history, then re-run the affected collector · No → go to the next question
  4. Is the custom code tile empty?Yes → upload the custom code ZIP to the existing analysis, from the same system · No → review the results and log the findings
Figure 6. Decision path for the most common Readiness Check failures
  • "Could not be performed" after upload. The related KBA lists an empty usage data file and ST03 as keywords, which points to a gap in workload history. Check ST03N coverage first, then re-run the collector.
  • Interface tile shows "No data available for this interface type". Certain data could not be collected because the user running the collector lacked some authorizations. Grant the missing objects and run a new collection. Updating an old ZIP will not fix it.
  • Uploaded file rejected as not valid. The fix is to confirm the file came from the SAP Readiness Check data collector report. Do not rename, repack or edit the ZIP.
  • Custom code ZIP will not update the analysis. An analysis is tied to the system it was created from, so a ZIP from a different system is refused. Use the same system or create a new analysis. Custom code ZIPs can only be added to an existing analysis, per the Community answer on uploading the custom code analyzer file.
  • Business Process Discovery error on upload. SAP's troubleshooting guide asks for the latest version of SAP Note 2745851 and an ST-A/PI level of 01V SP00 or later, then a re-run.
  • Target release missing from the dropdown. If collectors were implemented before the release date, the local replica of the simplification item catalog may need an update. Community sources disagree on which report refreshes it. One post points to report RC_COLLECT_ANALYSIS_DATA in SA38, another to /SDF/RC_START_CHECK. Run the one named in the note version you implemented, and log which one you ran.
  • Warning about SAP Note support for the Private Edition target. The warning says the notes may not support the private cloud target, and SAP advises updating to the latest notes and running the check again. A Community answer calls it harmless when the collector ran without errors. Our rule is to re-run, not to ignore the warning on a sign-off system.
  • Sizing missing from the dashboard. Note 2913617 expects a minimum ST-PI level for sizing, and a lower level means clearing the HANA sizing option.
  • Workload history too short. Sources disagree. A 2020 SAP Community post asks for a production system or copy with workload statistics loaded for at least six months, while a 2019 post cites six to eight weeks of transaction history. Use the number in the current version of the note, and record the window you actually analyzed.

11. Re-running it: cadence across the project

One run tells you where you started. A series of runs tells you whether the project is closing the gap. Run the check at five points, and keep one analysis per point so the trend is readable.

The first point is now. Q4 2026 is when the baseline should run, because the 2027 budget depends on it. Updating an existing analysis on SAP for Me is one option, but a new analysis per milestone is clearer for steering committees. After each cleanup sprint, re-run the collectors that cover the cleaned data. Before each mock conversion, re-run everything, so the mock is tested against the current findings and not the baseline.

  1. Q4 2026Baseline runFull collection, all relevant tiles, FDQ and sizing enabled. Record the note version and target release.
  2. After cleanup sprint 1Cleanup re-runCompare the SI consistency messages and FDQ errors with the baseline. Close or reclassify each item.
  3. Before mock 1Mock readiness runConfirm every relevant simplification item has a test condition and an owner.
  4. Before each later mockRegression of findingsCheck that fixes from the last mock did not reintroduce SI messages or custom code hits.
  5. Before cutoverFinal runFeed the final numbers into the go/no-go evidence pack and the cutover estimate.
Figure 7. Re-run cadence for a conversion project, from baseline to final run

Track a burndown view of consistency errors across runs. Count the open SI-Check messages per run, split by owner and by whether an exemption is possible. Add custom code objects by remediation type and FDQ errors by category. A burndown that falls with each run is evidence for the sign-off. A flat line late in the project is the earliest warning you will get that the schedule is slipping.

Keep one rule for every re-run: record the analysis ID, the collector date, the note version and the target release in the test status report. Without those, the next person to read the numbers cannot tell whether the change came from the system or from the run.

The bottom line

Readiness Check is the cheapest scope signal your project will get, and it is only useful if its findings turn into owned work. Run the baseline now, confirm the note version and the target release, and treat every relevant simplification item, custom code hit and interface finding as a test condition. Re-run before each mock, and let the burndown decide whether the plan still holds.

Frequently asked questions

What is the SAP Readiness Check?

It is a planning analysis that reads an existing SAP system and reports what a conversion or upgrade to S/4HANA will touch. The results appear in a web dashboard on SAP for Me or SAP Cloud ALM. The cloud application is available on both SAP for Me and SAP Cloud ALM.

What is the transaction code or report name for SAP Readiness Check?

The web application has no transaction code in the sources I checked. The in-system collector is the report RC_COLLECT_ANALYSIS_DATA, which you run from SA38 for the full collection. For the detailed simplification list and SI data, the sources also point to /SDF/RC_START_CHECK, run from SA38. Confirm the report names against the note version you implemented.

What is the SAP Readiness Check URL?

The SAP for Me entry point is me.sap.com/readinesscheck. You need an SAP user with access to SAP for Me, or an SAP Cloud ALM tenant, to reach the analysis pages. Analyses created on one platform do not appear on the other, so pick one as the system of record.

Is SAP Readiness Check free?

I did not find a fee or price in the sources I checked. SAP's walkthroughs describe the analysis as optional. Access depends on your SAP entitlement, so confirm the commercial position with your SAP account team before you commit budget or staff time.

What is the difference between SAP Readiness Check and the Simplification Item Check?

Readiness Check is a planning analysis with a dashboard, sizing and effort views. The Simplification Item Check is the consistency check that the conversion tooling runs against the system. You run Readiness Check to plan, and you run the SI-Check to prove the system is ready to convert. The two use the same simplification item catalog, but only one of them gates the conversion.

How do I run SAP Readiness Check step by step?

Implement SAP Note 2913617 in DEV and transport the collectors to production or a matching copy. Run RC_COLLECT_ANALYSIS_DATA, watch the background jobs in SM37, and download the ZIP only after the last job finishes. Upload the ZIP to the Readiness Check application, start a new analysis and wait for it to change from In Preparation to Available. Then triage the findings by owner and create follow-ups. The full sequence is in the step-by-step section above.

Can SAP Readiness Check be used for S/4HANA upgrades?

Yes. The upgrade scenario uses its own note, SAP Note 3059197, and a target release later than your current S/4HANA version. The results list is narrower than the conversion list, so check which tiles appear in your analysis. Re-run it before each upgrade test cycle, because feature pack changes can alter the findings.

Sources

  1. Conversion Guide for SAP S/4HANA 2025, SAP SE, 2026-10-07
  2. SAP Readiness Check: Key Feature Overview, SAP Readiness Check team, 2026-09
  3. What's New in SAP Readiness Check, SAP Help Portal, undated
  4. Deciding on Appropriate Approach, SAP Learning, undated
  5. New Planned Downtime Calculator in SAP Readiness Check Is Now Live, SAP Community, 2021-04-14
  6. SAP Readiness Check for SAP S/4HANA now supports SAP S/4HANA private Cloud / RISE Target Versions, SAP Community, 2025
  7. How to Update Your Implementation of SAP Readiness Check to Support the latest SAP S/4HANA Release, SAP Community, updated 2025-10
  8. Upgrade to S/4HANA: t1 Readiness Check, SAP Community, updated 2026-02
  9. S/4HANA Conversion - t2 - Readiness Check 2.0 step by step, SAP Community
  10. Conversion to S/4HANA 1809FPS0 - t2 - Readiness Check 2.0, SAP Community
  11. SAP Readiness Check 2.0 - Setup & Execution, SAP Community, 2020-06-02
  12. SAP Readiness Check for SAP S/4HANA: What's New in November 2020, SAP Community, 2020-11-26
  13. SAP Business AI Capabilities Tile in SAP Readiness Check, SAP Community, 2026
  14. Solved: S4/HANA Readiness Check Issue, SAP Community Q&A, 2025
  15. Solved: SAP Readiness upload failed for Custom Code Analyzer, SAP Community Q&A
  16. 2968380 - SAP Readiness Check for SAP S/4HANA - troubleshooting guide, SAP Knowledge Base
  17. 3425520 - SAP Readiness Check: App Availability Error, SAP Knowledge Base
  18. 3137140 - SAP Readiness Check for SAP S/4HANA Analysis on SAP Backend shows authorization issues for sub-items in section 'Integration', SAP Knowledge Base
  19. 3396086 - Custom Code Analysis ZIP from non-prod System cannot be uploaded into Readiness Check Analysis of prod System, SAP Knowledge Base
  20. 3415179 - The uploaded file is not valid - SAP Readiness Check, SAP Knowledge Base
  21. 2896138 - S/4 HANA Readiness check in status "In Preparation", SAP Knowledge Base
  22. 3440226 - Readiness Check upload showing error for Financial Data Quality Asset Accounting and Material Ledger, SAP Knowledge Base

More on Strategy & transition paths

How this guide is made: researched with AI-assisted search across SAP documentation and practitioner sources, with every fact linked to its source. Found an error or have field experience to add? Tell us.