How To Fix HRPSGB_HER218 - HESA INTERDEPENDENCY Validation Check &1 &2 &3 failed

SAP Error Message - Details

• Message type: E = Error

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

• Message number: 218

• Message text: HESA INTERDEPENDENCY Validation Check &1 &2 &3 failed

What causes this issue?

The employee has had PERSON and CONTRACT(s) records created that fails
one of the validation checks below:
Entity Fieldname Nr Description
Contract TCHWLH 3 Contract.TCHWLH must not equal 1 where
Person.ABLWELSH = 2.
Contract STARTCON 7 Contract.STARTCON must be before or on
Person.DATELEFT where all Contract.TERMS = 1 or 2
Person ABLWELSH 2 Person.ABLWELSH must exist for institutions
in Wales where any Contract.ACEMPFUN = 1 or 3 and Contract.TERMS = 1 or
2.
Person ACTCHQUAL 1 Person.ACTCHQUAL must exist for institutions
in England, Wales and Northern Ireland where any (Contract.ACEMPFUN = 1
or 3) and Contract.TERMS = 1 or 2.
Person ACTLEAVE 1 Person.ACTLEAVE must exist where
Person.DATELEFT is not null and (Contract.TERMS = 1 or 2) and (no
Contract.RESCON = 8) where any Activity.ACTSOC begins with 1, 2 or 3.
Person BIRTHDTE 1 Person.BIRTHDTE must exist where any
Contract.TERMS = 1 or 2.
Person BIRTHDTE 2 Person.BIRTHDTE must exist where any
Contract.TERMS = 3 and Contract.ACEMPFUN = 1, 2, 3, or 9.
Person CLINARD 1 Person.CLINARD must exist where any
Contract.CLINICAL = 1.
Person CLINARD 2 Person.CLINARD must not exist where all
Contract.CLINICAL not equal to 1.
Person CURACCDIS 1 Person.CURACCDIS must exist where any
(Contract.ACEMPFUN = 1, 2 or 3) and Contract.TERMS = 1 or 2
Person CURACCDIS 2 Person.CURACCDIS must not exist where all
Contract.ACEMPFUN = 4 or 9
Person DATEFHEI 1 Person.DATEFHEI must exist where any
Contract.TERMS = 1 or 2.
Person DATELEFT 1 Person.DATELEFT must exist where any
(Contract.TERMS = 1 or 2) and (all Contract.ENDCON are not null) and all
Contract.RESCON not equal to 1.
Person DATELEFT 2 Person.DATELEFT must not exist where any
Contract.ENDCON are null.
Person ECRSTAT 1 Person.ECRSTAT must exist where any
(Contract.ACEMPFUN = 2 or 3 and Contract.TERMS = 1 or 2) and
Person.RESAST does not equal 1.
Person ECRSTAT 2 Person.ECRSTAT must not exist where all
Contract.ACEMPFUN not equal to 2 or 3.
Person ECRSTAT 3 Person.ECRSTAT must not exist where any
Contract.ACEMPFUN = 2 or 3 and Person.RESAST = 1.
Person HQHELD 1 Person.HQHELD must exist where
(Contract.TERMS = 1 or 2) and any Activity.ACTSOC begins with 1, 2 or 3
Person LOCLEAVE 1 Person.LOCLEAVE must exist where
Person.DATELEFT exists and (no Contract.RESCON = 8) and any
Activity.ACTSOC begins with 1, 2 or 3.
Person LOCLEAVE 2 Person.LOCLEAVE must not exist where
Person.DATELEFT exists and any Contract.RESCON is coded 8.
Person PREVEMP 1 Person.PREVEMP must exist where
(Contract.TERMS = 1 or 2) and any Activity.ACTSOC begins with 1, 2 or 3.
Person PREVHEI 1 Person.PREVHEI must exist where
Person.PREVEMP = 01 and any Activity.ACTSOC begins with 1, 2 or 3.
Person REFUOA2014 1 Person.REFUOA2014 should not exist where all
Contract.ACEMPFUN not equal to 2 or 3
Person REFUOA2014 2 Person.REFUOA2014 must not exist where
Person.RESAST = 1 or no contract exists where (Contract.ACEMPFUN = 2 or
3 and Contract.TERMS = 1 or 2 and the contract is active on
'(Y1)-10-31')
Person REFUOA2014 3 Person.REFUOA2014 should exist where
Person.RESAST <> 1 and any contract exists where (Contract.ACEMPFUN = 2
or 3 and Contract.TERMS = 1 or 2 and the contract is active on
'(Y1)-10-31')
Person REGBODY 1 Person.REGBODY must exist where any
Contract.CLINICAL = 1, 2, 3 or 4 or (any Activity.CCENTRE = 109 and
Contract.ACEMPFUN = 1, 2, or 3 and Contract.TERMS = 1 or 2).
Person REGBODY 2 Person.REGBODY can only exist where there is
a Contract.CLINICAL = 1, 2, 3, or 4 or there is a Contract with (any
Activity.CCENTRE = 109 and Contract.ACEMPFUN = 1, 2, or 3 and
Contract.TERMS = 1 or 2).
Person REGBODY 4 Person.REGBODY (must equal 01 or 02) where
any Contract.CLINICAL = 1.
Person REGBODY 5 Person.REGBODY must equal 06 where any
Contract.CLINICAL = 2.
Person REGBODY 6 Person.REGBODY must equal 07 where any
Contract.CLINICAL = 3 .
Person RESAST 1 Person.RESAST must exist where any
Contract.ACEMPFUN = 2 and Contract.TERMS = 1 or 2.
Person RESAST 2 Person.RESAST must not exist where all
Contract.ACEMPFUN not equal to 2 or all Contract.TERMS = 3.
Person RESAST 3 Person.RESAST must not exist where all
Contract.TERMS = 3.
Person SEX 1 Person.SEX must exist where any
Contract.TERMS = 1 or 2.
Person SEX 2 Person.SEX must exist where any
Contract.TERMS = 3 and Contract.ACEMPFUN = 1, 2, 3 or 9.

