How To Fix HRPSGB_HER337 - HESA Record Validation Check Person.DATELEFT.4 failed

SAP Error Message - Details

• Message type: E = Error

• Message class: HRPSGB_HER - HR PS GB Higher Education Messages (USS, HESA etc)

• Message number: 337

• Message text: HESA Record Validation Check Person.DATELEFT.4 failed

What causes this issue?

Person.DATELEFT must be between (Y1-1)-08-01 and (Y2)-07-31 (inclusive)

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 HRPSGB_HER337 - HESA Record Validation Check Person.DATELEFT.4 failed ?

  The SAP error message HRPSGB_HER337 related to the HESA (Higher Education Statistics Agency) record validation typically indicates an issue with the data related to an employee's record, specifically concerning the DATELEFT field. This error is common in the context of higher education institutions in the UK that need to report staff data to HESA.
  Cause:
  The error message HRPSGB_HER337 HESA Record Validation Check Person.DATELEFT.4 failed usually arises due to one of the following reasons:
  
  Invalid Date Format: The DATELEFT field may contain a date that is not in the correct format or is not a valid date.
  Logical Inconsistency: The DATELEFT date may be earlier than the DATESTART or may not align logically with other date fields (e.g., DATEJOINED, DATELEFT should not be before DATEJOINED).
  Missing Data: The DATELEFT field may be empty when it is required for the record.
  Incorrect Employee Status: The employee's status may not align with the expected values for the DATELEFT field (e.g., if the employee is still active, there should not be a DATELEFT).
  
  Solution:
  To resolve the error, you can take the following steps:
  
  Check the Date Format: Ensure that the DATELEFT field is populated with a valid date in the correct format (usually YYYY-MM-DD).
  Verify Logical Consistency: Compare the DATELEFT date with other relevant date fields (like DATESTART, DATEJOINED) to ensure they are logically consistent.
  Complete Required Fields: If the DATELEFT field is mandatory, ensure it is filled out correctly. If the employee is still active, this field may need to be left blank or set to a specific value indicating they have not left.
  Review Employee Status: Check the employee's status in the system to ensure it aligns with the data being reported. If the employee is still active, the DATELEFT should not be populated.
  Consult Documentation: Refer to the HESA reporting guidelines to ensure compliance with the required data fields and formats.
  
  Related Information:
  
  HESA Reporting: Familiarize yourself with the HESA data requirements and validation rules, as they can provide insights into what is expected for each field.
  SAP Notes: Check for any SAP Notes or updates related to HESA reporting that may address known issues or provide additional guidance.
  Testing: After making corrections, run the validation checks again to ensure that the error has been resolved.
  
  If the issue persists after following these steps, it may be beneficial to consult with your SAP support team or a specialist in HESA reporting for further assistance.