How To Fix HRPAYRULOG029 - Wage type &1 has split &2 to RUDAT table

HRPAYRULOG029 - Overview

• Message type: E = Error

• Message class: HRPAYRULOG - Messages for HRUCALC0 logging

• Message number: 029

• Message text: Wage type &1 has split &2 to RUDAT table

What causes this issue?

The option TAXDT is activated and the system tries to process the
primary wage type according to Payment Date Classification, taking into
account data from table RUDAT, which uses the 2nd country split to link
the data with the primary wage type. Possibly the 2nd country split is
used by the system for another purpose.

System Response

By default, the system can continue calculation of the 2nd country split
with a warning for wage type &V1& in the payroll log.

How to fix this error?

Contact your system administrator.

Procedure for System Administrators

Check your payroll schema to clear the reason for the primary wage type
having the split.
<ZH>Note:</> You can change message type using Customizing activity
<DS:SIMG.OHARUBP_PY_TAX_049>Customize Types of Message in Payroll Run
</>.

Error message extract from SAP system. Copyright SAP SE.

HRPAYRULOG029 - Details

• The SAP error message HRPAYRULOG029 indicates that a wage type has been split into multiple entries in the RUDAT table, which is used for storing wage type data in the payroll process. This can occur due to various reasons, such as changes in payroll periods, retroactive accounting, or specific configurations in the payroll schema.
  
  Cause:
  
  Wage Type Configuration: The wage type may be configured to split based on certain criteria, such as different periods or conditions.
  Retroactive Accounting: If there are changes in employee data or wage types that affect previous payroll periods, the system may need to split the wage type to account for these changes.
  Payroll Schema: The payroll schema may have rules that dictate how wage types are processed, leading to splits in the RUDAT table.
  Data Inconsistencies: Inconsistencies in master data or infotypes related to the employee can also lead to this error.
  
  
  Solution:
  
  Check Wage Type Configuration: Review the configuration of the