CRET@: I-51/54 Shouldn't Be Printed in Compl LIQ If There Isn't Any Delta (Doc ID 2187591.1)

Last updated on JUNE 12, 2017

Applies to:

PeopleSoft Enterprise HCM Global Payroll Spain - Version 9.1 and later
Information in this document applies to any platform.

Symptoms

ACTUAL BEHAVIOR
---------------
For daily employee with monthly contribution the XML of bases for L03 is showing a slice with just I-51 and I-54 values if there isn't any other delta.

When a file is generated L03 has to be indicated per employee and per segment the data and corresponding I54 (between 1 to 5) value.
It was found the following:
Case 1: In the monthly payroll has been recalculated previous payroll for employees but there is one that has no differences in payroll or bases.
These employees have daily but monthly remuneration groups.
PeopleSoft see there is a recalculation for these employees and generate the file Cret@ leads to these employees, but as there are no differences in bases, the sections takes only the data I51M.
TGSS response against this data is treated as an error.

Case 2: Employees who had different absences in previous months .
An example of an employee with daily and monthly salary group with L03 to January presented in February with paternity January 4 to 16.
PeopleSoft generates correct section, but the segment of paternity (day 4 to 16) generates the section with the data I51M (no carries data base because not applicable).
As in the previous case, the response of TGSS is that this segment is wrong.

A similar issue was found for I54:
For an employee with a pay deduction from February, calculating the salary it generates L03 for the Cret@ with negative bases and the indicator is I 54. It's the correct one.
The XML generates a file with only the indicator I 54.
What we get from the SILTRA C9751 error, we need to complete some base for the optional ones.

STEPS
-----------------------
The issue can be reproduced at will with the following steps:
1. Setup a daily employee with monthly contribution.
2. Run a payroll and finalize it
3. Enter manually a retro trigger affecting that month
4. Run following payroll
5. Check XML of bases

Cause

Sign In with your My Oracle Support account

Don't have a My Oracle Support account? Click to get started

My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms