The SUM procedure stops with an error during uptime. How can you identify the current phase, the one in which SUM encountered an error? There are 2 correct answers to this question.

Question

Options

• ACheck the most recent entries shown in file sapevt.trc
• BCheck the system log (transaction SM21) of the SAP system
• CCheck the messages shown by the SUM UI
• DCheck the most recent entries in SAPup.log

• A
  9% (4)
• B
  2% (1)
• C
  89% (39)

Explanation

C is correct because the SUM (Software Update Manager) UI actively displays the current phase and any error messages in real time - when SUM halts, the UI clearly shows which phase it was executing when the error occurred, making it the most immediate and direct source.

D is correct because SAPup.log is SUM's primary activity log and records each phase transition along with error details. The most recent entries will pinpoint exactly which phase SUM was in when it failed.

A is wrong because sapevt.trc is a trace file related to SAP system events, not a SUM-specific log - it does not record SUM phase information or upgrade/update progress.

B is wrong because transaction SM21 shows the ABAP system log (OS-level and application server messages), which is not where SUM writes its phase or error information. SUM manages its own logging independently of SM21.

Memory tip: Think "SUM tells itself" - SUM reports its own status through its UI (C) and its own Update log, SAP**up**.log (D). Both contain the word or abbreviation of "SUM/update," while SM21 and sapevt.trc are general SAP system tools unrelated to SUM's internal phase tracking.

No community discussion yet for this question.