How To Fix HRPSGB_HER217 - HESA CONTRACT Record 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: 217

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

What causes this issue?

The employee has had a CONTRACT record created that fails one of the
validation checks below:
Entity Fieldname Nr Description
Activity ACTSOC 1 Where there are multiple occurrences of
Activity.ACTSOC, Activity.CCENTRE and Activity.CCPROP they must not be
identical.
Activity CCPROP 1 Where only one Activity returned
Activity.CCPROP must be 100
Activity CCPROP 2 Where Multiple Activity entities are
returned the sum of all Activity.CCPROP must be in the range 99.7 and
100.3
Contract ACEMPFUN 1 Contract.ACEMPFUN must exist where any
Activity.ACTSOC begins with 1, 2 or 3.
Contract ACEMPFUN 2 Contract.ACEMPFUN must not exist unless at
least one Activity.ACTSOC under that Contract begins with 1, 2 or 3.
Contract CLINICAL 1 Contract.CLINICAL must exist where
(Contract.ACEMPFUN = 1, 2 or 3) and (Contract.TERMS = 1 or 2) and any
Activity.CCENTRE = 101, 102, 103, 104, 105, 106, 107, 108, 112, 127 or
131.
Contract CLINICAL 2 Contract.CLINICAL must not exist where
all Activity.CCENTRE not equal to 101, 102, 103, 104, 105, 106, 107,
108, 112, 127 or 131.
Contract CLINSUB 1 Contract.CLINSUB must exist where
Contract.CLINICAL = 1.
Contract CLINSUB 2 Contract.CLINSUB must not exist where
Contract.CLINICAL not equal to 1.
Contract CLINSUB 3 Where there is more than one occurrence of
Contract.CLINSUB they must not be identical.
Contract CONFTE 1 Contract.CONFTE must be 0 where
Contract.MOEMP = 6
Contract CONFTE 2 Where (Contract.MOEMP is 3, 4 or 5) then
Contract.CONFTE must not be 100.
Contract CONFTE 3 Where (Contract.ENDCON > (YY)-07-31) and
Contract.ENDCON has been returned for this contract, then
Contract.CONFTE must not be 100
Contract CONFTE 4 Contract.CONFTE must not be 000.0 where
(Contract.MOEMP in (1, 2, 3, 4, 5) and (Contract.ENDCON > '(Y1)-07-31'
or Contract.ENDCON does not exist)).
Contract ENDCON 1 Contract.ENDCON must exist where
Contract.TERMS = 1 or 2 and ReasonForNull does not equal 1
Contract ENDCON 2 Contract.ENDCON must be null where
ReasonForNull = 1.
Contract ENDCON 3 Where Contract.ENDCON is null ReasonForNull
must equal 1.
Contract ENDCON 4 Where exists Contract.ENDCON must be less
than Y2-08-01
Contract ENDCON 5 Contract.ENDCON must be equal to or after
the date returned in Contract.STARTCON.
Contract ENDCON 6 Contract.ENDCON must be before or equal to
Person.DATELEFT where all Contract.TERMS = 1 or 2
Contract HEIJOINT 1 Contract.HEIJOINT must not be the returning
institution.
Contract HEIJOINT 2 Contract.HEIJOINT must not exist where
Contract.ACEMPFUN is not equal to 1, 2, 3 or 9
Contract HSPEC 1 Contract.HSPEC must exist where
Contract.CLINICAL = 1, 2, 3 or 4.
Contract HSPEC 2 Contract.HSPEC must not exist where
Contract.CLINICAL is not equal to 1, 2, 3 or 4.
Contract HSPEC 3 Where there is more than one occurrence of
Contract.HSPEC they must not be identical.
Contract LEVELS 1 Contract.LEVELS must exist where
(Person.DATELEFT is after (Y1)-07-31 or Person.DATELEFT does not exist)
and ((Contract.TERMS = 1 or 2) or (Contract.ACEMPFUN = 1, 2, 3 or 9 and
Contract.TERMS = 3))
Contract NHSCON 1 Contract.NHSCON must exist where
Contract.CLINICAL is equal to 1, 2, 3 or 4.
Contract NHSCON 2 Contract.NHSCON must not exist where
Contract.CLINICAL is not equal to 1, 2, 3 or 4.
Contract NHSCONGR 1 Where Contract.STARTCON is after 2009-08-01
Contract.NHSCONGR must not equal 02, 03, 06 or 07
Contract NHSCONGR 2 Contract.NHSCONGR must exist where
Contract.CLINICAL = 1, 2, 3 or 4.
Contract NHSCONGR 3 Contract.NHSCONGR must not exist where
Contract.CLINICAL is not equal to 1, 2, 3 or 4.
Contract PSCAG 1 Contract.PSCAG must exist where
Contract.TERMS = 1 or 2.
Contract PSCAG 2 Where Contract.SOBS = 01 then
Contract.PSCAG must be 100.
Contract PSCAG 3 Where Contract.SOBS not equal to 01 then
Contract.PSCAG must not be 100.
Contract RESAST 1 Where Contract.RESAST must exist where
Contract.ACEMPFUN = 2 and Contract.TERMS = 1 or 2.
Contract RESAST 2 Where Contract.RESAST must not exist
whereContract.ACEMPFUN does not equal 2 or Contract.TERMS = 3.
Contract RESCON 1 Where Contract.RESCON = 8 there must be no
new contracts starting after that Contract.ENDCON.
Contract RESCON 2 Contract.RESCON must exist where
Contract.TERMS = 1 or 2 and Contract.ENDCON exists.
Contract RESCON 3 Contract.RESCON must not exist where
(Contract.ENDCON does not exist and Contract.TERMS = 1 or 2.)
Contract SALREF 1 Where Contract.SALREF exists, then
Contract.SALREF must not be greater than 325000.
Contract SALREF 2 Where Contract.SALREF exists, then
Contract.SALREF must not be less than 4800.
Contract SALREF 3 Contract.SALREF must not exist where
Contract.SPOINT begins with C.
Contract SALREF 4 Contract.SALREF must exist where
(Contract.TERMS = 1 or 2) and Contract.SPOINT does not exist.
Contract SOBS 1 Where there is more than one occurrence
of Contract.SOBS they must not be identical.
Contract SOBS 2 Where Contract.SOBS = 01 there must be
no other occurrences of Contract.SOBS.
Contract SOBS 3 Contract.SOBS must exist where
Contract.TERMS = 1 or 2.
Contract STARTCON 1 Contract.STARTCON must not be after Y2-07-31
Contract STARTCON 2 Contract.STARTCON must not be after
Contract.ENDCON.
Contract STARTCON 3 Contract.STARTCON must exist where
Contract.TERMS = 1 or 2.
Contract STARTCON 4 Contract.STARTCON must be null where
ReasonForNull = 1
Contract STARTCON 5 Where Contract.STARTCON is null ReasonForNull
must equal 1.
Contract STARTCON 6 Where Contract.STARTCON exists it must be
afterPerson.BIRTHDTE where it exists or after (Y1-100)-07-31 where
Person.BIRTHDTE does not exist.
Contract STARTCON 7 Where Contract.STARTCON must be before or on
Person.DATELEFT where all Contract.TERMS = 1 or 2
Contract TCHWLH 1 Contract.TCHWLH must not exist for
institutions in England, Scotland or Northern Ireland.
Contract TCHWLH 2 Contract.TCHWLH must exist for Welsh
institutions where (Contract.ACEMPFUN = 1 or 3) and Contract.TERMS = 1
or 2.
Contract TCHWLH 3 Where Contract.TCHWLH must not equal 1 where
Person.ABLWELSH = 2.
Contract TERMS 1 Where Contract.MOEMP = 5 then
Contract.TERMS must equal 3.

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_HER217 - HESA CONTRACT Record Validation Check &1 &2 &3 failed ?

  The SAP error message HRPSGB_HER217 indicates that there is a validation issue with the HESA (Higher Education Statistics Agency) contract record in the HR module. This error typically arises during the process of submitting HESA data, which is required for compliance with UK higher education reporting standards.
  Cause:
  The error message "HESA CONTRACT Record Validation Check &1 &2 &3 failed" suggests that there are specific validation checks that have not been met for the contract record. The placeholders (&1, &2, &3) usually represent specific fields or criteria that have failed validation. Common causes for this error may include:
  
  Missing or Incorrect Data: Required fields in the contract record may be missing or contain invalid data.
  Data Format Issues: The data entered may not conform to the expected format (e.g., date formats, numeric values).
  Inconsistent Data: There may be inconsistencies between the contract record and other related records (e.g., employee details, job details).
  Configuration Issues: The system configuration for HESA reporting may not be set up correctly.
  
  Solution:
  To resolve the HRPSGB_HER217 error, you can follow these steps:
  
  
  Review the Error Message: Check the specific details provided in the error message (the values of &1, &2, &3) to identify which fields are causing the validation failure.
  
  
  Check Data Completeness: Ensure that all required fields in the HESA contract record are filled out correctly. This includes checking for any mandatory fields that may be empty.
  
  
  Validate Data Formats: Verify that the data entered adheres to the required formats. For example, ensure that dates are in the correct format and that numeric fields do not contain invalid characters.
  
  
  Cross-Check Related Records: Look for inconsistencies between the contract record and other related records, such as employee or job details. Ensure that all related data is consistent and accurate.
  
  
  Consult Documentation: Refer to the HESA reporting guidelines and SAP documentation for specific requirements related to contract records.
  
  
  System Configuration: If the issue persists, check the configuration settings for HESA reporting in your SAP system. Ensure that all necessary settings are correctly configured.
  
  
  Testing: After making corrections, re-run the validation checks to see if the error is resolved.
  
  
  Seek Support: If you are unable to resolve the issue, consider reaching out to your SAP support team or consulting with an SAP HR expert who has experience with HESA reporting.
  
  
  Related Information:
  
  HESA Reporting: HESA is responsible for collecting data from higher education institutions in the UK. Understanding the requirements for HESA reporting is crucial for compliance.
  SAP HR Module: Familiarity with the SAP HR module and its functionalities can help in troubleshooting issues related to employee records and reporting.
  SAP Notes: Check for any relevant SAP Notes that may address known issues or provide additional guidance on HESA reporting errors.
  
  By following these steps, you should be able to identify and resolve the validation issues causing the HRPSGB_HER217 error.