System Response

Either incorrect data has been stored in the HESA infotypes, by the
incorrect maintenance of the customising tables that relate to the error
in question or the HESA return has incorrectly generated the person
record.

How to fix this error?

If you can resolve this problem by correcting the employees master data
then do so.
If you cannot resolve this problem by correcting the employees master
data then please raise a customer message referencing the specific code
that has failed. In this case, it is likely that this is due to a fault
in the logical design of the HESA return and not necessarily the
employee's data.

Procedure for System Administrators

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.

Smart SAP Assistant

• What is the cause and solution for SAP error message HRPSGB_HER218 - HESA INTERDEPENDENCY Validation Check &1 &2 &3 failed ?

  The SAP error message HRPSGB_HER218, which pertains to the HESA (Higher Education Statistics Agency) interdependency validation check, indicates that there is an issue with the data being submitted for HESA reporting. This error typically arises when certain interdependencies between fields in the HESA data are not met, meaning that the values in the specified fields do not align with the expected relationships or rules defined by HESA.
  Cause:
  The error message "HESA INTERDEPENDENCY Validation Check &1 &2 &3 failed" suggests that:
  
  There are specific interdependencies between the fields that are not satisfied. For example, if one field requires a certain value based on the value of another field, and that condition is not met, this error will occur.
  The data being submitted may be incomplete, incorrect, or not formatted properly according to HESA requirements.
  There may be missing or invalid entries in the relevant fields that are required for the validation check.
  
  Solution:
  To resolve this error, you can take the following steps:
  
  
  Review the Error Message: The placeholders &1, &2, and &3 in the error message will provide specific details about which fields are causing the validation failure. Review these details carefully.
  
  
  Check HESA Guidelines: Refer to the HESA data submission guidelines to understand the interdependencies between the fields. Ensure that the data you are submitting adheres to these guidelines.
  
  
  Validate Data Entries: Go through the data entries in the relevant fields and check for:
  
  Correctness of values (e.g., valid codes, formats).
  Completeness of data (e.g., no missing mandatory fields).
  Logical consistency (e.g., if one field indicates a certain status, ensure that related fields reflect that status appropriately).
  
  
  
  Use SAP Tools: Utilize any available SAP tools or reports that can help identify data inconsistencies or issues. This may include running validation reports or using transaction codes related to HESA reporting.
  
  
  Consult Documentation: Check the SAP documentation or notes related to HESA reporting for any known issues or additional guidance on resolving validation errors.
  
  
  Seek Help from Colleagues or SAP Support: If you are unable to resolve the issue, consider reaching out to colleagues who have experience with HESA reporting or contact SAP support for assistance.
  
  
  Related Information:
  
  HESA Reporting: HESA is responsible for collecting and publishing data about higher education in the UK. Institutions must comply with specific data standards and interdependencies when submitting their data.
  SAP HR Module: The error is related to the SAP Human Resources (HR) module, specifically the components dealing with employee data and reporting.
  Data Quality: Maintaining high data quality is crucial for successful HESA submissions, as errors can lead to compliance issues and potential penalties.
  
  By following these steps, you should be able to identify and correct the issues causing the HRPSGB_HER218 error message.