What would cause the expiry date to calculate with a year of 1932?

SUGGESTED

We have products that have a 10 year expiry date. Our operations team has reported that on these products as they are processed on a work order they come out with an expiry date of 1932. I am at a loss as to what would cause this. Any guidance would be much appreciated!

  • 0
    SUGGESTED

    Is it perhaps the set rollover date in the system?  See this.

    (+) Date field default year 1930 instead of 2030 - General Discussion - Sage X3 - Sage City Community

    Try setting the two digit max year in locale preferences.

    This is called the rollover date and it was a popular topic around the changing of the millennium.   

    adxdcs is a pivot year used to determine the century when the year is two digits.

    Upper and lower bound

    You need to provide a pivot date to define the century used by default when the date is two digits. Only the upper bound is entered, the lower bound is calculated accordingly.

    Example: If you enter 2029 for the upper bound:

    • Any date with a year that has two digits lower or equal to 29 is in the [2000-2029] range.
    • Any date with a year that has two digits between 30 and 99 is in the [1930-1999] range, which is the reason why 1930 > is displayed in the lower bound.

    Online  in reply to Christine T.

    Just set the pivot year to 2050.   As long as you have no data in the system with 2 digits years prior to 1950 it will then start "pivoting" on 2050.  Birthdays can be a problem because folks born in 1949 with a 2 digit year entered would be born in 2049 but you would think that programmers would use a 4 digit year anywhere that exist. 

    So editing the discussion above

    Example: If you enter 2050 for the upper bound:

    • Any date with a year that has two digits lower or equal to 50 is in the [2000-2050] range
    • Any date with a year that has two digits between 50 and 99 is in the [1950-1999] range