GPES: When Loading the Cret@ XML Files, it Duplicates the Liquidation
(Doc ID 2956280.1)
Last updated on JULY 26, 2023
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
When the Payroll Administrator uses one SSN (Social Security Number) for two different EMPLIDs (for instance an Employee with an Employee ID is terminated and Rehired
with another Employee ID), the system just selects the first row, and it is not checking if the employee is terminated or not.
This is a problem as there are users that creates the new employee ID in case the Employee is terminated and rehired again.
Steps to replicate the issue:
1. When Cret@ file is printed for the first time, a new line is written at GPES_CRT_LQ_TBL which records the status of liquidation
Global Payroll & Absence Mgmt > Social Security/Insurance > Print Cret@ Files ESP
2. Global Payroll & Absence Mgmt > Social Security/Insurance > Review Cret@ Liquidations ESP
Then, a Calculation Details file is loaded.
This causes a new line is recorded with the same SSN Employer, instead of makes an update
3. If a new Cret@ file is created, the file has a liquidation duplicated.
Query the record view GPES_CRT_LIQ0_VW, with the node S1 04 and it will return twice the same liquidation.
Steps to replicate the issue:
1. When Cret@ file is printed for the first time, a new line is written at GPES_CRT_LQ_TBL which records the status of liquidation
Global Payroll & Absence Mgmt > Social Security/Insurance > Print Cret@ Files ESP
2. Global Payroll & Absence Mgmt > Social Security/Insurance > Review Cret@ Liquidations ESP
Then, a Calculation Details file is loaded.
This causes a new line is recorded with the same SSN Employer, instead of makes an update
3. If a new Cret@ file is created, the file has a liquidation duplicated.
Query the record view GPES_CRT_LIQ0_VW, with the node S1 04 and it will return twice the same liquidation.
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 |