How To Fix HRPSGB200 - For pers. number &1 no records after &2 will be stored in Archive table

HRPSGB200 - Overview

• Message type: E = Error

• Message class: HRPSGB - HR PS Great Britain

• Message number: 200

• Message text: For pers. number &1 no records after &2 will be stored in Archive table

In TPS Annual return only 9 records can be returned in mechanised
format for each employee. For personnel number &V1& the record
starting on &V2& and finising on &V3& is the 10th record generated.
Starting from this record all consequent records will not be stored in
archive table and will be only displayed in ALV display.
Some manual processing is required for this employee.You can either
exclude this employee from the selection on the selection screen of the
report and return all of his /hers records to TP manually. In this case
you should also return 'Additonal contributions' and 'Appointment'
records, if required, manually. Or you can return manually only the
additional records, not stored in the archive table.

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.

HRPSGB200 - Details

• The SAP error message HRPSGB200 indicates that for a specific personnel number, there are no records available after a certain date that can be stored in the archive table. This typically occurs during the archiving process in the Human Resources (HR) module, particularly when trying to archive employee data.
  
  Cause:
  
  
  No Records Available: The primary cause of this error is that there are no relevant records for the specified personnel number after the given date. This could be due to:
  
  The employee has no data entries after the specified date.
  The records may have already been archived or deleted.
  The date specified for archiving is too early, and all records are before that date.
  
  
  
  Incorrect Configuration: There may be issues with the archiving configuration or selection criteria that do not match any existing records.
  
  
  Data Integrity Issues: There could be data integrity issues in the HR module that prevent records from being archived.
  
  
  
  Solution:
  
  
  Check Records: Verify if there