SAPFree referencePDF, Excel, Word exportSAP S/4HANA (on-premise)All SAP S/4HANA (on-premise) tools

SAP SUM 2.0 Roadmap Phases Reference

This reference walks through the SUM 2.0 roadmap from Extraction to Postprocessing, with the phases that matter most for Basis teams, where downtime starts and where to read the logs. It covers ABAP upgrades, S/4HANA conversions and Database Migration Option runs.

Download:

Roadmap step	Phase or sub-step	Uptime or downtime	What happens	Typical issue	Where to look
Before start	Start SUM UI	Uptime	Unpack SUM, register it with SAP Host Agent, open https://<host>:1129/lmsl/sumabap/<SID>/doc/sluigui	Host Agent too old or wrong user; port 1129 blocked	SAP Host Agent logs, SUM/abap/log
Extraction	Stack file and archives	Uptime	Reads stack.xml from Maintenance Planner, checks and extracts the archives into the download directory	Missing or wrong archives for the target stack	SUM/abap/log
Extraction	Tool and key checks	Uptime	Asks for passwords, checks kernel, SPAM/SAINT and SUM requirements, SAP Note implementation prompts	Required SAP Notes not implemented	SUM/abap/log
Configuration	Parameters	Uptime	Choose scenario options, number of R3trans, R3load and background processes, shadow instance number and ports	Too many processes for the host, port conflicts with the shadow instance	SUM/abap/log
Configuration	Add-ons and transports	Uptime	Decide add-on handling and include customer transports or SPDD/SPAU adjustment transports from a previous run	Add-on without a target version blocks the run	SUM/abap/log
Checks	Prerequisite checks	Uptime	Free space, database version, open updates, open transports and other prerequisites	Tablespace or disk space too small	SUM/abap/log
Preprocessing	Shadow instance	Uptime	Creates the shadow instance and imports the new repository into shadow tables (EU_IMPORT phases)	Long runtime on large repositories, shadow cannot start	SUM/abap/log, SUM/abap/tmp
Preprocessing	Development lock	Uptime	Development environment is locked; no more transports or repository changes	Developers lose work if not told in time	SUM/abap/log
Preprocessing	SPDD adjustment (before ACT_UPG)	Uptime	Adjust modified DDIC objects with SPDD in the shadow instance	Skipped SPDD lets SAP standard overwrite modified tables or fields	SPDD in shadow instance
Preprocessing	ACT_UPG	Uptime	Activates the new dictionary objects in the shadow	Activation errors for customer DDIC objects	SUM/abap/log (activation logs)
Preprocessing	DMO uptime migration (DMO only)	Uptime	With downtime-optimized options, part of the table migration runs in uptime	Changes during uptime must be replayed later	SUM/abap/log, migration logs
Preprocessing	DOWNCONF_DTTRANS	Uptime, end of	Asks you to confirm entering downtime	Users and jobs still active; lock users and suspend jobs first	SUM UI dialog
Execution	Switch	Downtime	Shadow repository is switched into the system, kernel switch (KX_SWITCH)	Kernel or profile problems after the switch	SUM/abap/log
Execution	DMO migration (DMO only)	Downtime	R3load export and import of tables to the target database, e.g. SAP HANA	Runtime longer than benchmarked; table splitting tuning	SUM/abap/log, migration logs in SUM/abap/migrate_*
Execution	PARCONV_UPG	Downtime	Table conversions and structure changes in parallel	Conversion errors on large or modified tables	SUM/abap/log (PARCONV logs)
Execution	TABIM_UPG	Downtime	Imports remaining table contents	Import errors from customer table content	SUM/abap/log
Execution	XPRAS_AIMMRG	Downtime	Runs XPRAs and after-import methods	XPRA errors that need SAP Notes; long runtimes on application data	SUM/abap/log (XPRA logs)
Postprocessing	SPAU and SPAU_ENH	After downtime (system can be released per guide)	Adjust modified repository objects and enhancements	Large SPAU backlog; Note corrections to reset or reapply	SPAU, SPAU_ENH
Postprocessing	SGEN and cleanup	Uptime	Load generation with SGEN, removal of shadow and temporary objects	Slow first use if SGEN is skipped	SGEN job logs
Postprocessing	Evaluation	Uptime	Runtime analysis UPGANA.XML, feedback form, SUM Utilities	Not saving the analysis for the next system run	SUM/abap/doc/analysis

