Preparing the system and collecting data

Readiness Check analyzes data collected in your own system. Collection is a small Basis project: implement the collectors, test them, transport them to production, run them, and upload the result. At Contoso, Sam (Basis lead) owns it with Kenji for the custom code part.

Prepare: notes and the Note Analyzer

The central note lists the SAP Notes that deliver the data collectors and their prerequisites. Because there are many, SAP provides a Note Analyzer input file for the scenario where available, used in transaction SNOTE to find missing or outdated notes. Implement in the development system first, test the collectors in non-production, and transport them to production with the normal change process. Notes and the collection report change often, so always start from the current version of the central note rather than a project document from last year. SAP Note 2968380 is the troubleshooting guide.

• Check the minimum release: the SAP S/4HANA conversion scenario analyzes SAP ERP 6.0 systems; consult the central note for supported start releases and required support packages.
• Get the right authorizations for the collection user; some checks, such as the integration analysis, need specific authorizations named in their notes.
• Plan the custom code analysis separately (next section), because it usually runs in a different system.
• Agree on data protection: the archive can be reviewed before upload, and SAP describes reviewing its content locally.

Process: running the collection in production

Collection runs in production, or a recent copy of it, because results depend on real data volumes and real transaction usage. SAP and community guides describe the collection report RC_COLLECT_ANALYSIS_DATA: you select the target SAP S/4HANA release and the checks, schedule the analysis, and the framework starts background jobs for the individual collectors, such as sizing, data volume, business process analysis and the simplification item checks. Check the job logs; a collector that fails silently leaves an empty tile on the dashboard. When the jobs finish, run the report again to download the archive.

Simplification item consistency results deserve one extra rule. The Simplification Item Check guidance from SAP says SUM always runs these checks in client 000, because only there do they cover data in all clients. Run them the same way when you want results comparable to what SUM will see.

Custom code results

The custom code view in Readiness Check shows results of the custom code analyzer (SYCM), the ABAP test cockpit (ATC) or the SAP Fiori Custom Code Migration app. For the analyzer, Kenji's team runs report SYCM_DOWNLOAD_REPOSITORY_INFO (SAP Note 2185390) in the background and downloads the file S4HMigrationRepositoryInfo.zip. The scope information that separates used from unused code is available only when the Custom Code Migration app was used. The custom code results are uploaded into the same analysis, so the dashboard combines them with everything else.

Step by step: Sam's collection run in EP1

1. Open the current version of SAP Note 2913617 and download the Note Analyzer file for the scenario where offered.
2. In ED1, check the file in SNOTE and implement every missing or outdated note; test in EQ1; transport to EP1 under change control.
3. In EP1, start RC_COLLECT_ANALYSIS_DATA in SA38 in the production business client. Choose the target release, SAP S/4HANA 2025, and the checks, then schedule the analysis.
4. Watch the jobs in SM37 until all collectors finish; open the log of any cancelled job before downloading.
5. Run the report again and download the archive. Review it locally if the data protection officer asks.
6. In SAP Cloud ALM, open the Readiness Check app, start a new analysis, name it (for example "EP1 · 2026-03 · S/4HANA 2025") and upload the archive. Processing takes a while; the dashboard appears when it finishes.
7. Add Kenji's custom code file to the same analysis.