How To Fix HRPSGB_HER206 - HESA INTERDEPENDENCY Validation Check &1 failed

SAP Error Message - Details

• Message type: E = Error

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

• Message number: 206

• Message text: HESA INTERDEPENDENCY Validation Check &1 failed

What causes this issue?

The employee has had PERSON and CONTRACT(s) records created that fails
one of the validation checks below;

The system issues an error message and will not allow you to continue with this transaction until the error is resolved.

Validation Errors - Number, Text and Specification
40252001 - No two records on the person table can have the same STAFFID
No two records on the person table can have the same STAFFID
40252002 - For every STAFFID returned on the person table there must be
at least one record on the contract table
For every STAFFID returned on the person table there must be at least
one record on the contract table
40252003 - For every STAFFID on the contract table there must be one
record on the person table
For every STAFFID on the contract table there must be one record on the
person table
40252004 - The combination of CONTID and STAFFID must be unique within
an institution
The combination of CONTID and STAFFID must be unique within an
institution
40252006 - If any contract record for this person record has (ACT1, ACT2
or ACT3 = 1, 2A, 2B, 3A, 3B, 3C and TERMS<>3) then PREVEMP must not be
XX
PREVEMP must be completed with a valid code other than the default code
when any of ACT1, ACT2, or ACT3 = '1', '2' or '3' and the member of
staff is not classed as 'atypical'
40252007 - If PREVEMP=01 and (DATEFHEI>YYYY0731 (where YYYY is the
starting year of the current return) and DATEFHEI<>99991231) and any
contract record for this person has (ACT1, ACT2 or ACT3 = 1, 2A, 2B, 3A,
3B, 3C and TERMS<>3) then PREVHEI must not be XXXX
PREVHEI must be completed with a valid code other than the default code
when any of ACT1, ACT2, or ACT3 = '1', '2' or '3' and PREVEMP ='01' and
DATEFHEI > YYYY0731 (where YYYY is the starting year of the current
return) (excluding 99991231) and the member of staff is not classed as
'atypical'
40252008 - If any contract record for this person has (ACT1, ACT2 or
ACT3 = 1, 2A, 2B, 3A, 3B, 3C and TERMS<>3) then HQHELD must not be XX
HQHELD must be completed with a valid code other than the default code
when any of ACT1, ACT2, or ACT3 = '1', '2' or '3' and the member of
staff is not classed as 'atypical'
40252009 - If (HQHELD is 01, 02, 03, 09, 11, 12, 19, 21, 22 or 29) and
any contract record for this person has (ACT1, ACT2 or ACT3 = 1, 2A, 2B,
3A, 3B, 3C and TERMS<>3) then ACCDIS1 must not be XXXX
ACCDIS1 must be completed with a valid code other than the default code
when any of ACT1, ACT2, or ACT3 = '1', '2' or '3' and HQHELD= '01 to
03', '09', '11 to 12', '19', '21', '22' or '29' and the member of staff
is not classed as 'atypical'
40252010 - If any contract record for this person has ((ACT1=2A and
CCENTRE1=01- 09 or 29) or (ACT2 =2A and CCENTRE2=01- 09, or 29) or (ACT3
= 2A and CCENTRE3=01- 09, or 29) and TERMS <> 3 then REGBODY must not be
XX
REGBODY must be completed with a valid code other than the default code
when any of ACT1, ACT2, or ACT3 = '2A' and the related cost centre field
has been coded '01-09' or '29' and the member of staff is not classed as
'atypical'
40252011 - If this is a Welsh institution and any contract record for
this person has (ACT1, ACT2 or ACT3 = 2A and TERMS<>3) then ABLWELSH
must not be X
ABLWELSH must be completed with a valid code other than the default code
when the contract held is with a Welsh institution and any of ACT1,
ACT2, or ACT3 ='2A' and the member of staff is not classed as 'atypical'
40252012 - If DATELEFT<>99991231 and any of the contract records for
this person has (ACT1, ACT2, ACT3 = 1, 2A, 2B, 3A, 3B, 3C and TERMS<>3)
then LEDEST must not be XX
LEDEST must be completed with a valid code other than the default code
when any of ACT1, ACT2, or ACT3= '1', '2' or '3' and the member of staff
has left the HEI and the member of staff is not classed as 'atypical'
40252013 - If any contract record for this person has (ACT1, ACT2, ACT3
= 2A and TERMS <>3) then RESACT must not be X
RESACT must be completed with a valid code other than the default code
when any of ACT1, ACT2, ACT3= '2A' and the member of staff is not
classed as 'atypical'
40252017 - If sum of CONFTE for all the contract records for this person
is greater than 200 then fail
Check to reject any individuals for whom the sum of their CONFTE for all
contracts is more than 200%
40252018 - Incorrect instid in file
Incorrect INSTID in data
New Validation Errors - Number, Text and Specification
40252036 - If DATELEFT <> 99991231 and TERMS<>3 then all of the contract
records, except where TERMS=3, for this person must have ENDCON
<>99991231
If the member of staff has left the HEI (DATELEFT <> 99991231) and the
member of staff is not classed as 'atypical' then all the standard (TERM
<>3) contract records for this person must have ended (ENDCON<>99991231)
40252037 - If a member of staff was included in the previous Staff
person table, and if any contract record for this person had (ACT1,
ACT2, ACT3 = 1, 2A, 2B, 3A, 3B or 3C and TERMS <>3) and DATELEFT =
99991231 in that
return, a record must be included on the current STAFF person table
Any member of staff who was not recorded as a leaver in the previous
with any of ACT1, ACT2, or ACT3 = '1', '2' or '3' and the member of
staff is not classed as 'atypical' must be returned in this years Staff
data
40252038 - If a member of staff was NOT included in the previous Staff
person table, and if any contract record for this person has (ACT1,
ACT2, ACT3 = 1, 2A, 2B, 3A, 3B or 3C and TERMS <>3), then DATEFHEI <>
99991231
Any new member of staff with any of ACT1, ACT2, or ACT3 = '1', '2' or
'3' and the member of staff is not classed as 'atypical', must have a
valid date other than the default date
40252043 - If field 7 MOEMP is 1, and field 23 ENDCON = '31-DEC-9999'
and field 22 STARTCON < '01-AUG-04', then field 9 CONFTE must NOT be <
080.0
Full-time contract with CONFTE of less than 080.0 (not a starter or
leaver within the reporting period)
40252044 - If field 7 MOEMP is 3, 4 or 5 then field 9 CONFTE must not be
100.0
CONFTE must NOT be 100.0 for a part-time or atypical contract
Validation Warnings - Number, Text and Specification
40252020 - Comparing the previous and current Staff returns, if the same
STAFFID appears in both returns, then GENDER must be consistent
Comparing previous Staff data with this years Staff data, GENDER must be
the same
40252021 - Comparing the previous and current Staff returns, if the same
STAFFID appears in both returns, then BIRTHDTE must be consistent
Comparing previous Staff data with this years Staff data, BIRTHDTE
should be the same
40252023 - If the same STAFFID appears in both the previous and current
Staff returns, and HQHELD is not coded 99 (unknown) in previous return,
then HQHELD must not be coded 99 (unknown) in the current return for the
same STAFFID
Comparing previous Staff data with this years Staff data, HQHELD is not
known this year
40252024 - If the same STAFFID appears in both the previous and the
current Staff returns, and NATION was coded other than 1782 (not known)
last year, then NATION should be consistent
Comparing previous Staff data with this years Staff data, are you sure
NATION should change?
40252025 - If all of the contract records for this person have (ENDCON
<>99991231 and TERMS<>3) then DATELEFT must not be 99991231
DATELEFT must be completed with a valid code other than the default code
when the member of staff has left the HEI and the member of staff is not
classed as 'atypical'
New Validation Warnings - Number, Text and Specification
40252026 - Comparing the previous and current Staff returns, if the same
STAFFID appears in both returns, then DATEFHEI must be consistent
Comparing previous Staff data with this years Staff data, DATEFHEI
should be the same
40252027 - Comparing the previous and current Staff returns, if the same
STAFFID appears in both returns, and ETHNIC was coded other than 99 (not
known) or 98 (information refused) last year, then ETHNIC must be
consistent
Comparing previous Staff data with this years Staff data, ETHNIC should
be the same
40252028 - Comparing the previous and current Staff returns, if the same
STAFFID appears in both returns, and DISABLED was coded other than 9
(information not provided), then DISABLED should be consistent
Comparing previous Staff data with this years Staff data, are you sure
DISABLED should change?
40252029 - Comparing the previous and current Staff returns, if the same
STAFFID appears in both returns, then PREVHEI must be consistent
Comparing previous Staff data with this years Staff data, PREVHEI should
be the same
40252030 - Comparing the previous and current Staff returns, if the same
STAFFID appears in both returns, then PREVEMP must be consistent
Comparing previous Staff data with this years Staff data, PREVEMP should
be the same
40252031 - Comparing the previous and current Staff returns, if the same
STAFFID appears in both returns, then ACCDIS1 must be consistent
Comparing previous Staff data with this years Staff data, ACCDIS1 should
be the same
40252032 - Comparing the previous and current Staff returns, if the same
STAFFID appears in both returns, then ACCDIS2 must be consistent
mComparing previous Staff data with this years Staff data, ACCDIS2
should be the same
40252033 - Comparing the previous and current Staff returns, if the same
STAFFID appears in both returns, and NATID1 was coded other than R
(information refused) or U (unknown), then NATID1 should be consistent
Comparing previous Staff data with this years Staff data, are you sure
NATID1 should change?
40252034 - Comparing the previous and current Staff returns, if the same
STAFFID appears in both returns, and NATID2 was coded other than R
(information refused) or U (unknown), then NATID2 should be consistent
Comparing previous Staff data with this years Staff data, are you sure
NATID2 should change?
40252035 - Comparing the previous and current Staff returns, if the same
STAFFID appears in both returns, then REGBODY should be consistent
Comparing previous Staff data with this years Staff data, are you sure
REGBODY should change?
40252039 - If a member of staff was included in the previous Staff
person table, and if any contract record for this person has (ACT1,
ACT2, ACT3 = 1, 2A, 2B, 3A, 3B or 3C and TERMS <>3), then DATEFHEI <>
99991231
Any existing member of staff with any of ACT1, ACT2, or ACT3 = '1', '2'
or '3' and the member of staff is not classed as 'atypical', should have
a valid DATEFHEI date other than the default date
40252040 - (If DATELEFT>= YYYY0801 (where YYYY is the starting year of
the current return) and DATELEFT<>99991231) and any contract record for
this person record has (ACT1, ACT2, ACT3 = 1, 2A, 2B, 3A, 3B, 3C and
TERMS<>3) then LEDEST should not be 99
Any member of staff that has left during the reporting period with any
of ACT1, ACT2, or ACT3 = '1', '2' or '3' and the member of staff is not
classed as 'atypical', should have a valid LEDEST code between 01-15,
21, 22, 31
40252041 - (If DATEFHEI>= YYYY0801 (where YYYY is the starting year of
the current return) and DATEFHEI<>99991231) and any contract record for
this person record has (ACT1, ACT2, ACT3 = 1, 2A, 2B, 3A, 3B, 3C and
TERMS<>3) then PREVEMP should not be 99
Any new member of staff with any of ACT1, ACT2, or ACT3 = '1', '2' or
'3' and the member of staff is not classed as 'atypical', should have a
valid PREVEMP code between 01-21
40252042 - If ENDCON>YYYY0731 (where YYYY is the starting year of the
current return) for this contract then CONFTE must not be 000.0
CONFTE should NOT be 000.00 unless an exception has been agreed for this
STAFFID
40252045 - If field 7 MOEMP is 3 or 4, then field 9 CONFTE should not be
between 080.0 - 099.9
CONFTE should NOT be between 080.00 and 099.9 for a part-time contract
40252046 - If field 7 MOEMP is 5, then field 9 CONFTE must not be
between 020.0 - 099.9
CONFTE should NOT be between 020.00 and 099.9 for an atypical contract
40252047 - Comparing the previous and current Staff returns the
percentage change in field 17 SALREF between previous and current
should not be more that 25%
Comparing previous Staff data with this years Staff data, are you sure
SALREF should change?
80252054 - The field SALREF contains a value greater than MAXSAL in the
GRADE table
80252055 - The field SALREF contains a value less than MINSAL in the
GRADE table
80252056 - The field SPOINT contains a value greater than MAXSPINE in
the GRADE table
80252057 - The field SPOINT contains a value less than MINSPINE in the
GRADE table
80252053 - GRADID must contain a valid entry from INSTGRAD, 400, 410,
420, 430, 500, 510, 520, 900 or XXXXXXXXXX
80252066 - Where TERMS<>3, If MAXSAL is not XXXXXXX and MAXSPINE is not
F99, then the corresponding SALREF must not be XXXXXXX.
80252067 - Where TERMS<>3, If MAXSPINE is not XXX or F99, then the
corresponding SPOINT must not be XXX.
10025098 - Comparing last year's staff data with this year's staff data,
there is a significant change in the number of professorial roles.
10025103 - Comparing last year's staff data with this year's staff data,
if the same STAFFID appears in both returns, and last year's GENDER = 0,
then GENDER should not = 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 and
contract records.

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

Error message extract from SAP system. Copyright SAP SE.

Smart SAP Assistant

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

  The SAP error message HRPSGB_HER206 related to the HESA (Higher Education Statistics Agency) interdependency validation check typically occurs in the context of processing HESA returns in the SAP HR module, particularly for UK higher education institutions. This error indicates that there is a validation issue with the data being submitted, specifically regarding interdependencies between different fields or records.
  Cause:
  The error message HRPSGB_HER206 usually arises due to one or more of the following reasons:
  
  
  Data Inconsistencies: There may be inconsistencies or missing data in the fields that are interdependent. For example, if one field requires a specific value based on another field's value, and that condition is not met, the validation will fail.
  
  
  Incorrect Configuration: The configuration settings for HESA reporting may not be set up correctly, leading to validation errors.
  
  
  Missing Required Fields: Certain required fields may not be populated, which can cause the validation to fail.
  
  
  Business Rules Violation: The data submitted may violate specific business rules defined for HESA reporting, such as incorrect combinations of data.
  
  
  Solution:
  To resolve the HRPSGB_HER206 error, you can take the following steps:
  
  
  Review the Error Message: Check the detailed error message for specific information about which validation check failed. The message may provide a reference to the specific fields or records that are causing the issue.
  
  
  Validate Data: Go through the data entries related to the HESA return and ensure that all interdependent fields are populated correctly. Look for any inconsistencies or missing values.
  
  
  Check Configuration: Review the configuration settings for HESA reporting in your SAP system. Ensure that all necessary settings are correctly configured according to the latest HESA guidelines.
  
  
  Consult Documentation: Refer to the HESA documentation or SAP notes related to HESA reporting for any specific requirements or updates that may affect your data.
  
  
  Test with Sample Data: If possible, test the validation with a smaller set of sample data to identify the specific records causing the issue.
  
  
  Seek Support: If you are unable to resolve the issue, consider reaching out to your SAP support team or consulting with SAP experts who specialize in HESA reporting.
  
  
  Related Information:
  
  HESA Reporting: HESA is responsible for collecting, analyzing, and disseminating data about higher education in the UK. Institutions must comply with specific reporting requirements.
  SAP Notes: Check SAP Notes for any known issues or patches related to HESA reporting and the specific error message.
  Training and Documentation: Ensure that staff involved in data entry and reporting are trained on the requirements and processes for HESA submissions.
  
  By following these steps, you should be able to identify and resolve the cause of the HRPSGB_HER206 error message.