You have selected "Standard" as scenario strategy in the SUM tool. Which steps take place via the shadow instance? Note: There are 2 correct answe rs to this question.

Question

Options

• AModification adjustment (SPAU)
• BModification adjustment (SPDD)
• CActivation of dictionary objects (ACT_UPG)
• DConversion of application tables (PARCONV_UPG)

• A
  18% (12)
• B
  74% (48)
• D
  8% (5)

Explanation

In SAP SUM's Standard scenario, the shadow instance runs in parallel with the live system to pre-process ABAP Dictionary work before downtime begins. SPDD (B) - the modification adjustment for Dictionary objects - is performed via the shadow instance so that dictionary conflicts can be resolved before the system goes down. ACT_UPG (C) - activation of those dictionary objects - also runs on the shadow instance, reducing the actual downtime window significantly.

SPAU (A) is wrong because it handles modifications to Repository objects (programs, screens, etc.) and is performed after the system switch in the main instance, not the shadow. PARCONV_UPG (D) is wrong because table conversion operates on the real database and occurs in the main instance during the downtime phase - the shadow instance cannot touch production data.

Memory tip: Shadow = Dictionary. Both correct answers (SPDD and ACT_UPG) deal with ABAP Dictionary objects - the shadow instance "shadows" the dictionary work ahead of time. If the step touches real tables or repository source code, it's not shadow work.

No community discussion yet for this question.