The cheapest time to find a problem in an S/4HANA conversion is before you have committed to a plan, a partner and a date. SAP provides a set of free or low-cost tools that look at your actual ECC system and report what will change, what will break and what you need to decide. Used well, they turn a vague worry about "the conversion" into a short, owned list of findings.
This guide explains how to run that review, what the tools actually tell you, how to read the simplification items that matter most, and how to turn the results into a plan. It is written for SAP programme managers, IT leaders and finance and operations owners who have to sign off the plan, as well as for the technical teams who run the tools.
- 1ScopePick the source system, the target release and the people involved.
- 2CollectRun the data collector and the simplification item check in production.
- 3Review itemsWalk through relevant simplification items with the business owners.
- 4Check code and add-onsAnalyse custom code and confirm add-on support.
- 5Assess dataReview data volume, quality, business partner readiness and sizing.
- 6Decide and planTurn findings into a register, a route and a plan.
What a readiness review is, and what it is not
A readiness review answers one question: how far is this system from being convertible, and what stands in the way? It is based on facts taken from your system and checked against SAP's own catalogue of changes between ECC and S/4HANA. It is not a project plan, a business case or a design. It gives you the inputs to those.
It helps to separate three layers of change, because each has a different owner and a different kind of work.
Technical prerequisites: things the conversion tool or the target system requires, such as Unicode, a single ABAP stack, a supported release and database, and compatible add-ons.
Functional simplifications: places where S/4HANA works differently from ECC, such as the business partner model, the finance data model or how certain sales and inventory processes behave. SAP calls these simplification items.
Your own objects: custom code, enhancements, interfaces and reports that touch the areas SAP changed.
SAP's own guidance observes that most simplification items are technical and need little fit-to-standard work, while custom code still needs review. That is a reassuring starting point, but it should not be read as "nothing to do". A small number of items usually carry most of the business effort, and the review is how you find them.
The review is also not a one-time event. A first pass early in planning tells you whether a conversion is realistic. A second pass after cleanup shows how much was removed. A third pass shortly before the technical conversion catches anything that changed in between. Plan for all three.
The tools SAP provides
There are several tools, and they overlap in ways that confuse people. This table shows what each one does and where its result is used.
| Tool | What it does | Where you use the result |
|---|---|---|
| Simplification Item Catalog | SAP's central source for simplification items. Each item describes the business impact, the source and target releases, and the checks that decide whether it applies to you. | Reference for functional consultants and business owners; feeds the checks below. |
| Simplification Item Check | Runs the relevancy and consistency checks from the catalogue against your system. Delivered through SAP Note 2399707 and run through report /SDF/RC_START_CHECK. Also triggered by Readiness Check and by the Software Update Manager. | Tells you which items apply and what must be fixed before conversion. |
| SAP Readiness Check for SAP S/4HANA | A dashboard that brings the simplification item check and other analyses together in one place. It does not run the consistency checks itself. | Your first overview and the basis for early planning discussions. |
| Maintenance Planner | SAP-hosted tool that checks add-on and product compatibility with the target release and produces the stack file used by the Software Update Manager. | Add-on decisions and the technical conversion run. |
| ABAP Test Cockpit (ATC) with S/4HANA readiness checks | Static code checks of your custom code against the simplification database. | Custom code scope and fix lists. |
| Custom Code Migration app (SAP Fiori) | Central analysis of custom code, combined with usage data to separate used from unused code. | Scope reduction and the remediation backlog. |
| Data volume analysis (TAANA and related tools) | Shows which tables are large and which data can be archived or deleted. | Sizing, conversion runtime and archiving plan. |
The Simplification Item Catalog is described by SAP as the single source of truth for simplification items. The Simplification Item Check is the engine that uses it. SAP Readiness Check is the readable summary. If you remember one relationship, remember that: catalogue, check, dashboard.
Start with SAP Readiness Check for the overview, then use the other tools for depth. Do not try to read the whole simplification catalogue. It is a reference source, not a reading list.
Running SAP Readiness Check, step by step
SAP Readiness Check for SAP S/4HANA works by collecting data from your ECC system, packaging it into a file, and uploading that file to an SAP-hosted analysis. The following sequence comes from SAP's community documentation of the tool. Check the current version of the documentation before you start, because tool versions and prerequisite notes change.
1. Prepare the system
Implement the prerequisite SAP Notes. SAP Note 2913617 is the main landing note for the current version of the tool and sets up the data collector framework. Related notes cover the simplification item content (2758146), the check framework (2399707), the system information file used for add-on and business function analysis (2287046) and data volume preparation (1159758). The people who run the collector need the right authorisations in the source system, which your security team should provide before the day you plan to run it.
2. Run the data collector in production
Execute the data collector report, RC_COLLECT_ANALYSIS_DATA, in the productive client of each ECC system. The tool offers standard and expert modes. Run it once per system. Use production, because only production holds real usage, real volumes and real data quality.
3. Upload and choose the target release
Download the resulting ZIP file and upload it to create the analysis. The upload is rejected if the file was not produced by the data collector. You choose the S/4HANA release you are planning to move to, so the analysis is tied to a defined target. Later runs for the same system, client and target version can update the same analysis, which is how you track progress.
4. Share the analysis
The analysis is visible to all S-users under the same customer number. To share it with colleagues or a partner outside that group, grant access by email address in the tool's settings. Agree with your partner how the file will be shared and who can see it, as it contains information about your system.
5. Review the sections
The dashboard covers several areas: simplification items grouped by line of business, add-ons and active business functions, custom code, BW extractors, recommended SAP Fiori apps, integration, data volume management and sizing. Some checks, such as business partner readiness and customer vendor integration, are client-dependent. Work through them in a workshop with the owners present rather than reading them alone.
The analysis reflects the system on the day you collected data. If your landscape is changing, for example if a support package is imported or a large custom project goes live, rerun the collector. Planning on a stale analysis is a common reason for surprises later.
Reading the simplification items
Relevancy and consistency
Each simplification item goes through two checks. The relevancy check decides whether the item applies to you, based on your source release, your target release and conditions such as whether you actually use the affected function. The consistency check decides what you have to fix before conversion to reach a consistent state. An item can be relevant with no consistency problems, in which case the business just needs to understand the change. It can also be relevant with a blocking consistency error, which you must fix first.
Triage by impact, not by count
The number of relevant items is not a measure of effort. A long list of technical items that need no action can take an afternoon. A single item that changes how your finance team closes the books can take months of design, testing and training. Sort the list into three groups: items that need only awareness, items that need a technical fix, and items that need a business decision.
Areas that commonly matter
The areas below tend to appear in conversion projects. They are examples to help you ask the right questions. Your own result comes from the catalogue and the checks, so treat this table as a prompt, not a list of what you will find.
| Area | What typically changes | Question to ask | Reviewer |
|---|---|---|---|
| Business partner | Customers and vendors are maintained as business partners. SAP states that systems without Customer Vendor Integration are declined in the pre-checks. | Is CVI active, and is customer and vendor data clean enough to synchronise? | Master data owner, IT |
| Finance data model | Financial accounting and controlling data move to a new data model after conversion, and finance needs an additional conversion step. | Which reports, interfaces and reconciliations rely on the old tables? | Finance lead, ABAP lead |
| Inventory and material valuation | The inventory data model changes, and valuation moves to the Material Ledger. | Which custom code reads inventory documents or valuation tables directly? | Supply chain, finance, ABAP lead |
| Material requirements planning | Planning logic and execution change in S/4HANA. | Do we rely on custom planning reports or enhancements? | Planning lead |
| Credit management and sales functions | Some sales and distribution functions, such as credit management and rebates, are replaced by newer solutions. | Which of these do we use, and who owns the replacement design? | Sales operations, finance |
| Output and forms | Output management changes, which can affect forms and print programs. | How many custom forms and output types do we run? | Business process owners, ABAP lead |
| User interface | SAP Fiori becomes the main user interface. | Which roles need Fiori apps, and which GUI transactions remain? | Security, business owners |
| Material number length | S/4HANA supports a longer material number field. You choose whether to use it. | Do any interfaces or external systems depend on the current length? | Integration lead |
Give each relevant item a one-line decision written in business language: "accept as is", "change process", "fix code", "retire function". Items written only in SAP terms get skipped by business owners and resurface at test time.
Custom code, add-ons and interfaces
Custom code
Custom code is usually the largest variable in the plan. SAP's documented process has a preparation phase before conversion and a realization phase after it. In preparation, you collect usage data in production for as long as you can, ideally at least a year, so you can separate used from unused code. You set up the ABAP Test Cockpit with remote code analysis on one central check system, implement SAP Note 2436688 for the S/4HANA readiness checks, download the Simplification Database content following SAP Note 2241080 and install it with transaction SYCM. You then run the readiness check variant, S4HANA_READINESS_REMOTE, which needs a central check system on SAP_BASIS 7.52. Alternatively you can use the Custom Code Migration app, which is available from ABAP platform 1809 on premise and in the SAP BTP ABAP environment.
After the conversion, in the realization phase, you rerun the checks, adjust modifications with SPDD, SPAU and SPAU_ENH, fix findings, test the business processes and tune performance, for example with the SQL Monitor. Our companion guide on cleaning up custom code before S/4HANA goes into the first half of this process in detail.
Add-ons and third-party products
Add-ons are a classic hidden blocker. The Maintenance Planner checks whether each add-on is compatible with the target release. It marks third-party add-ons with unknown status for you to confirm with the vendor, and it generates the stack file that the Software Update Manager uses if all add-ons are compatible. An add-on that you no longer need must be uninstalled as part of the conversion, and the vendor has to supply the uninstaller. Without one, the add-on can block the conversion. Start the vendor conversation early, because vendor answers can take weeks.
Interfaces and integration
SAP Readiness Check includes an integration section that counts interfaces and IDocs. Treat that as a starting point. Your own interface inventory, covering middleware, file transfers, APIs, and reports that external parties receive, is the real source. For each interface, record what it reads and writes, which tables or functions it touches, who owns the other end, and whether the other end will change at the same time.
Data, sizing and technical prerequisites
Technical prerequisites
SAP's documentation lists the conditions a system conversion starts from: ECC 6.0 at a supported enhancement package level, on any database or on SAP HANA, with Unicode, and as an ABAP single-stack system. A dual-stack system must be split before conversion. If your system is not yet Unicode, that is a separate project to complete first. Check these on day one, because they decide whether you can start at all.
Data volume and archiving
A smaller database converts faster, costs less to size and carries less to test. The data volume analysis shows which tables are largest and which data is eligible for archiving or deletion. Archiving old data before conversion shortens runtime and reduces memory requirements on the target database, but it needs business and compliance agreement on what can go. Start early, because archiving projects need functional involvement and several test cycles of their own.
Business partner and master data
The business partner approach is mandatory in S/4HANA on-premise. Preparation includes cleaning customer and vendor data, confirming Customer Vendor Integration is configured, synchronising the data with the synchronisation cockpit, and converting. SAP Note 2265093 and its attached conversion document are the main reference. Master data cleansing needs business owners to decide which duplicates to merge, so it belongs on the critical path.
Sizing
SAP Readiness Check includes a sizing section, and the author of SAP's FAQ notes that sizing depends on the conversion scenario. Use it as an early estimate for infrastructure planning and discuss it with your hosting provider or hyperscaler. Revisit the numbers after archiving, because the target database size can change significantly.
A worked example (illustrative)
The following is invented to show what a findings register looks like. The company, the findings and the ratings are not real. They show the structure you want: each finding has a rating, an owner, a decision and a next action.
The situation. A manufacturer with one ECC 6.0 system has run SAP Readiness Check and the ATC checks. The review workshop has taken place with finance, supply chain, master data and IT in the room. The programme manager records each finding in a single register and rates it as red (blocks the conversion or needs major work), amber (needs work but is manageable) or green (awareness only).
| # | Finding | Rating | Owner | Decision and next action |
|---|---|---|---|---|
| 1 | Customer Vendor Integration not yet active; duplicate vendor records known | Red | Master data owner | Start CVI setup and duplicate cleanup now; target completion before first test conversion. |
| 2 | Third-party add-on with unknown status for the target release | Red | IT manager | Ask the vendor in writing for a supported path and an uninstaller; decide on replacement if none exists. |
| 3 | Large estate of custom finance reports reading old tables directly | Amber | Finance lead with ABAP lead | Run usage analysis; retire unused reports; adapt or rebuild the rest. |
| 4 | Custom sales order enhancements flagged by ATC | Amber | ABAP lead | Triage after usage data; fix used objects in the remediation backlog. |
| 5 | Credit management in use, with custom checks | Amber | Sales operations and finance | Design the replacement function and its test cases. |
| 6 | Large tables eligible for archiving | Amber | IT and finance | Agree retention rules; run archiving cycles before the first test conversion. |
| 7 | Several output types and forms need review | Amber | Business process owners | List forms in use; retire unused ones; plan rework for the rest. |
| 8 | Technical simplification items needing no action | Green | Programme manager | Record for awareness; share summary with the business. |
The result. Two red findings go to the top of the plan because they can delay everything: business partner readiness and the third-party add-on. The amber items become workstreams with owners and dates. The register is reviewed every two weeks, the readiness check is rerun after cleanup, and the route and timeline recommendation is written from the register rather than from opinion.
What the example shows. The red items were not the biggest in effort. They were the ones with long lead times that someone else controlled: a vendor and a master data clean-up. Readiness work is partly about finding the things with the longest lead times and starting them first.
From register to plan: who does what
A register only helps if someone runs it. The table below sets out a workable division of roles for the review. Adjust it to your own organisation, but keep one rule: every row has exactly one accountable person.
| Role | Accountable for | Typical tasks |
|---|---|---|
| Programme manager | The findings register and the plan | Chairs the review workshops, tracks ratings, reruns the checks, reports to the sponsor. |
| Basis lead | Data collection and technical prerequisites | Implements the prerequisite notes, runs the collector, checks Unicode and stack, supports sizing. |
| ABAP lead | Custom code analysis | Sets up usage monitoring and ATC checks, produces the retire, fix and rebuild lists. |
| Functional leads (finance, supply chain, sales) | Simplification item decisions | Read the relevant items, write the business decision, own the test cases. |
| Master data owner | Business partner and data quality | Runs the cleansing, decides on duplicates, owns the synchronisation. |
| Integration lead | Interfaces and add-ons | Maintains the interface inventory, chases vendors, owns the add-on decisions. |
| Executive sponsor | Decisions that cross teams | Settles priority conflicts and approves the recommended route. |
Turn the register into a plan by grouping findings into workstreams and ordering them by lead time rather than by size. Anything that depends on another company, such as a vendor reply or an archiving approval from compliance, starts first. Anything that needs the business to clear time in a calendar, such as workshops and test cycles, is booked early. Anything that only needs developer hours comes last, because it is the easiest to schedule.
Finally, agree how often the review repeats. A sensible rhythm is a full run at the start, a rerun after the cleanup phase, and a final run shortly before the first full test conversion. Between runs, the register is reviewed regularly and every change in scope is recorded with a date and a reason. That record becomes the evidence your sponsor needs when someone asks why the plan changed.
Pitfalls to avoid
Reading the dashboard without the business
A readiness dashboard that only IT has seen is a technical report. The value comes when finance, supply chain and sales owners read the relevant items and say what they mean in practice.
Treating "relevant" as "problem"
Many relevant items need nothing more than awareness. Counting them creates panic. Rating each item by action needed gives the real picture.
Running it only on a test system
A copy of production that is months old, or a system with partial data, will give misleading usage, volume and quality results. Run the data collection in production.
Forgetting that the target release matters
Simplification items, add-on support and tool behaviour depend on the target release you select. Confirm the target with your SAP account team and keep it consistent between runs, or the results are not comparable.
Treating the review as the end
The review sets the scope. It does not fix anything. The risk is that the report is delivered, admired and filed. Put the register into the project plan with dates the same week.
Tool names, report names and SAP Notes change between releases. The notes we cite are those described in SAP's community documentation at the time of writing. Always confirm the current note numbers on SAP's support site before you act on them.
Readiness checklist
- Target S/4HANA release agreed, and the same release used in every run.
- System is ECC 6.0 at a supported level, Unicode and ABAP single stack, or a plan exists to get there.
- Prerequisite SAP Notes for Readiness Check implemented, and authorisations granted.
- Data collector run in the productive client of each system, with the ZIP uploaded and shared with the right people.
- Simplification items reviewed in a workshop with business owners, each with a one-line decision.
- Usage data collection started for custom code, with the period and tool recorded.
- ATC readiness checks run with up-to-date Simplification Database content.
- Every add-on and third-party product checked in the Maintenance Planner, with vendor confirmations on file.
- Customer Vendor Integration status confirmed and data cleansing started.
- Data volume analysis done, with an archiving plan and owner.
- Interface inventory complete, with owners on both ends.
- Findings register created, rated and put into the project plan.
How Steady Rabbit can help
Our SAP team runs readiness reviews as a short, fixed first stage. We collect the data, run the checks, review the findings with your business owners and give you a written register with ratings, owners and next actions. Steady Rabbit is India-based, has delivered SAP work since 2016, and has about 60 engineers, with team leads who have 7 to 16 or more years of SAP delivery and certifications in ABAP Cloud and SAP BTP. We work directly with enterprises, and inside SAP partners' programmes as a subcontract team.
Book a readiness review S/4HANA Migration ABAP Code Modernization Basis and Support Services For SAP partners
FAQs
What is SAP Readiness Check for SAP S/4HANA?
It is an SAP-hosted dashboard that analyses data collected from your ECC system and shows simplification items, add-ons, custom code, data volume, integration, sizing and other areas relevant to a move to S/4HANA. It presents results from the Simplification Item Check alongside other analyses.
What is a simplification item?
It is an entry in SAP's Simplification Item Catalog that describes a change between ECC and S/4HANA, with its business impact, the releases it applies to and the checks that decide whether it affects you. Items include technical changes and functional changes.
Is the readiness check free?
SAP has described it as free of charge for customers with Enterprise Support. Confirm your own entitlement with SAP, because licensing terms can change.
How long does a readiness review take?
Running the collector and uploading the data takes little time. The effort is in the review: workshops with business owners, vendor enquiries about add-ons, and custom code analysis. Plan weeks rather than days, and plan to repeat it.
Do we need to run it in production?
SAP's documentation says to run the data collector in the productive client. Production holds the real usage, volumes and data quality that the analysis depends on.
What is the difference between SAP Readiness Check and the ABAP Test Cockpit checks?
Readiness Check gives a broad overview of the system, including a custom code section. ATC with the S/4HANA readiness checks analyses your custom code object by object and produces the detailed findings that developers fix. Use both.
What blocks a conversion most often?
Typical blockers are missing business partner preparation, unsupported add-ons without an uninstaller, a system that is not Unicode or not single stack, and consistency errors from simplification items. A readiness review finds all of these before you plan the cutover.
Can Steady Rabbit run this for us?
Yes. We can run the review, work through the findings with your owners and hand you the register. Contact us using the form on this page.
Sources
SAP Community: SAP Readiness Check 2.0 for SAP S/4HANA FAQ and what's new in releases. Analyses covered, prerequisite notes (2913617, 2758146, 2399707, 2287046, 1159758) and the data collector steps.
SAP Community: Simplification Item Catalog, Simplification Item Check and SAP Readiness Check for SAP S/4HANA. Relevancy and consistency checks, SAP Note 2399707, report /SDF/RC_START_CHECK and note 2502552.
SAP Community: S/4HANA system conversion, custom code adaptation process. SCMON and SUSG usage data, ATC set-up (SAP Note 2436688), Simplification Database content (SAP Note 2241080, transaction SYCM), check variant S4HANA_READINESS_REMOTE, and the Custom Code Migration app.
SAP Community: How to move to SAP S/4HANA. Prerequisites for a system conversion, the role of SAP Readiness Check and the observation that most simplification items are technical.
SAP Community: Business Partner Approach in SAP S/4HANA. Customer Vendor Integration, the pre-check behaviour and SAP Note 2265093.
SAP Community: Handling add-ons during a system conversion or upgrade to SAP S/4HANA. Maintenance Planner, stack file, third-party add-ons and uninstallers.
SAP Notes can be read on SAP's support site with an S-user. SAP products, tools and note numbers change. We checked these sources in November 2026. Confirm current details before acting.