SAP ECC 6.0 EHP8 Upgrade Effort Simulator (SPDD, SPAU and Downtime)
This simulator estimates the ABAP side of an SAP ECC 6.0 upgrade to enhancement package 8: SPDD and SPAU adjustment hours, regression retest hours, effort across rehearsal cycles and the outage of the first system. Technical runtime comes from your own SUM rehearsal; the tool adds the people work around it.
Your numbers
Planning assumption: later cycles import the SPDD/SPAU transports and retest a subset.
Your results
Minutes per object, test hours and the later-cycle share are planning assumptions to replace with your own rehearsal figures, not SAP figures.
Total ABAP effort vs SPAU objects
Sweeps SPAU objects (repository modifications incl. notes) from 100 to 3000, holding your other inputs fixed.
Want your SPAU list sized before the project starts?
Send us your modification and note counts from the current system and we will review your effort estimate and rehearsal plan.
Optional. The tool and every export work without this. No spam.
Where SPDD and SPAU fall in a SUM run
EHP8 upgrades run with Software Update Manager (SUM 1.0, since the target is NetWeaver 7.50) and a stack.xml from Maintenance Planner. The SUM roadmap steps are Extraction, Configuration, Checks, Preprocessing, Execution and Postprocessing. SPDD, the adjustment of modified dictionary objects, is requested before the new dictionary is activated. With the standard shadow approach it happens in the shadow system during Preprocessing, while the system is still up, but SUM waits until you finish, so it is on the critical path of the first cycle. In single system mode it falls into downtime. SPAU, the adjustment of modified programs, function modules and implemented notes, follows in Postprocessing. Record both in transports so SUM can import them automatically in later systems.
- SPDD: tables, data elements, domains with SAP modifications
- SPAU: programs, includes, screens, implemented SAP Notes
- SPAU_ENH: enhancement implementations to adjust
- Later systems: SUM asks for the SPDD and SPAU transports
How the estimate is calculated
SPDD hours = SPDD objects x minutes per object / 60. Manual SPAU objects = SPAU objects x (1 - automatic share); the automatic share covers notes that SPAU can reset to standard or adopt because the new support package contains them. SPAU hours = manual objects x minutes / 60. Retest hours = custom objects / 100 x test hours per 100. The first cycle is the sum. Each later cycle, a rehearsal on a copy of production or production itself, costs the later-cycle share of the first, because adjustments are imported from transports and only a subset is retested. The first system outage is SUM downtime plus SPDD hours when SPDD runs in downtime. All rates are rules of thumb used in planning, not SAP figures.
Worked example and reading the result
With 40 SPDD objects at 45 minutes, 600 SPAU objects of which 60% are handled automatically at 20 minutes per manual object, and 300 custom objects at 16 test hours per 100: SPDD is 30 hours, manual SPAU is 240 objects or 80 hours, retest is 48 hours, so the first cycle is 158 hours. Three cycles at 30% each later bring the total to about 253 hours. With SPDD in the shadow, the development outage is the 10 hour SUM downtime. The chart shows effort against SPAU volume: SPAU usually dominates in old systems with many manually implemented notes, which is why cleaning notes with SNOTE before the upgrade pays back.
Version gotchas
EHP8 for ERP 6.0 runs on AS ABAP 7.50, which supports Unicode systems only, so a non-Unicode system needs a Unicode conversion first or combined with the upgrade, a separate effort not modelled here. Check the database and operating system against the Product Availability Matrix for 7.50 before planning. Going from EHP4 straight to EHP8 is a single SUM run, but SPAU volume grows with the gap because more notes and modifications meet new code. If an S/4HANA conversion is close, compare the effort with running the readiness check and the custom code analysis instead.
Frequently Asked Questions
Can I upgrade SAP ECC 6.0 from EHP4 directly to EHP8?
Yes. Maintenance Planner calculates a target stack for EHP8 and SUM applies it in one run. Expect more SPDD and SPAU work than a smaller jump, and check that the system is Unicode, because the NetWeaver 7.50 basis under EHP8 does not support non-Unicode systems.
What are the steps of an SAP system upgrade with SUM?
Plan the target in Maintenance Planner and download the stack.xml and files. Run SUM through Extraction, Configuration, Checks, Preprocessing, Execution and Postprocessing. Adjust dictionary modifications in SPDD before activation and repository objects in SPAU afterwards, then test, transport the adjustments and repeat in the next system.
What is the difference between SPDD and SPAU?
SPDD adjusts modified ABAP Dictionary objects such as tables and data elements, and must be done before the new dictionary is activated to avoid data loss. SPAU adjusts modified repository objects such as programs, function modules and implemented SAP Notes, after the import. Both create transports for later systems.
How long does an SP upgrade take in SAP?
A support package stack update on ECC usually needs hours of technical downtime, and an EHP upgrade more, depending on database size, hardware and SUM options. The only reliable number is a rehearsal on a production copy. The ABAP adjustment and testing effort, which this tool estimates, often takes longer than the technical run.
If your developers want to ask which Z objects and modifications an upgrade touches in plain English against your own ECC repository, we can set up a private AI layer on your servers.
Related Tools
SAP ECC Extended Maintenance Cost and Runway Calculator (2027 to 2030)
Enter your maintenance base, rate and migration timeline to see the extended maintenance premium, how many extended years your project implies, and whether it runs past 2030.
Developer ToolsSAP ECC BAdI Implementation Method Code Generator (ME_PROCESS_PO_CUST, MB_MIGO_BADI, WORKORDER_UPDATE)
Pick a plant, the field that must be filled and your message class, and get ready-to-paste method code for three common ECC classic BAdIs, with the SE19 steps.
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.
SAPSAP ECC Job Log, Spool and TBTCO Growth Housekeeping Calculator
Enter jobs per day, steps, spool share, average sizes and retention days to see how many job and spool rows you keep and how much TemSe storage they use in the database or file system.
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 6.0 EHP8 Upgrade Readiness ChecklistA step-by-step readiness checklist for upgrading SAP ECC 6.0 from EHP4 to EHP7 to EHP8 on NetWeaver 7.50 with SUM.
- 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 Classic MRP Run (MD01/MDBT) Runtime SimulatorEnter materials in scope, net change share, processing key, measured milliseconds per material and parallel processes to estimate the MRP job runtime and whether it fits the night window.
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.