Upgrade Path Planner

SAP ECC upgrade path planner: EHP upgrades and S/4HANA conversion

Pick the ECC release you run today (R/3 4.6C, 4.7, ECC 5.0 or ERP 6.0 at any enhancement package) and the target: a later EHP, SAP ERP, private edition, or a system conversion to S/4HANA. The planner lays out the documented SAP route (Maintenance Planner, SUM 1.x or 2.0, SPDD and SPAU, Simplification Item-Check, DMO), what changes at each level, and a risk score, effort range and regression test plan sized to your custom code, interfaces and reports.

Free, runs in your browser, no sign-in needed. Release data checked 2026-10 against 13 cited sources.

1Releases
SupportedGerman Wikipedia: ramp-up November 2011, generally available June 2012.
SupportedEnglish and German Wikipedia: 2016.
On-premises or hosted
2Landscape
What to count in SAP ECC
customizations:
Modifications to SAP objects (SPDD and SPAU candidates), Z programs, function modules, classes, user exits, BAdI implementations and enhancements. TADIR gives the Z object count.
integrations:
SAP PI/PO, SAP CRM, SRM, SCM/APO, BW, MES, WMS, tax engines, banks, e-commerce.
interfaces:
IDoc partner profiles, RFC and BAPI callers, file interfaces, EDI maps, web services in SOAMANAGER.
reports:
Z reports, ALV reports, SAPscript, Smart Forms and Adobe forms, Report Painter and Report Writer reports.
sites:
Plants or company codes that need their own validation and cutover checks.
Modules in use
Integration types
SAP ERP 6.0 EHP6SAP ERP 6.0 EHP8

Direct update with SUM 2.0: any ERP 6.0 level goes to EHP8 on NetWeaver 7.50 in one run, with the latest Support Package stack. Non-Unicode and dual-stack systems need their own steps first.

