Basis Errors and Solutions

Symptom

The entries in the password history (table USRPWDHISTORY) are not saved in the correct chronological order if several entries (due to password changes or password assignments) were made within 24 hours.
Other terms

UTC, Coordinated Universal Time, time zones, GMT, Greenwich Mean Time
Reason and Prerequisites

In the password history, the system saves the hash values of the (production) passwords that a user previously chose (but does not save the hash values of the (initial) passwords that an administrator assigned to the user).
There are two events that cause the system to create new entries in the password history:
If a user changes their own password (as long as they chose the previous password). This takes place in the kernel. Here, the system uses the system time stamp instead of the UTC time stamp; this is incorrect.If an administrator assigns a new password to a user (as long as the previous password was chosen by the user; that is, if it was a production password). This takes place using ABAP functions. Here, the system uses the UTC time stamp; this is correct.

Depending on the time zone used for the system time, the variation from UTC (or the Greenwich Meridian) may be significant.
Solution

Implement a new kernel.