Fusion Applications - Global Payroll - Retro Costing For Person Is Not Working
(Doc ID 2667822.1)
Last updated on MAY 07, 2020
Applies to:
Oracle Fusion Global Payroll Cloud Service - Version 11.13.20.01.0 and laterInformation in this document applies to any platform.
Symptoms
On : 11.13.20.01.0 version, Global Payroll
ACTUAL BEHAVIOR
---------------
When Retroactive changes occur in Payroll, costing should pick the account set at Person level costing.
It is working fine, when running the normal payroll without any retroactive changes.
EXPECTED BEHAVIOR
-----------------------
Costing is picking the account from Element Eligibility, instead of Person level costing.
STEPS
-----------------------
The issue can be reproduced at will with the following steps:
1. Costing set up at Person Level.
2. Also set Element Eligibility Costing
3. Run the Quickpay and check the costing for the Retro elements.
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 |