Steps
12
3 to confirm
Releases crossed
2
SAP ERP 6.0 EHP6 to EHP8
Risk
66 / 100
High
Effort
297-791 d
about 15-40 person-months
  1. 1
    PreparationDocumented

    Run the whole procedure first on a sandbox copy of production

    SAP recommends testing the installation and the activation of new functions on a sandbox system first, evaluating runtime, system behavior, dependencies and impacts, and making sure the system is free of errors before go-live. Use the sandbox run to time each SUM phase.

    Source 10
  2. 2
    PreparationDocumented

    Plan the target stack in Maintenance Planner and generate stack.xml

    Maintenance Planner is the successor of Maintenance Optimizer. System data flows from the System Landscape Directory (SLD) to LMDB in SAP Solution Manager and is uploaded to the SAP Support Portal. In Define Change it calculates the required NetWeaver release (EHP8 for SAP ERP 6.0 requires SAP NetWeaver 7.5) and generates the stack XML and download archives that SUM consumes.

    Maintenance PlannerSAP Solution Manager (LMDB)SLDSource 9Source 10
  3. 3
    PreparationVerify with vendor

    Check database, operating system and kernel against the target NetWeaver release

    The target NetWeaver release (7.40 for EHP7, 7.50 for EHP8) sets the minimum database, operating system and kernel versions. Check them in the SAP Product Availability Matrix and the NetWeaver upgrade master guide before the project plan is fixed.

    Source 10Source 9
  4. 4
    PreparationDocumented

    Update SPAM/SAINT and download the latest SUM

    Patch the SAP Support Package Manager with the latest SPAM/SAINT update before importing anything. SAP says to always use the latest version of the SUM tool and guide, so download them at the start of each test cycle, not once per project.

    SPAMSAINTSoftware Update ManagerSource 13Source 10
  5. 5
    PreparationDocumented

    If the system is dual-stack (ABAP and Java), split it first

    As of SAP Business Suite 7i2011 a dual-stack system can no longer be upgraded to a higher release; run a dual-stack split on the source system before the upgrade. The S/4HANA conversion also requires an AS ABAP-only system (SAP Notes 1686144 and 1655335 cover the split).

    Software Provisioning Manager (dual-stack split)Source 10Source 11
  6. 6
    MigrationVerify with vendor

    Non-Unicode systems: plan the Unicode conversion before the 7.50 target

    SUM offers a technical Unicode conversion inside DMO only when the target is lower than BASIS 7.50, so a non-Unicode system cannot convert during the EHP8 run. Plan a combined upgrade and Unicode conversion to a lower target first, or a separate Unicode conversion, and confirm the route in the current SUM guide. SAP Note 838402 explains the data loss risk of non-Unicode code pages.

    Software Update Manager (DMO)Source 8Source 10
  7. 7
    PreparationDocumented

    Check add-on and industry solution compatibility with the target

    Check every installed add-on against the target release before planning (SAP Note 1820906 is referenced for add-on compatibility in the EHP7 master guide). Maintenance Planner blocks the plan when an add-on, active business function or industry solution has no valid path.

    Source 10Source 11
  8. 8
    UpgradeDocumentedlands on SAP ERP 6.0 EHP8

    Run SUM 2.0 to EHP8 on SAP NetWeaver 7.50

    EHP8 for SAP ERP 6.0 requires SAP NetWeaver 7.5, and SUM 2.0 is the SUM line for ABAP single stacks with a target on BASIS 7.50 or higher. Install the EHP with the latest Support Package stack in the same run.

    Software Update Manager 2.0stack.xmlSource 8Source 9Source 10
  9. 9
    UpgradeDocumented

    Adjust modified dictionary objects in SPDD

    SUM stops for the SPDD modification adjustment in the development system only, before the ABAP Dictionary is activated. Do not activate objects during SPDD. Adjustments are recorded in transport requests that SUM reuses for the quality and production runs.

    SPDDSource 12Source 13
  10. 10
    UpgradeDocumented

    Adjust modified repository objects in SPAU

    Non-dictionary repository objects (programs, function modules, screens and implemented SAP Notes) are adjusted in SPAU towards the end of the upgrade during downtime, again in the development system only. Manually implemented SAP Notes show up here.

    SPAUSPAU_ENHSource 12Source 13
  11. 11
    ConversionDocumented

    Decide which business functions to switch on in SFW5

    Installing an enhancement package changes nothing in business processes or screens until a business function is activated in the Switch Framework (SFW5). Activate only what is required: installing an EHP is irreversible and most business functions cannot be deactivated. Each activated function goes into the test scope; SFW5 gives access to the Impact Analyzer and SAP test catalogs.

    SFW5Source 10Source 12
  12. 12
    CutoverVerify with vendor

    Rehearse, freeze and cut over

    Run the production procedure at least once on a full-size copy to measure downtime, agree the freeze window for transports and master data, close or complete open business steps as your test cycle showed necessary, then run SUM, apply the SPDD and SPAU transports, and reconcile key balances before users return.

Free, optional. Reopen it on any device.
Export plan:

This is a planning model. Before you commit a budget or a date, have an engineer check the path, the effort drivers and the test scope.

How to use the SAP ECC upgrade planner

  1. 1

    Pick your releases

    Choose the current release from System > Status (SAP_APPL and SAP_BASIS levels) and the target: EHP6, EHP7 or EHP8, SAP ERP private edition, or S/4HANA 2023 or 2025.

  2. 2

    Describe your landscape

    Enter counts for modifications and Z objects, integrations, IDoc and file interfaces, custom reports and forms, database size, users and plants, then tick the modules and integration types you use.

  3. 3

    Read the path and the drivers

    Review each step with its SAP source, the SAP Notes it names, the changes at every level you cross, and the drivers behind the risk score and effort range.

  4. 4

    Export the test plan

    Download the regression plan as Excel, Word, PDF or CSV. Tests become critical where the path changes that area, for example Finance data migration or the Business Partner on S/4HANA targets.

  5. 5

    Save or get it reviewed

    Save the plan to your Netray account to reopen later, or send it to an engineer for a written review.

Questions

What is the latest version of SAP ECC?

