GPESP: Incorrect Calculation of Earning "LIQ PXTR JUL" for Employees Hired in December and Terminated in February
(Doc ID 2862106.1)
Last updated on JUNE 08, 2022
Applies to:
PeopleSoft Enterprise HCM Global Payroll Spain - Version 9.2 to 9.2 [Release 9]Information in this document applies to any platform.
Symptoms
An incorrect calculation of the element "LIQ PXTR JUL" has been noticed for monthly employees that have been hired in December and terminated in February.
If the payroll is run for a termination in March, the results are correct. Likewise, in case of daily employees, the element is correctly calculated after running payroll.
Steps to replicate the issue:
1. Update definition of the Labor Agreement to have two extra periods with duration 12 months.
Navigation: Set Up HCM > Product Related > Global Payroll & Absence Mgmt > Framework > Organizational > Labor Agreement ESP > Extra Period Definition
o June extra: From 7 , duration 12, paid on month 6
o December extra: From 1 , duration 12 , paid on month 12
o Both paid with payment month compensation
2. Assign the labor agreement to employee (he/she needs to be setup as monthly employee -> on Update contract ESP page)
Navigation: Workforce Administration > Job Information > Contract Administration > Update Contracts ESP > Contract Data > AFI Events
3. Terminate employee as of December 2019
Navigation: Workforce Administration > Job Information > Job Data
4. Rehire on December 1st 2020
5. Run December extra period. Results are correct.
Navigation: Global Payroll & Absence Mgmt > Absence and Payroll Processing > Calculate Absence and Payroll > Calculate Absence and Payroll
6. Run December payroll
7. Run January 2021 Payroll
8. Terminate employee as of Feb 20th
Navigation: Workforce Administration > Job Information > Job Data
9. Run February and check the two liquidation earnings:
Issue: paid days for June extra period "LIQ PXTR JUL" are incorrectly calculated as it is adding additional 30 days, producing 109 days instead of 79 days
Changes
Cause
To view full details, sign in with your My Oracle Support account. |
|
Don't have a My Oracle Support account? Click to get started! |
In this Document
Symptoms |
Changes |
Cause |
Solution |
References |