When using the DMO of SUM, which files can be handled by SUM in the download directory? Note: There are 2 correct answe rs to this question.

Question

Options

• ABreakpoint configuration file SAPUPPHAS.BRK
• BParameter file SAPup_add.par
• CMIGRATE_DT_DUR.XML file from a previous run
• DStack XML file calculated by the maintenance planner

• A
  9% (3)
• B
  3% (1)
• C
  88% (28)

Explanation

In SAP SUM with DMO, the download directory is where users place externally sourced or reusable files that SUM picks up automatically. The Stack XML file (D) is generated by SAP Maintenance Planner and must be placed in the download directory - it defines the target software stack and is a mandatory input for any SUM run. The MIGRATE_DT_DUR.XML file (C) captures migration duration data from a prior DMO run and can be reused in the download directory to give SUM accurate time estimates for migration steps in a repeat or resumed run.

Why the distractors are wrong:

• (A) SAPUPPHAS.BRK is a breakpoint/phase control file managed internally by SUM in its own working directories - users don't place it in the download directory.
• (B) SAPup_add.par is an additional parameter file for SUM but it belongs in the SUM installation/configuration path, not the download directory.

Memory tip: Think "D = Downloaded from Maintenance Planner" (it literally comes from the MP download) and "C = Carry over from a previous run" - both are files that originate outside the current SUM process and get dropped into the download directory for SUM to consume.

No community discussion yet for this question.