How To Fix HRPSGB_HER335 - HESA Record Validation Check Person.DATELEFT.2 failed

SAP Error Message - Details

• Message type: E = Error

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

• Message number: 335

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

What causes this issue?

Person.DATELEFT must not exist where any (Contract.TERMS = 1 or 2 and
Contract.ENDCON are null).

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

  The SAP error message HRPSGB_HER335 related to the HESA (Higher Education Statistics Agency) record validation typically indicates an issue with the DATELEFT field for a person in the HR system. This error is often encountered in the context of reporting or data submission to HESA, which is responsible for collecting and publishing data about higher education in the UK.
  Cause:
  The error message HRPSGB_HER335 HESA Record Validation Check Person.DATELEFT.2 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 expected format or is invalid (e.g., a future date or a date that does not exist).
  Logical Inconsistency: The DATELEFT may not logically align with other date fields, such as DATEJOINED or DATEOFLEAVING. For example, if the DATELEFT is earlier than the DATEJOINED, it would trigger this error.
  Missing Data: The DATELEFT field may be empty or not populated when it is required.
  Incorrect Configuration: There may be issues with the configuration of the HESA reporting module or the specific validation rules applied.
  
  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: Cross-check the DATELEFT against other relevant date fields (like DATEJOINED and DATEOFLEAVING) to ensure that the dates make logical sense.
  Populate Missing Fields: If the DATELEFT field is empty and should be filled, update it with the correct date.
  Review Configuration: If the issue persists, review the configuration settings for the HESA reporting module to ensure that all necessary fields and validation rules are correctly set up.
  Consult Documentation: Refer to the SAP documentation or HESA guidelines for any specific requirements regarding the DATELEFT field.
  Testing: After making corrections, run the validation check again to ensure that the error is resolved.
  
  Related Information:
  
  HESA Reporting: Familiarize yourself with the HESA reporting requirements and guidelines, as they provide detailed information on the data fields and their expected formats.
  SAP Notes: Check for any relevant SAP Notes or updates that may address known issues with HESA reporting or the specific error message.
  Support: If you are unable to resolve the issue, consider reaching out to your SAP support team or consulting with a specialist who has experience with HESA reporting in SAP.
  
  By following these steps, you should be able to identify and correct the issue causing the HRPSGB_HER335 error message.