# SAP ECC 6.0 EHP8 Upgrade Effort Simulator (SPDD, SPAU and Downtime)

> Source: https://netray.co/tools/sap-ecc-ehp8-upgrade-spau-spdd-effort-simulator
> Publisher: Netray (netray.co), AI and integration engineering for ERP and manufacturing systems.
> Section: Free Tools

## Short answer

Enter 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.

## Category

sap

## Erp

SAP ECC 6.0

## Audience

- SAP Basis lead
- ABAP developer
- SAP program manager

## Tool

**Kind:** calculator

**Inputs:**

#### SPDD objects (dictionary modifications)

**Key:** spdd

**Type:** number

**Default:** 40

**Min:** 0

**Step:** 5

**Unit:** objects

#### SPAU objects (repository modifications incl. notes)

**Key:** spau

**Type:** number

**Default:** 600

**Min:** 0

**Step:** 10

**Unit:** objects

#### SPAU share handled automatically (notes reset or adopted)

**Key:** auto

**Type:** slider

**Default:** 60

**Min:** 0

**Max:** 100

**Step:** 5

**Unit:** %

#### Minutes per SPDD object

**Key:** m_spdd

**Type:** number

**Default:** 45

**Min:** 1

**Step:** 5

**Unit:** min

#### Minutes per manual SPAU object

**Key:** m_spau

**Type:** number

**Default:** 20

**Min:** 1

**Step:** 5

**Unit:** min

#### Custom objects to retest

**Key:** custom

**Type:** number

**Default:** 300

**Min:** 0

**Step:** 10

**Unit:** objects

#### Test hours per 100 objects

**Key:** th

**Type:** number

**Default:** 16

**Min:** 0

**Step:** 1

**Unit:** hours

#### SUM technical downtime (from rehearsal)

**Key:** sum_dt

**Type:** number

**Default:** 10

**Min:** 0

**Step:** 1

**Unit:** hours

#### Where SPDD runs in the first system

**Key:** spdd_mode

**Type:** select

**Default:** 0

**Options:**

##### Shadow system, uptime (standard)

**Value:** 0

##### Single system mode, downtime

**Value:** 1

#### Upgrade cycles (dev, rehearsals, production)

**Key:** cycles

**Type:** slider

**Default:** 3

**Min:** 1

**Max:** 6

**Step:** 1

**Unit:** cycles

#### Effort of each later cycle vs first

**Key:** later

**Type:** slider

**Default:** 30

**Min:** 0

**Max:** 100

**Step:** 5

**Unit:** %

**Help:** Planning assumption: later cycles import the SPDD/SPAU transports and retest a subset.

**Outputs:**

#### SPDD adjustment hours

**Key:** spdd_h

**Expr:** spdd * m_spdd / 60

**Format:** hours

#### Manual SPAU objects

**Key:** spau_manual

**Expr:** round(spau * (1 - auto / 100))

**Format:** integer

#### SPAU adjustment hours

**Key:** spau_h

**Expr:** spau_manual * m_spau / 60

**Format:** hours

#### Retest hours

**Key:** test_h

**Expr:** custom / 100 * th

**Format:** hours

#### ABAP effort, first cycle

**Key:** cycle_h

**Expr:** spdd_h + spau_h + test_h

**Format:** hours

#### ABAP effort, all cycles

**Key:** total_h

**Expr:** cycle_h * (1 + (cycles - 1) * later / 100)

**Format:** hours

**Primary:** true

#### First system outage (SUM downtime plus SPDD if in downtime)

**Key:** dev_outage

**Expr:** sum_dt + spdd_mode * spdd_h

**Format:** hours

**Primary:** true

**Chart:**

#### Total ABAP effort vs SPAU objects

**Type:** line

**X:** spau

**From:** 100

**To:** 3000

**Steps:** 30

**Series:**

- total_h

**Disclaimer:** Minutes per object, test hours and the later-cycle share are planning assumptions to replace with your own rehearsal figures, not SAP figures.

## Content

**Intro:** 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.

**Sections:**

#### Where SPDD and SPAU fall in a SUM run

**Body:** 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.

**Bullets:**

- 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

**Body:** 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

**Body:** 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

**Body:** 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.

**Cta:** 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.

**Faq:**

#### Can I upgrade SAP ECC 6.0 from EHP4 directly to EHP8?

**Answer:** 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?

**Answer:** 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?

**Answer:** 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?

**Answer:** 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.

## Search terms

upgrade sap ecc 6.0 ehp4 to ehp8, sap ecc 6.0 ehp 8 upgrade guide, sap system upgrade steps, sp upgrade in sap, upgrade project in sap abap, spdd spau adjustment, sap sum upgrade phases

---
Talk to an engineer: https://netray.co/contact?intent=erp_ai | Machine catalog: https://netray.co/agent/catalog.json