How To Fix 5G219 - Migration not possible: No unique pay date between & and &

5G219 - Overview

• Message type: E = Error

• Message class: 5G - HR: Messages for Britain

• Message number: 219

• Message text: Migration not possible: No unique pay date between & and &

What causes this issue?

The system needs to find a unique pay date between the begin and end
dates from the entry in the table <LS>National Insurance Data Take-on
</>(T5G_NIDTO). However, the date range entry spans over two or more
pay dates.

System Response

The system rejects this entry, as the correct pay date is unclear.

How to fix this error?

Correct the entry in the table <LS>National Insurance Data Take-on
</>(T5G_NIDTO) so that there is a unique pay date between the begin and
end date.
Re-run this <LS>Migration report for NI Data Take-on table
</>(RPUMNIG0).

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 5G219 - Migration not possible: No unique pay date between & and & ?

  The SAP error message 5G219 indicates that during a migration process, the system has encountered a situation where there is no unique pay date between the specified date range. This typically occurs in the context of payroll processing or data migration where the system expects a unique pay date for the records being processed.
  
  Cause:
  
  Multiple Pay Dates: The error arises when there are multiple pay dates for the same employee within the specified date range. The system requires a unique pay date to proceed with the migration.
  Data Inconsistency: There may be inconsistencies in the payroll data, such as overlapping payroll periods or incorrect entries in the payroll master data.
  
  Configuration Issues: The payroll configuration may not be set up correctly, leading to multiple pay dates being generated for the same period.
  
  
  Solution:
  
  Check Payroll Data: Review the payroll data for the employees involved in the migration. Look for any duplicate pay dates or overlapping