How To Fix HRPAYDEST294 - Pension basis &1 in period &2 to &3 is not unique.

HRPAYDEST294 - Overview

• Message type: E = Error

• Message class: HRPAYDEST - Message Class: Taxes Germany

• Message number: 294

• Message text: Pension basis &1 in period &2 to &3 is not unique.

What causes this issue?

The employment tax statement data contain the pension basis &V1& more
than once. These cannot be grouped as the start and end date of the
entries for this pension basis are not the same in the statement period.

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 if it is necessary to transfer the assessment bases for the
pension exemption amount of the second and subsequent basis. Use d
ifferent <ZK>Wage Type Groups Pension Payments</> to separate the
pension bases.

Procedure for System Administrators

How can this happen?

Infotype record <ZK>Tax Data</> (0012) on the statement contains the
following entries for pension bases for statement year 2019:
Basis of first pension payment
Start date: 1/1/2018
End date:
Decisive year: 2004
Assignment payments: V001
Regular pension payment: EUR 200,00
Basis of second pension payment
Start date: 10/1/2018
End date: 8/31/2019
Decisive year: 2004
Assignment payments: V001
Regular pension payment: EUR 300,00
Both pension bases use assignment V001. The regular pension payments of
this assignment are stored in wage type /4VL and included on the
statement for the first basis.
As the basis for the second pension payment ended prematurely in
statement year 2019, the bases cannot be grouped.
Use a different payments assignment for the basis for the second pension
payment (with different pension wage types).

Error message extract from SAP system. Copyright SAP SE.

HRPAYDEST294 - Details

• The SAP error message HRPAYDEST294 indicates that there is a problem with the pension basis for a specific employee in a given period. This error typically arises when the system finds multiple entries for the pension basis that should be unique for the specified period. Here’s a breakdown of the cause, potential solutions, and related information:
  
  Cause:
  
  Duplicate Entries: The most common cause of this error is that there are duplicate entries for the pension basis in the specified period. This can happen due to incorrect data entry or issues during data migration.
  Incorrect Configuration: There may be configuration issues in the payroll settings that lead to multiple pension basis entries being created for the same period.
  Data Inconsistencies: If there are inconsistencies in the employee master data or payroll results, it can lead to this error.
  
  
  Solution:
  
  
  Check for Duplicates:
  
  Go to the relevant infotype (e.g., IT 0580 for pension data) and check for duplicate entries