How does SUM recognize modification adjustment transports from predecessor systems?

Question

Options

• ABy searching for transport requests in DIR_TRANS, subdirectory "transport"
• BBy searching for transport requests that are assigned to project SAP_ADJUST
• CBy searching for transport requests named <sid>K0<number>
• DBy searching for transport requests in file umodauto.lst

• A
  3% (1)
• B
  3% (1)
• C
  6% (2)
• D
  89% (32)

Explanation

SUM (Software Update Manager) identifies modification adjustment transports from predecessor systems by scanning the file umodauto.lst, which explicitly lists the relevant transport requests. This file serves as the designated registry for these transports, making it the authoritative source SUM consults during the upgrade process.

Why the distractors are wrong:

• A is wrong because DIR_TRANS/transport (or cofiles/data subdirectories) is the general transport directory structure - SUM doesn't blindly search there to identify modification adjustment transports specifically.
• B is wrong because SAP_ADJUST is not a real project naming convention used to flag these transports; SUM does not filter by project assignment in the transport management system.
• C is wrong because the <SID>K0<number> naming pattern describes the standard format for customizing transport requests (K = workbench/customizing), not a special identifier for modification adjustment transports.

Memory tip: Think of the "lst" in umodauto.lst as a list - SUM needs a pre-compiled list of which transports are modification adjustments, and that list lives in umodauto.lst. The "umod" prefix stands for User MODification, tying the filename directly to its purpose.

No community discussion yet for this question.