Element Not Costed When Assignment Is Changed Between A Payroll Run And The Costing Run
(Doc ID 2461053.1)
Last updated on DECEMBER 04, 2022
Applies to:
Oracle Payroll - Version 12.1.3 and laterInformation in this document applies to any platform.
Symptoms
A payroll is processed and an employee has an element linked to them based on some eligibility criteria. After the payroll run, a change is made to the assignment that ends the eligibility for the element and it is end-dated or purged. The Costing process is now run for the original payroll run. Elements that were end dated or purged due to the eligibility change do not get costed. The result is the Payroll Register and US Gross to Net Summary are correct, but do not equal the Costing results, which is incorrect.
Example of Steps taken:
Payroll Period 6-Aug-2018 thru 19-Aug-2018
1. Payroll Run processed on 24-Aug-2018
2. Payroll Register and US Gross to Net run on 24-Aug-2018
3. On 28-Aug-2018, the Effective Date was set back to mid July and the assignment was updated, making it ineligible for certain elements.
4. On 29-Aug-2018, Costing was run. Costing reports do not agree with Payroll register. Element Entries that were dis-allowed under the assignment setup are missing from the Costing results.
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 |
| Cause |
| Solution |
| References |