Upgrades and Conversions with Software Update Manager (SUM)
Course quiz
Upgrades and Conversions with Software Update Manager (SUM)
Keep this: job aid
SUM conversion checklist for Basis
- Use SUM 2.0 for any SAP S/4HANA target; download the latest SP and read its central SAP Note.
- Inputs: stack.xml from the Maintenance Planner, the download basket, target kernels and HANA client for DMO, transports from earlier runs.
- Prerequisites: Unicode, AS ABAP only, supported start release (2025: SAP Notes 3549655 and 3493301), SI-Check errors at return code 8+ resolved.
- Roadmap: Extraction, Configuration, Checks, Preprocessing (shadow, SPDD), Execution (downtime), Postprocessing.
- Freeze development and transports once the shadow repository is being built.
- Budget business downtime: ramp-down, SUM, technical and application follow-ups, validation, ramp-up, contingency.
- Keep logs, phase durations and DMO duration files from every run; change one big thing at a time.
- Freeze the SUM version for the dress rehearsal and production.
- Before handover: SPAU and SPAU_ENH, SDM_MON, ST22 and SM21, SM37, SM59, ATC S4HANA_READINESS, Fiori and output smoke test.
- Hand over each run with a note; record the run number in all test evidence.