You are performing an SAP S/4HANA conversion. Which phases are executed during SUM technical downtime? Note: There are 2 correct answe rs to this question.

Question

Options

• ATABIM_UPG
• BPARDIST_SHD
• CPARMVNT_UPG
• DTABIM_SHADOW_*

• A
  5% (1)
• B
  86% (19)
• D
  9% (2)

Explanation

During SUM-based S/4HANA conversion, technical downtime begins once the production system is locked for cutover. PARDIST_SHD (Parallel Distribution Shadow) executes during this window to distribute the shadow-prepared content into the live production system, and PARMVNT_UPG (Parallel Movement Upgrade) performs the parallel movement of upgrade objects into production tables - both are cutover-phase activities that require the system to be offline.

Option A (TABIM_UPG) is wrong because TABIM (Table Import) phases run during the uptime window, importing table structures into the shadow repository before technical downtime begins. Option D (TABIM_SHADOW_*) is wrong because the word "SHADOW" in the phase name explicitly identifies it as a shadow-phase (uptime) activity - these phases complete well before the system is ever locked.

Memory tip: Think of it as two stages - "build in shadow (uptime)" vs. "move/distribute to production (downtime)." Phases with SHADOW in the name stay in uptime; PARDIST (distribute) and PARMVNT (move) are the handoff actions that can only happen once the system is locked, making them technical downtime phases.

No community discussion yet for this question.