How To Fix HRTMC_BASIS508 - February 28 must be entered instead of February 29

SAP Error Message - Details

• Message type: E = Error

• Message class: HRTMC_BASIS - Message Class for Talent Management Core (HCM_TMC)

• Message number: 508

• Message text: February 28 must be entered instead of February 29

What causes this issue?

February 28 must be specified instead of February 29, otherwise the key
date will only be found in leap years.

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?

Procedure for System Administrators

Error message extract from SAP system. Copyright SAP SE.

Smart SAP Assistant

• What is the cause and solution for SAP error message HRTMC_BASIS508 - February 28 must be entered instead of February 29 ?

  The SAP error message HRTMC_BASIS508 indicates that there is an issue with date entry, specifically related to the handling of leap years. The error message states that "February 28 must be entered instead of February 29," which typically occurs when a user attempts to enter a date of February 29 in a year that is not a leap year.
  Cause:
  
  Non-Leap Year Entry: The most common cause of this error is that the user is trying to enter February 29 in a year that is not a leap year. For example, 2023 is not a leap year, so February 29 does not exist in that year.
  System Configuration: There may be configurations or validations in the SAP system that enforce date rules, leading to this error when an invalid date is entered.
  
  Solution:
  
  Check the Year: Verify the year for which you are trying to enter the date. If it is not a leap year, change the date to February 28.
  Correct Date Entry: If you intended to enter February 29, ensure that you are doing so in a leap year (e.g., 2020, 2024).
  Validation Rules: If you are developing or configuring the system, review any custom validations or rules that may be enforcing this check and adjust them if necessary.
  
  Related Information:
  
  Leap Year Calculation: A leap year occurs every four years, except for years that are divisible by 100 but not by 400. For example, 2000 was a leap year, but 1900 was not.
  SAP Documentation: Refer to SAP Help documentation for more details on date handling and error messages related to date entries.
  User Training: Ensure that users are trained on how to correctly enter dates, especially around February in leap years.
  
  If the issue persists after checking the above points, it may be beneficial to consult with your SAP support team or refer to SAP Notes for any specific patches or updates related to this error message.