Phase names follow SUM 2.0 for ABAP. Exact phase lists change with each SUM 2.0 SP: always read the SUM guide and the central SAP Note for your SUM SP. With near-Zero Downtime Maintenance (nZDM) or downtime-optimized DMO, more work moves into uptime.

Get your downtime estimate reviewed

Send us the UPGANA.XML from your sandbox run and we will point out the phases to tune before production.

Optional. The tool and every export work without this. No spam.

Was this tool useful?

How to use it

Read the table top to bottom as a runbook outline, or search for a phase name you see in the SUM UI or a log, such as ACT_UPG or PARCONV_UPG. The uptime or downtime column tells you whether users can still work. Downtime begins after you confirm it at the end of Preprocessing (DOWNCONF_DTTRANS), so lock users, suspend background jobs and stop interfaces just before that. The typical issue column lists what usually stops a run at that point, so you can prepare for it in the sandbox.

The six roadmap steps

SUM 2.0 runs six steps. Extraction reads the stack.xml from Maintenance Planner and extracts archives. Configuration sets process counts, the shadow instance and options such as nZDM or downtime-optimized DMO. Checks verifies space, versions and prerequisites. Preprocessing builds the shadow instance, imports the new repository, locks development, asks for SPDD and activates DDIC in ACT_UPG, all in uptime. Execution is the downtime: the switch, kernel switch, DMO migration if used, table conversion, imports and XPRAs. Postprocessing covers SPAU, SGEN, cleanup and evaluation.

SPDD happens in Preprocessing, in the shadow instance.
SPAU happens in Postprocessing, after the switch.
DMO adds the R3load migration in Execution.

Worked example: planning the weekend

On the sandbox run, save UPGANA.XML from SUM/abap/doc/analysis. It shows the runtime of every phase. Use the downtime phases (switch, migration, PARCONV_UPG, TABIM_UPG, XPRAS_AIMMRG) to estimate the production window, adding time for SPAU, tests and a rollback point. For DMO, run the benchmarking tool first to tune R3load process counts and table splitting. Feed the SPDD and SPAU transports from development into later runs through the Configuration step so you do not adjust the same objects again in QA and production.

Common mistakes

Teams skip SPDD and lose modified table fields, or tell developers about the development lock too late. Shadow instance ports clash with other instances on the host. Too many R3load or background processes overload the database host and make downtime longer, not shorter. People read only the SUM UI message and not the detailed log in SUM/abap/log, where the real error is. And they do not keep UPGANA.XML from the previous run, so the production plan rests on guesses.

Frequently Asked Questions

What are the SUM upgrade steps in SAP Basis?

SUM 2.0 runs six roadmap steps: Extraction, Configuration, Checks, Preprocessing, Execution and Postprocessing. Preprocessing builds the shadow instance and runs in uptime; Execution is the downtime with the switch, conversions and XPRAs; Postprocessing covers SPAU, SGEN and evaluation.

When does downtime start in SUM?

At the end of Preprocessing SUM asks you to confirm the start of downtime (phase DOWNCONF_DTTRANS). Before confirming, lock users, suspend background jobs and stop interfaces. With nZDM or downtime-optimized DMO, more work happens in uptime and the downtime part is shorter.

When do I do SPDD and SPAU?

SPDD comes in Preprocessing, in the shadow instance before ACT_UPG activates the dictionary. SPAU and SPAU_ENH come in Postprocessing, after the switch. Collect both in transports and feed them into later runs so the next systems pick them up automatically.

Where are the SUM logs?

Most logs are in SUM/abap/log, with temporary and working files in SUM/abap/tmp. The runtime analysis UPGANA.XML is in SUM/abap/doc/analysis. Read the detailed log named in the SUM UI error message, not just the summary.

If you want your Basis team to search SUM logs and runbooks in plain English on your own servers, Netray can set up a private AI assistant for that.

Talk to an Expert Explore More Free Tools