Now accepting guest editorial from SAP, Oracle, Workday and ServiceNow practitioners.Pitch a guide
The Sign-Off Table

Lesson 4 of 5

Downtime-optimized approaches

10 min

Listen to this lesson

0:00 / 7:43

In a DMO run, downtime is dominated by the migration of application data. When even a tuned standard run does not fit the window, SAP offers ways to move part of the work into uptime. Each one buys downtime with complexity, extra load on the running system and extra testing. Use them when measurements say you must, not because they sound modern.

Downtime-optimized DMO

Downtime-optimized DMO migrates selected large application tables during uptime. SAP's 2022 tuning deck calls it uptime migration: the initial load and most of the delta migrate while users work, user changes are captured with SUM's record-and-replay technology, and only the remaining delta migrates in downtime. SAP made it generally available with SUM 2.0 SP 06 for system conversions and migrations. The option is offered in the SUM dialog for the scenario strategy, a report helps select suitable tables, and replication monitoring is part of the SUM Utilities. SAP Note 2547309 describes it.

Record and replay in downtime-optimized DMO: large tables move while users post, and only the last delta is left for downtime.
The Sign-Off Table · thesignofftable.com/academy/sap-bas-302
  1. Select tablesLargest application tables chosen with SAP's selection report
  2. Initial load in uptimeSelected tables copied to SAP HANA while users work
  3. Record changesUser changes to those tables captured during uptime
  4. Replay deltaChanges replayed to the target; replication monitored in SUM Utilities
  5. DowntimeRemaining delta and all other tables migrated; update and conversion finish
Downtime-optimized DMO moves the bulk of the biggest tables into uptime.
The Sign-Off Table · thesignofftable.com/academy/sap-bas-302
ConstraintWhat it means
Only when the source is not yet on SAP HANAIt is a DMO option; a system already on SAP HANA has no migration to optimize
Not combinable with DMO with system moveSAP's DMO page states this; it can be combined with the move variant for S/4HANA conversion
Requires SUM 2.0Per SAP's DMO page and note
Extra load during uptimeRecording changes adds work to the productive system before downtime
More to verifyChanges made during uptime must arrive correctly in the target

Constraints of downtime-optimized DMO. Check the current note for your SUM support package.

Other options

Tuned standard DMORight number of R3loads, good table splits, duration files, data volume reduced
Downtime-optimized DMOLarge tables migrate in uptime with record and replay
Downtime-optimized conversionPart of the data conversion also moves into uptime; SAP requires an ADM329-trained expert for Private Edition
Near-zero downtime serviceSAP service approach for drastic reduction (SAP Note 693168); project-specific
Downtime options from simplest to most demanding.
The Sign-Off Table · thesignofftable.com/academy/sap-bas-302

Downtime-optimized conversion goes a step further than downtime-optimized DMO: SAP's 2025 conversion guide says it executes part of the data conversion in uptime processing, and for SAP S/4HANA Cloud Private Edition it requires an SAP expert who has completed training ADM329. SAP Note 3301507 describes executing and monitoring it. The near-zero downtime (nZDT) approach is an SAP service rather than a SUM option a customer switches on. Under RISE, SAP's roles and responsibilities document notes that the standard technical conversion service does not include nZDT, ZDO or other downtime minimization approaches; those must be agreed separately.

Decide on downtime optimization with numbers. Take the measured standard-run budget from the latest mock, subtract it from the window, and compare the gap with the contingency the program wants. If the gap is negative or thin, list the options with their expected savings, extra preparation, extra uptime load, extra test runs and contract implications under RISE. Grace's steering committee then decides with the trade-off in front of it, instead of hearing about a new technique for the first time on the go-live weekend.

Downtime optimization is decided from measurements: only a negative or thin gap puts the options, with their costs, in front of the steering committee.
The Sign-Off Table · thesignofftable.com/academy/sap-bas-302

What would you do?

Contoso's mock 2 measured 24 hours of SUM technical downtime, and the whole run took 58.5 hours: inside the 60-hour window, but with 1.5 hours of float, below the steering group's 4-hour minimum. A partner architect proposes downtime-optimized DMO for the dress rehearsal 'to be safe'. What should Sam recommend?

Key points
  • Downtime-optimized DMO migrates selected large tables in uptime with record and replay; GA since SUM 2.0 SP 06.
  • It applies only when the source is not on SAP HANA and cannot be combined with DMO with system move.
  • Downtime-optimized conversion moves part of the data conversion into uptime and needs an ADM329-trained expert for Private Edition.
  • Every uptime technique needs tests where users post during uptime; use them only when measurements require.

Check your understanding · not graded

Lesson check

  1. 1. How does downtime-optimized DMO capture user changes made during uptime?

  2. 2. Which combination does SAP say is not possible?

  3. 3. Why must a test of downtime-optimized DMO include postings during uptime?

  4. 4. Under RISE, how does SAP's R&R treat downtime minimization approaches such as nZDT or ZDO for the technical conversion?