Do you have any question about this error?
Stop googling SAP errors. Use our Free Essentials plan instead - no credit card needed. Start Now →
Message type: E = Error
Message class: HRPSGB_HER - HR PS GB Higher Education Messages (USS, HESA etc)
Message number: 350
Message text: HESA Record Validation Check Person.LOCLEAVE.4 failed
Person.LOCLEAVE should not equal 8 where Person.DATELEFT > '(Y1)-07-31'
and any contract record for this person has Contract.TERMS = 1 or 2.
The system issues an error message and will not allow you to continue with this transaction until the error is resolved.
Error message extract from SAP system. Copyright SAP SE.
HRPSGB_HER350
- HESA Record Validation Check Person.LOCLEAVE.4 failed ?The SAP error message HRPSGB_HER350 related to the HESA (Higher Education Statistics Agency) record validation typically indicates an issue with the data being processed for a specific employee or record in the context of HESA reporting. The specific part of the error message, Person.LOCLEAVE.4 failed, suggests that there is a validation failure related to the local leave data for a person.
Cause:
- Data Inconsistency: The error may arise due to inconsistencies or missing data in the employee's local leave records. This could include incorrect leave types, dates, or statuses.
- Configuration Issues: There may be issues with the configuration of the HESA reporting module or the local leave data structure.
- Incorrect Mapping: The mapping of local leave data to the HESA requirements may not be correctly set up, leading to validation failures.
- Missing Required Fields: Certain required fields for the HESA record may not be populated, leading to the validation check failing.
Solution:
- Review Local Leave Data: Check the local leave records for the employee in question. Ensure that all required fields are filled out correctly and that the data is consistent.
- Validate Configuration: Ensure that the HESA reporting configuration is set up correctly in your SAP system. This includes checking the mapping of local leave data to HESA fields.
- Check for Updates: Ensure that your SAP system is up to date with the latest patches and updates, as these may contain fixes for known issues.
- Consult Documentation: Refer to the SAP documentation for HESA reporting to understand the specific requirements for local leave data and ensure compliance.
- Run Validation Reports: Use any available validation reports or tools within SAP to identify and correct issues with the data before attempting to generate the HESA records again.
- Contact Support: If the issue persists after checking the above, consider reaching out to SAP support or your internal SAP team for further assistance.
Related Information:
By addressing the underlying data issues and ensuring compliance with HESA requirements, you should be able to resolve the error and successfully validate the records.
Get instant SAP help. Sign up for our Free Essentials Plan.
HRPSGB_HER349
HESA Record Validation Check Person.LOCLEAVE.3 failed
The system issues an error message and will not allow you to continue with this transaction until the error is resolved. Procedure for System Adminis...
HRPSGB_HER348
HESA Record Validation Check Person.LOCLEAVE.2 failed
What causes this issue? Person.LOCLEAVE must not exist where Person.DATELEFT does not exist.System Response The system issues an error message and w...
HRPSGB_HER351
HESA Record Validation Check Person.NATIOND.1 failed
The system issues an error message and will not allow you to continue with this transaction until the error is resolved. Procedure for System Adminis...
HRPSGB_HER352
HESA Record Validation Check Person.NATIOND.2 failed
What causes this issue? Person.NATIOND (National identity) must not exist for providers in England, Scotland and Northern Ireland.System Response Th...
Click on this link to search all SAP messages.