How To Fix HRGB_GBSXP003 - Period history corrupted for absence &1 between &2 - &3

HRGB_GBSXP003 - Overview

• Message type: E = Error

• Message class: HRGB_GBSXP - Message for GBSXP

• Message number: 003

• Message text: Period history corrupted for absence &1 between &2 - &3

What causes this issue?

The internal table PERIOD_HISTORY contains all the contiguous(linked)
absences that are relevant to the current absence being processed
through GBSXP.
In other words, if a Period of Incapacity for Work (PIW) (A) links to
an earlier PIW (B), and from that one to an earlier PIW (C), then:
PERIOD_HISTORY will hold A if GBSXP is processing A.
PERIOD_HISTORY will hold A and B if GBSXP is processing B
PERIOD_HISTORY will hold A, B and C if GBSXP is processing C
Therefore, as an absolute minimum, PERIOD_HISTORY must contain the
current absence that is being processed. If this is not the case, then
this error message is raised.

System Response

A permanent error has occurred during the processing of the payroll
for this employee.

How to fix this error?

1) Re-process the employee through payroll after checking that the
Master Data Change Date (IT0003-RRDAT) has been updated to re-process
this date.
2) Check that your payroll subschema for "Up to Gross" (i.e. a copy of
GT00) respects the order and structure of the SAP-delivered payroll
subschema GT00.
3 ) If you cannot resolve this issue, raise an OSS message stating that
this error has occurred.

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.

HRGB_GBSXP003 - Details

• The SAP error message HRGB_GBSXP003 indicates that there is a corruption in the period history for an absence record in the system. This typically occurs when there are inconsistencies in the data related to employee absences, such as missing or incorrect entries in the absence records.
  
  Cause:
  
  Data Inconsistencies: The absence records may have been altered or deleted incorrectly, leading to gaps or overlaps in the data.
  Incorrect Configuration: Configuration settings in the absence management module may not align with the actual data.
  System Errors: Bugs or issues during data migration or updates can lead to corrupted records.
  Manual Data Entry Errors: Incorrect manual entries by users can also lead to this error.
  
  
  Solution:
  
  Check Absence Records: Review the absence records for the employee in question. Look for any missing or overlapping entries in the specified period.
  Data Correction: If you find any inconsistencies, correct the absence records. This may involve adding missing records or adjusting existing ones.
  Use