SAP S/4HANA upgrade steps: a runbook for manufacturers
sap s4 hana upgrade steps
Also searched as
- sap s/4 hana upgrade steps
- sap s4 hana upgrade guide
- ecc to s/4hana conversion steps SUM
Short answer
An S/4HANA move runs in phases: assess with the readiness check and simplification items, clean up and adapt custom code, plan the stack in Maintenance Planner, run the technical conversion or upgrade with SUM in a sandbox, test business processes, rehearse the cutover and go live. Most of the effort is in custom code, data and testing, not the tool.
Applies to: SAP ECC 6.0 to S/4HANA system conversion, and upgrades between S/4HANA releases on-premise
The upgrade runbook
- 1Decide the path: system conversion (brownfield) keeps your data and customizing, new implementation (greenfield) starts clean, and selective data transition sits between. An upgrade from one S/4HANA release to the next uses the same SUM tool with a smaller scope.
- 2Run the SAP Readiness Check for the source system and the Simplification Item Check. These list the simplification items that apply to you, such as business partner, material number length, inventory and finance changes.
- 3Analyse custom code with the ABAP Test Cockpit (ATC) checks for S/4HANA and the custom code migration tooling. Remove unused code first with usage statistics, then fix what remains.
- 4Plan the target in SAP Maintenance Planner: define the target release, add-ons and languages, and generate the stack file (stack XML) that SUM consumes. Confirm hardware, HANA database version and operating system.
- 5Prepare a sandbox copy of production. Run pre-conversion activities such as customer-vendor integration to business partner, data cleanup, and reduction of data volume through archiving.
- 6Run SUM (Software Update Manager) with DMO, including the database migration to HANA when moving from another database. Resolve the findings and re-run on a fresh copy until the downtime is acceptable.
- 7Execute post-conversion tasks, adapt Fiori and authorizations, then run test cycles on business processes and interfaces. Rehearse cutover, cut over production, and monitor the hypercare period.
What drives effort
The technical conversion is a small part of the project. The larger work is the business and data side: converting customers and vendors to business partners, changes to inventory management (material document tables), the universal journal in finance, material ledger activation for valuation, and the new data model for MRP. Each of these is a simplification item with pre- and post-conversion tasks.
Custom code is the typical schedule risk. Manufacturers often carry years of enhancements into pricing, production confirmations and quality processes. Use ATC findings to separate what must be fixed, what can be retired and what the new standard replaces.
Manufacturing specifics to check early
Check the production planning functions your plants use: MRP Live replaces classic MRP run behaviour, so procedures and planning reports change. Review quality management inspection types, subcontracting and any special procurement. Shop floor interfaces to MES, scanners and label printers often depend on 18-character material numbers or old tables, so test them explicitly.
Regulated or defense manufacturers should plan validation documentation in parallel, because change control and traceability evidence is required for the conversion itself.
Dual maintenance, testing and cutover
Most projects freeze changes to the source system during the final phase, or run dual maintenance with a defined transport process until go-live. Decide this early; undisciplined changes in production during a long project are a common cause of late defects.
Test in layers: technical (jobs, interfaces, authorizations), functional (order to cash, procure to pay, plan to produce, record to report) and performance (MRP runs, month-end close). Automate regression tests where possible. For cutover, rehearse at least twice, time each step, and agree a rollback point.
Tools: SAP Readiness Check, Simplification Item Check, ATC (S/4HANA readiness checks), Maintenance Planner, SUM (with DMO)
Typical sequence: Assess > Prepare > Convert in sandbox > Test > Rehearse cutover > Go live > Hypercare
Timeline and support dates
SAP has announced end of mainstream maintenance for ECC 6.0 at the end of 2027, with an extended option to 2030 at extra cost. Check SAP's current published dates before building a business case. Typical project durations are measured in many months to a couple of years depending on landscape size, so the plan should start from the date you must be live and work backward.
Try it here, free
SAP S/4HANA Conversion and Migration Tools Reference
A lookup of the SAP tools used at each phase of an S/4HANA conversion or migration, what each does and when to use it.
Common pitfalls
- !Starting with the tool and discovering simplification items late.
- !Carrying all custom code over without usage analysis.
- !Testing only transactions and not integrations to MES, EDI and label printers.
- !Running a single rehearsal and trusting the downtime estimate.
- !Ignoring data quality before the business partner conversion.
How an ERP-grounded AI assistant handles this
Several upgrade tasks are reading tasks: finding which custom objects touch changed tables, which reports use old stock tables, and which interfaces hard-code field lengths. A grounded assistant working against your own system and code can produce these lists and suggest fixes for review. For regulated manufacturers the model can run on-prem so source code and data stay in-house. The upgrade itself remains an SAP Basis and functional project.
Frequently asked questions
What are the main steps in an SAP S/4HANA upgrade?
Assess with the readiness check, clean up and adapt custom code, plan the target in Maintenance Planner, run the conversion with SUM in a sandbox, test the business processes, rehearse cutover and go live. Data and custom code drive most of the effort.
What is SUM in SAP?
Software Update Manager is the tool that performs upgrades and system conversions. With the Database Migration Option it can also migrate the database to HANA in the same run. It consumes the stack file generated by Maintenance Planner.
Is an upgrade from ECC to S/4HANA a normal upgrade?
No, it is a system conversion with data model changes, such as business partner and the universal journal, so it needs business preparation as well as a technical run. Moving between S/4HANA releases is closer to a normal upgrade.
How long does an S/4HANA conversion take?
It depends on landscape size, custom code and data quality. Small, clean systems may take months; large manufacturing landscapes with many interfaces commonly take a year or more. Use a sandbox run to calibrate before committing a date.
Related
ERP Upgrade or AI First? A CIO Decision Framework
In most cases, add a grounded AI layer on top of your current ERP first, because it proves value in weeks and shows exactly what an upgrade would need to fix. Reserve a full ERP replacement for cases where the platform itself is end of support, unsupported, or structurally blocking the business, not simply because it feels dated.
How-toTeamcenter to SAP BOM transfer: why releases fail and how to fix them
Most failed Teamcenter to SAP transfers come from order and master data problems: the BOM was sent before its materials existed, a unit of measure or plant is missing, the SAP change number or status does not allow the update, or a mapping produced a value SAP rejects. Read the SAP-side message first (IDoc status, application log, BAPI return), then correct the Teamcenter data or the mapping.
How-toHow to create a material in SAP MM (MM01) and mass-change it with MM17
Run MM01, enter the material number or let it be assigned, pick the industry sector and material type, select the views and organizational levels, then maintain each view and save. MM17 mass-changes selected material master fields. In S/4HANA the material number can be up to 40 characters.
AdvancedPlanning an AX 2012 to Dynamics 365 Finance and Operations upgrade
Moving from AX 2012 to D365 F&SCM is a platform change, not a version bump: X++ customizations go through a code upgrade to the new extension/overlayering model, and data moves through a structured data migration, both coordinated as an Upgrade project in Lifecycle Services (LCS). Plan it as a project with its own testing cycle, not a routine patch.
Error fixSAP M7 021: Deficit of SL Stock Quantity
M7 021 fires during a goods issue, delivery, or confirmation when SAP checks the unrestricted-use (SL) stock for the exact plant, storage location and batch combination and finds less than what you are trying to post out. Fix the entry (batch, storage location, quantity) first; only enable negative stock or downgrade the message to a warning if the business genuinely needs to post ahead of a receipt.
Error fixSAP IDoc Status 51: Application Document Not Posted
Status 51 tells you the IDoc reached the application layer and failed to post, but the status text itself is not the error - the real cause sits in the status record's long text or the linked application log. Fix the underlying data or configuration, then reprocess the IDoc through BD87 rather than editing the status.
AI for ERPGet AI Value From SAP ECC Now, and Use It to De-Risk the Move to S/4HANA
SAP ECC 6.0 mainstream maintenance ends in 2027. Add AI value on ECC now, using its existing BAPIs and IDocs, and use it to de-risk the S/4HANA migration.
AI for ERPAI for SAP S/4HANA, Running On-Prem or in Your Private Cloud
Run AI on SAP S/4HANA without sending ERP data to a public API. On-prem and private-cloud architecture, CDS views, OData, and honest deployment trade-offs.
Stuck on SAP ECC to S/4HANA?
Talk to engineers who work inside SAP ECC to S/4HANA every week, and who build private AI that answers these questions from your own ERP data.
Keep exploring
Free tools
- SAP S/4HANA Conversion and Migration Tools ReferenceA lookup of the SAP tools used at each phase of an S/4HANA conversion or migration, what each does and when to use it.
- S/4HANA Conversion Downtime Window CalculatorEstimate the business downtime of an ECC to S/4HANA conversion and check whether it fits your cutover weekend.
- SAP Greenfield vs Brownfield AssessmentTen questions that point toward brownfield conversion, selective data transition or greenfield re-implementation for your S/4HANA move.
ERP fixes and how-tos
- SAP ECC 2027: what mid-size manufacturers should actually doSAP ECC mainstream support ends in 2027. Practical options for mid-size manufacturers: extended maintenance, S/4HANA migration paths, and how to decide with limited time.
- SAP PO Upgrade: Updating Process Orchestration 7.5 and Planning the Move to Integration SuiteHow to approach an SAP Process Orchestration upgrade: 7.5 support packages with SUM, PAM checks, testing, and the path to SAP Integration Suite or staying on-prem.
- SAP S/4HANA API Guide: Business Hub, OData, Public Cloud and Business PartnerA guide to SAP S/4HANA APIs: the Business Accelerator Hub, A2X OData, the Business Partner API, public cloud communication arrangements, PI/PO and Digital Manufacturing.
Runs with your ERP
- Delfoi Planner with SAP S/4HANA: finite scheduling for production ordersHow Delfoi Planner adds finite scheduling and a drag-and-drop Gantt to SAP S/4HANA, which data flows, how to set it up, what breaks and where private AI helps.
- SEEBURGER Business Integration Suite and SAP S/4HANAHow SEEBURGER's SAP-certified S/4HANA connector handles EDI, e-invoicing, MFT and APIs, including moving ECC EDI during migration. Setup, pitfalls, AI.
- Prometheus Planning & Scheduling with SAP Plant MaintenanceHow Prometheus Planning and Scheduling works with SAP Plant Maintenance work orders on S/4HANA and ECC: data flows, setup, pitfalls and a private AI layer.
Guides
- SAP to Infor LN Migration Assessment FrameworkEvaluate migrating from SAP ECC or S/4HANA to Infor LN. Assessment framework covering costs, risks, functional gaps, and realistic timelines.
- Baan to SAP Migration vs Infor LN: Baan ERP vs SAP S/4HANABaan to SAP migration versus Infor LN: compare functional fit, the 12-18 vs 18-30 month timelines, customization rework and cost for Baan ERP manufacturers.
- AI-Powered Code Review for ERP CustomizationsReview ERP customizations with AI agents detecting code quality issues, upgrade risks, security vulnerabilities, and performance problems in custom ERP code.
AI on your ERP
- Get AI Value From SAP ECC Now, and Use It to De-Risk the Move to S/4HANASAP ECC 6.0 mainstream maintenance ends in 2027. Add AI value on ECC now, using its existing BAPIs and IDocs, and use it to de-risk the S/4HANA migration.
- AI for SAP Plant Maintenance: Notifications, Work Orders, and Predictive SignalsAI grounded on SAP PM data that triages notifications, drafts work orders, standardizes failure codes, and flags predictive maintenance signals, on-prem.
Integrations
- How to connect Power BI to SAP S/4HANAConnect Power BI to SAP S/4HANA using the HANA connector, OData or a warehouse, set up the on-prem gateway, and build manufacturing dashboards with AI Q&A.
- How to use ChatGPT with SAP ECC 6.0Using ChatGPT with SAP ECC 6.0: custom GPT actions, exports versus live access, an OData or MCP bridge, enterprise data controls, and when a private model is safer.