STP: Payee YTD Repeated In XML For Multiple CAL_RUN_IDs When Total Period Is Paid In Multiple Parts
(Doc ID 3004467.1)
Last updated on FEBRUARY 04, 2025
Applies to:
PeopleSoft Enterprise HCM Global Payroll Australia - Version 9.2 and laterInformation in this document applies to any platform.
Goal
When a Payee is paid in multiple CAL_RUN_IDs in the same pay period due to Pay Group transfers, the following occurs:
Consider the most recently finalized pay period, which includes Payees who are paid in multiple parts for the pay period.
e.g. Pay period #6 for the financial year.
Payee is paid for the first 7 days of the period in one Pay Group (CAL_RUN_ID).
Pay Group transfer occurs in the middle of pay period #6 to another Pay Group.
Payee is paid for the second 7 days of the period in the second Pay Group (the transferred CAL_RUN_ID).
The Staging tables include YTD for the Payee for both CAL_RUN_IDs.
The first Pay Event, processed up to the Payment Date of Pay period #6, CORRECTLY selects the YTD from the MAX(process date column) in the staging tables.
The Payee is reported correctly.
When pay period #6 is run separately by CAL_RUN_ID, the Payee appears in the XML for BOTH CAL_RUN_IDs, meaning that the YTD is reported twice for the period for the Payee.
The code INCORRECTLY selects the YTD from the MAX(process date column) in the staging tables FOR THE CAL_RUN_ID, instead of for the Payee.
It fails to determine that the YTD in the first CAL_RUN_ID is superseded by the YTD in the second CAL_RUN_ID.
The same is true if the First Pay Event is processed and sent for the Payment Date of pay period #6 and then pay period #7 is processed by CAL_RUN_ID, thereafter.
The Payee in the scenario will be reported twice in pay period #7.
How to handle such scenario while reporting the amounts in STP XML file?
Solution
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
Goal |
Solution |
References |