SAP ECC 6.0 EHP8 Upgrade Readiness Checklist
This checklist walks an SAP ECC 6.0 system from EHP4 to EHP7 to EHP8 on SAP NetWeaver 7.50 with the Software Update Manager. It is ordered the way a Basis team actually works: plan the stack, prove the prerequisites, run SUM, adjust, test and cut over.
0 of 35 items complete
13 critical items still open - these are the highest-risk gaps.
Planning
Pre-upgrade checks
Execution with SUM
Post-upgrade
Test and cutover
Critical items are the ones that most often stop a SUM run or force a rollback. Clear all of them on the production-copy rehearsal first.
Get your EHP8 plan reviewed
Send your current component levels, add-on list and DB/OS versions and we will flag blockers before you book a sandbox run.
Optional. The tool and every export work without this. No spam.
Why EHP8 and what it changes
EHP8 is the last enhancement package for SAP ERP 6.0, and it moves the technical stack to SAP NetWeaver 7.50. SAP ended mainstream maintenance for EHP0 to EHP5 at the end of 2025, while EHP6 to EHP8 keep mainstream maintenance to the end of 2027 with optional extended maintenance after that. Staying supported on ECC therefore means EHP6 or higher, and most teams go straight to EHP8. An EHP upgrade installs new software versions but does not activate new business functions by itself; activation in SFW5 is a separate, mostly irreversible decision. The upgrade is also the moment to confirm Unicode and single-stack status, because NetWeaver 7.50 requires both.
How to use the checklist
Work through it twice: once on a sandbox or production copy, where you record real runtimes and SPDD/SPAU effort, and again for production using the transports and stack XML from the first runs. Tick items as you complete them and export the list to Excel for the project log. The critical items are the ones that most often stop SUM or cause a rollback: an unsupported add-on, a non-Unicode or dual-stack system, open update records or extraction queues, missing SPDD adjustments and an untested backup.
- Phases of an SAP upgrade in SUM: Extraction, Configuration, Checks, Preprocessing, Execution, Postprocessing
- SPDD happens before the switch so dictionary objects are not lost; SPAU follows after
- Add-ons are upgraded in the same SUM run using the stack XML and vendor packages
Add-on upgrade steps
List installed add-ons in SAINT or in System > Status. For each one, find the compatible release for NetWeaver 7.50 in the PAM or the vendor's note, and download the upgrade or exchange package. Maintenance Planner includes SAP add-ons in the stack calculation; third-party add-ons need the vendor's packages placed where SUM asks for them during Configuration. If an add-on has no compatible version, SUM stops: you then need the vendor, an uninstall option if one exists, or a different target. Finding this out in the rehearsal, not on the production weekend, is the point of the checklist.
How to check the result
After the upgrade, System > Status should show the new SAP_APPL and SAP_BASIS 750 levels. SPAU should list no open objects. SM37 should show standard jobs running again, SM59 connection tests should pass, and ST22 should be quiet. Compare ST03N response times with the baseline you took beforehand, and keep the SUM evaluation file for the next system in the landscape.
Frequently Asked Questions
How do I upgrade SAP ECC 6.0 EHP4 to EHP8?
Confirm Unicode and single-stack status, check DB/OS and add-ons in the PAM, calculate the EHP8 stack in Maintenance Planner, and run SUM with the stack XML. Adjust SPDD during the upgrade and SPAU afterwards, run SGEN, test interfaces and regression, then repeat the same stack and transports in QAS and PRD.
What are the phases of an SAP upgrade?
In SUM the roadmap steps are Extraction, Configuration, Checks, Preprocessing, Execution and Postprocessing. Most of the work, including the shadow system and SPDD, runs while the system is still up; the downtime part falls in Preprocessing and Execution. Postprocessing covers SPAU and cleanup.
Does an EHP8 upgrade activate new functionality?
No. It installs new software components, but business functions only become active when you switch them on in SFW5, and most cannot be switched off again. Plan activation as a separate change with its own testing, after the technical upgrade is stable.
Do I need to split a dual-stack system before EHP8?
Yes. NetWeaver 7.50 does not support ABAP and Java in one system for ERP, so a dual-stack system has to be split with Software Provisioning Manager before the upgrade. Do this as a separate project step and test it on a copy first.
If you want your team to ask your upgraded ECC system questions in plain English on your own servers, we can add a private AI layer once the upgrade settles.
Related Tools
SAP ECC Unicode Conversion Downtime Estimator (Before EHP8 / NetWeaver 7.50)
Estimate the technical downtime of a non-Unicode SAP ECC 6.0 system's Unicode conversion from database size, R3load throughput, parallel processes and the largest table.
SAPSAP ECC Support Package Stack (SPS) Update Checklist
A checklist for applying a support package stack to SAP ECC 6.0: decide, prepare, apply with SUM or SPAM, adjust modifications and validate.
SAPSAP ECC SM36 Standard Housekeeping Jobs Checklist
Check that every standard SAP ECC housekeeping job is scheduled with the right program and frequency, plus the common interface and application jobs.
SAPSAP ECC Obsolete Transactions and S/4HANA Replacements
A lookup table of common ECC transaction codes and the transaction or app that replaces them in S/4HANA, for training and role design.
More SAP tools
See all- SAP ECC Private AI Layer Blueprint Generator
- SAP ECC AI Assistant Sizing and Value Calculator
- SAP ECC SD User Exit Forms Reference (MV45AFZZ, RV60AFZZ, MV50AFZ1)
- SAP ECC Customer Exits (SMOD Enhancements) by Module Reference
- SAP ECC Classic BAdI Definitions Reference (MIGO, ME21N, MIRO, Deliveries, PM Orders)
- SAP ECC Background Job Tables Reference (TBTCO, TBTCP, Job Status Codes)
- SAP ECC Output Determination Tables and Codes Reference (NAST, TNAPR, NACE)
- SAP ECC Movement Type Configuration Tables Reference (T156, T156T, T157D)
- SAP ECC Stock Type and Location Transfer Movement Type Matrix
Keep exploring
Free tools
- SAP ECC Unicode Conversion Downtime Estimator (Before EHP8 / NetWeaver 7.50)Estimate the technical downtime of a non-Unicode SAP ECC 6.0 system's Unicode conversion from database size, R3load throughput, parallel processes and the largest table.
- SAP ECC EHP8 Upgrade SPDD/SPAU Adjustment Effort and Downtime SimulatorEnter SPDD and SPAU object counts, minutes per object, custom objects to retest and SUM downtime, and get adjustment hours per cycle, total effort and development outage.
- SAP ECC 6.0 Enhancement Packages and Maintenance Dates Reference (EHP1 to EHP8, 2027, 2030, 2033)Every SAP ERP 6.0 enhancement package with its NetWeaver basis, SAP_APPL release and the maintenance dates that apply: 2025, 2027, 2030 and the 2033 transition option.
ERP fixes and how-tos
- SAP S/4HANA upgrade steps: a runbook for manufacturersStep-by-step SAP S/4HANA upgrade and conversion runbook: readiness check, Maintenance Planner, custom code, SUM, testing and cutover for manufacturers.
- How to add AI to SAP ECC 6.0 on-prem without moving data to a cloudReference architecture for a private on-prem AI assistant on SAP ECC 6.0: RFC and BAPI reads, SLT replica, retrieval index, local LLM, permission mirroring.
Integrations
- 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.
- How to add AI agents to SAP ECC 6.0How to add AI agents to SAP ECC 6.0: a tool layer over BAPIs, RFC and IDocs, human approval before any posting, and an on-prem model that never leaves your network.