How To Fix UMGLOG437 - Outdated messages in SPUMG main log.

SAP Error Message - Details

• Message type: E = Error

• Message class: UMGLOG - Message class for the SPUMG Main Log

• Message number: 437

• Message text: Outdated messages in SPUMG main log.

What causes this issue?

The status check "SPUMG Main Log" checks the SPUMG main log for outdated
messages. Log messages are considered to be outdated if there is a gap
of two years between two log messages.

System Response

The system issues an error message and will not allow you to continue with this transaction until the error is resolved.

How to fix this error?

in transaction SPUMG select Scanner -> Main Log from the menu
look for gaps in the log with a time difference greater than two years
decide whether the log messages originate from your current activities
in SPUMG or not

Procedure for System Administrators

If you started the preparation in SPUMG long time ago you should be sure
that there was no change in the language configuration of the system
after SPUMG was started
that all tables are included in the corresponding SPUMG work lists (make
sure to find the log message "Initialization of work list started."
(message number 2)
no modifications to database tables with respect to the "Text Language
Attribute" of language fields were applied after SPUMG was started
If you find out that the current preparation is based on a wrong or
outdated configuration you should restart SPUMG and start the
preparation from scratch (see section "Restart SPUMG" in the Unicode
conversion guide). Note: A restart of SPUMG deletes all existing SPUMG
data. The data cannot be restored.
<ZH>Known issues</>
There can be log messages originating from 2005. These messages were
created during tests and shipped with an upgrade. The message are
deleted when following the steps described in the Unicode conversion
guide (section "Restart SPUMG")

Error message extract from SAP system. Copyright SAP SE.