SAP S/4HANA Conversion and Migration Tools Reference
An S/4HANA program uses more than ten different SAP tools across assessment, preparation, conversion and data migration. This list shows each tool, its phase and where to find it.
| Tool | Phase | What it does | Where to find it |
|---|---|---|---|
SAP Readiness Check for SAP S/4HANA | Assess | Analyzes an ECC system for simplification items, custom code, add-ons, sizing and interface impact | SAP cloud service, fed by data collected from the ECC system |
Simplification Item Catalog | Assess | Lists simplifications by area with notes and required actions | SAP Help Portal and SAP Support Portal |
Simplification Item Check | Assess | Runs the catalog checks in your own system and shows relevant items and consistency errors | Report /SDF/RC_START_CHECK (see the SAP Note for your release) |
SCMON | Assess | Records which ABAP code is executed in production | Transaction SCMON |
SUSG | Assess | Aggregates ABAP call monitor data for use in custom code analysis | Transaction SUSG |
ABAP Test Cockpit (ATC) | Assess | Runs static checks, including S/4HANA readiness checks, on custom code | Transaction ATC |
Custom Code Migration app | Remediate | Analyzes custom code against a target S/4HANA system and supports quick fixes | SAP Fiori app in the S/4HANA system |
SPDD and SPAU | Convert | Adjust dictionary and repository modifications after upgrade steps | Transactions SPDD and SPAU |
Maintenance Planner | Plan | Checks add-on and product compatibility and generates the stack file for the conversion | SAP cloud service |
Software Update Manager (SUM) | Convert | Performs the technical conversion and the software update | SUM tool started on the application server |
Database Migration Option (DMO) of SUM | Convert | Combines the update with a database migration to SAP HANA in one run | SUM with DMO option |
MDS_LOAD_COCKPIT | Prepare | Synchronizes customer and vendor data to Business Partner during CVI preparation | Transaction MDS_LOAD_COCKPIT |
SAP S/4HANA Migration Cockpit | Migrate | Loads data into S/4HANA from files or a staging database using predefined migration objects | Transaction LTMC or the Migrate Your Data Fiori app, depending on release |
Migration Object Modeler | Migrate | Extends or creates migration objects for the cockpit | Transaction LTMOM |
Data archiving (SARA) | Prepare | Archives old data before conversion to cut downtime and database size | Transaction SARA |
SAP Activate | Plan | Project methodology with phases Discover, Prepare, Explore, Realize, Deploy and Run | SAP Roadmap Viewer |
Tool names and screens vary by release and by whether the project is a system conversion, a new implementation or selective data transition. Confirm with the SAP documentation for your release.
Review your tool plan and timeline
Share your approach and landscape and we will comment on tool sequencing and dry run planning.
Optional. The tool and every export work without this. No spam.
How to use this reference
Filter by phase to build the toolset for the workstream you are staffing. A Basis lead needs Maintenance Planner, SUM and DMO. A development lead needs SCMON, SUSG, ATC and the Custom Code Migration app. A data lead needs the Migration Cockpit and Migration Object Modeler. Assigning tools to named owners at the start prevents the usual mid-project discovery that nobody collected usage data.
- Start SCMON early, since it needs weeks of production data
- Run Readiness Check before committing to a scope or date
- Reserve Basis capacity for SUM dry runs on a sandbox copy
Order of use in a system conversion
A typical conversion starts with the Readiness Check and the Simplification Item Catalog, then SCMON and SUSG in production to find used code, followed by ATC checks and remediation. Maintenance Planner builds the stack file before SUM runs on sandbox, development, quality and finally production. CVI preparation and archiving run in parallel. New implementations and selective data transition replace SUM with the Migration Cockpit as the main loader.
Common mistakes
Teams run the Readiness Check once and treat it as final, although the system changes. Another common error is starting SCMON too late, which leaves custom code analysis without usage evidence and forces remediation of unused code. A third is skipping dry runs of SUM, so the real downtime is only learned at production cutover.
Frequently Asked Questions
Do I need all of these tools?
No. System conversions use SUM and the readiness tools, while new implementations rely mostly on the Migration Cockpit. Select tools by approach, then add archiving and CVI as needed.
How long should SCMON run before analysis?
Long enough to cover a full business cycle, including month end, quarter end and year end jobs. Many teams aim for at least several months so rarely used but critical code is not missed.
What is the difference between Readiness Check and the Simplification Item Check?
Readiness Check is a cloud-based analysis of data collected from your system. The Simplification Item Check runs inside the system and gives a more current, detailed result against a chosen target release.
Is LTMC still the Migration Cockpit?
In many on-premise releases yes, but newer releases move to the Migrate Your Data app. Check documentation for your target release before building runbooks around a transaction code.
If you want help interpreting Readiness Check or ATC output and sizing remediation effort, Netray can review it with you.
Related Tools
SAP S/4HANA Key Simplifications Reference
A searchable reference of the biggest ECC to S/4HANA data model and functional changes, with the action each one usually forces.
SAPSAP S/4HANA Pre-Conversion Technical Checklist
A checklist of the technical preparation items to close before running SUM on a system conversion from ECC to S/4HANA.
SAPSAP Custom Code Inventory ABAP Query Generator (TADIR)
Generates ABAP SELECT statements against TADIR that count and list custom objects by type and package for S/4HANA remediation planning.
SAPSAP HANA Largest Tables SQL Query Generator
Generates SAP HANA SQL for the biggest tables and the usual archiving suspects, to size and reduce data before migration.