How To Fix HRPAYUSCALC357 - Employee skipped from UOTX0 processing. Invalid C1 entry

HRPAYUSCALC357 - Overview

• Message type: E = Error

• Message class: HRPAYUSCALC - Messages for payroll log RPCALCU0

• Message number: 357

• Message text: Employee skipped from UOTX0 processing. Invalid C1 entry

What causes this issue?

You attempted to execute a payroll for an employee using the PY-US-TX:
Freeze existing taxes during cross-year retrocalculation (UOTX0 payroll
function), but the system could not find a corresponding entry in the
current cost assignment table, causing the system to skip employee from
UOTX0 processing. The cost assignment index for the wage type in the
original period does not exist in none of the cost assignment tables
(C0, WPBP or C1).

The system issues an error message and will not allow you to continue with this transaction until the error is resolved.

System Response

The employee processed has a wage type with an invalid cost assignment
split (i.e. the cost assignment referred to that split does not exist).
As a result, the system creates an entry in Cost Assignment from
Different Infotypes (C1) table with blank value, which is invalid.

How to fix this error?

To verify why this message is displayed, proceed as follows:
+,,Check why the cost assignment was not found.
+,,In case of inconsistencies, it may be that other parts in payroll are
causing this issue.
+,,PC_PAYRESULT transaction can be used to verify the payroll results
and check if any entries are missing.
+,,These inconsistencies must be solved in order to run payroll
accordingly
Example
<ZH>Freeze existing taxes during cross-year retrocalculation</>
In the last payroll period of 2019, you paid employee B a gross-up
amount. In this last payroll period of 2019, employee B has only one
entry in WPBP table, which has the cost assignment split (APZNR) 01.
However, in the RT table for this same last payroll period of 2019, this
gross-up wage type had the cost assignment split APZNR as 02.
Whenever you run a cross-year retrocalculation back to 2019, the system
will create an entry in C1 table with blank company code. This is
incorrect.

Error message extract from SAP system. Copyright SAP SE.

Smart SAP Assistant

• What is the cause and solution for SAP error message HRPAYUSCALC357 - Employee skipped from UOTX0 processing. Invalid C1 entry ?

  The SAP error message HRPAYUSCALC357 indicates that an employee was skipped during the processing of the UOTX0 (US Payroll) due to an invalid C1 entry. This error typically arises in the context of payroll processing in the United States, particularly when dealing with payroll calculations and the associated infotypes.
  
  Cause:
  The error can be caused by several factors, including:
  
  
  Invalid C1 Entry: The C1 entry refers to a specific configuration or data entry related to the employee's payroll. If this entry is missing, incorrect, or not properly configured, the system will skip the employee during processing.
  
  
  Missing Infotypes: The employee may not have the necessary infotypes (e.g., infotype 0008 for basic pay, infotype 0014 for recurring payments, etc.) that are required for payroll processing.
  
  
  Incorrect Payroll Configuration: There may be issues with the payroll configuration settings in the system that affect how the C1 entries are processed.
  
  
  Data Inconsistencies: There could be inconsistencies in the employee's