SAP ERP 6.0 with enhancement package 8 (EHP8), released in 2016. EHP8 is the most recent enhancement package and requires SAP NetWeaver 7.5. SAP's successor product is SAP S/4HANA.

When does SAP ECC support end?

SAP provides mainstream maintenance for SAP Business Suite 7 core applications, including SAP ERP 6.0, until the end of 2027, for the latest three enhancement packages (EHP6, EHP7 and EHP8). Mainstream maintenance for releases before EHP6 ended on 31 December 2025. Optional extended maintenance runs from 2028 to the end of 2030 at two percentage points on the maintenance basis; after that, or without it, customer-specific maintenance applies. For systems moved to SAP ERP, private edition, the transition option covers 2031 to 2033, and SAP now says subscriptions may run until the end of 2035.

Can we upgrade from EHP4 or EHP5 directly to EHP8?

Yes. Enhancement packages are cumulative and any ERP 6.0 level can be updated to EHP8 in one SUM run, planned in Maintenance Planner, which calculates the required NetWeaver 7.5 stack. SUM 2.0 is the SUM line for targets on BASIS 7.50 and higher. Install the EHP together with the latest Support Package stack, split a dual-stack system first, and confirm the calculated path in Maintenance Planner.

Our system is not Unicode. Can it go to EHP8 or S/4HANA?

Not in one step. SUM offers a technical Unicode conversion inside DMO only when the target is below BASIS 7.50, and EHP8 needs NetWeaver 7.5. The S/4HANA conversion requires a Unicode source; SAP describes a two-step approach: a combined upgrade and Unicode conversion to a supported start release, then the conversion.

What are SPDD and SPAU, and why do they drive the timeline?

SPDD is the modification adjustment for ABAP Dictionary objects; SUM stops for it in the development system before the dictionary is activated. SPAU adjusts other repository objects and implemented SAP Notes towards the end of the upgrade, during downtime. Both are done once in development and transported to quality and production, so the number of modifications sets much of the technical effort and the test scope.

Is a system conversion to S/4HANA an upgrade?

SAP calls it a conversion: the product is exchanged from SAP ECC to SAP S/4HANA in the same system. It needs SAP Readiness Check, Maintenance Planner, the Simplification Item-Check, custom code analysis, and then SUM 2.0, which migrates the database to SAP HANA if needed, installs S/4HANA and converts the data. Business Partner, Finance data migration and the simplified SD and inventory data models are part of the scope.

How should we test an SAP ECC upgrade, and what should we automate?

Run regression on a full-size copy: platform tests (logon, roles, background jobs, dumps, Z programs and enhancements, forms), the business processes per module you use, and every IDoc, RFC and file interface with saved production data. Support Package stacks and later EHP or S/4HANA steps repeat the same cycle, so the tests marked for automation pay back each time. SAP also offers Data Transition Validation to compare business reports before and after a conversion.

Sources

  1. SAP News: SAP S/4HANA maintenance to 2040 and choice for SAP Business Suite 7 (February 2020)
  2. SAP Support: maintenance strategy for SAP S/4HANA and SAP Business Suite 7
  3. SAPinsider: SAP details end of maintenance plans for Business Suite (2023)
  4. SAP News: RISE with SAP journey, SAP ERP private edition transition option updates (August 2025, updated October 2026)
  5. SAP News: new SAP S/4HANA release and maintenance strategy (September 2022)
  6. Wikipedia (German): SAP ERP release history
  7. Wikipedia: SAP ERP
  8. SAP Support: Software Update Manager (SUM 1.x and 2.0, DMO)
  9. SAP Help: Maintenance Planner User Guide
  10. SAP Help: Master Guide, SAP Enhancement Package 7 for SAP ERP 6.0
  11. SAP Help: Conversion Guide for SAP S/4HANA 2025
  12. SAP Learning: SAP system upgrade and SAP S/4HANA conversion
  13. SAP Learning: SAP Support Packages, SPAM, SAINT and modification adjustment

Steps marked Verify with vendor are planning inferences, not vendor statements. Effort coefficients are Netray planning assumptions and are shown in full in the Effort tab.