How To Fix HRPSGB_HER182 - Staff ID as send to HESA is different (&1)

HRPSGB_HER182 - Overview

• Message type: E = Error

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

• Message number: 182

• Message text: Staff ID as send to HESA is different (&1)

What causes this issue?

The <DS:DE.P08_HESA_STAFFID>HESA staff ID</> that was sent to HESA for
the contract(s) valid until &V2& according to infotype HESA Submitted
Data (0616) was different: &V1&.

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?

Check the data.
If the data in infotype HESA Submitted Data is incorrect, disregard the
warning now:
If the data in infotype HESA Submitted Data is incorrect because the
data has been entered manually in the course of data migration, you
should correct it there. Otherwise you will get a similar message when
you run the HESA Staff Return program (RPUHESG0).
You should resolve the problem.
The HESA Staff ID is supposed to not change over the course of an
employees work with Higher Education Institutions.

Procedure for System Administrators

Error message extract from SAP system. Copyright SAP SE.

HRPSGB_HER182 - Details

• The SAP error message HRPSGB_HER182 indicates that there is a discrepancy between the Staff ID that has been sent to HESA (Higher Education Statistics Agency) and the Staff ID that is recorded in the SAP system. This error typically arises during the process of submitting staff data to HESA, which is a requirement for higher education institutions in the UK.
  
  Cause:
  
  
  Data Mismatch: The Staff ID in the SAP system does not match the Staff ID that is being sent to HESA. This could be due to:
  
  Manual entry errors.
  Changes in staff records that have not been updated in the HESA submission.
  Incorrect mapping of Staff IDs between systems.
  
  
  
  Timing Issues: If there have been recent changes to staff records (e.g., new hires, terminations, or changes in roles), and these changes have not been reflected in the HESA submission.
  
  
  
  Configuration Issues: There may be issues with the configuration of the HESA reporting module in SAP, leading