A museum that has ancient assets to track will, no doubt, require that all asset entries use the full presentation of the year. The candidates for this review were identified by searching for lines of code containing the string '19', potentially symptomatic of a hard-coded century. I have visually inspected many these programs and have found several Y2K inconsistencies.
Programs then use a variety of algorithms to impute the intended century.
In the middle of the 1900's, this was not a problem, but as we move across the millennium, there are cases where the two-digit year is ambiguous. Several different strategies seem to be in use in SAP core code to deduce the intended century. The first of these strategies imputes the century of an entered date based on its relationship to the current system date. Assume a person was born in the year 1942, and it is now 2001. If the person's DOB was entered as '42', the program would first suppose the DOB to be 2042, discover that 2042 is greater than 2001, then reset the DOB to 1942, correctly.