Fusion Global Payroll: Department Changes History Effective Date Not Supported in Payroll Interface For ADP Global Payroll V2
(Doc ID 2983561.1)
Last updated on OCTOBER 30, 2023
Applies to:
Oracle Fusion Payroll Interface Cloud Service - Version 11.13.23.07.0 and laterInformation in this document applies to any platform.
Symptoms
ACTUAL BEHAVIOR
---------------
Payroll Interface for ADP Global Payroll V2 is fetching Department changes date effective, but the third party provider - ADP, receives only the latest, active one.
EXPECTED BEHAVIOR
-----------------------
What gets into the ADP system should match the actual employee assignment history -transfer changes for Department.
STEPS
-----------------------
The issue can be reproduced at will with the following steps:
1. On October 1st, Department is changed from A to B.
2. Doing a correction, on same October 1st, reverting back to the original Department - A.
(After the initial change was made at 1. and registered, realized that the transfer should have happened on November 1st, so they changed it back).
3. Then, from November 1st, updating the Department value correctly to B.
4. GPI V2 extract is fetching only the latest modified value and not the entire history of Department changes - assignment level.
(So, on October 1st, the Department - B is shown and not the already corrected one A).
| Start Date | End Date | Department (DEP) | Observation | How ADP received the DEP changes |
| 15.09.2022 | 30.09.2023 | A | Initial value | A |
| 01.10.2023 | 01.10.2023 | B | Initial change (wrong) | B |
| 01.10.2023 | 31.10.2023 | A | Correction 1 | B |
| 01.11.2023 | 31.12.4712 | B | Correction 2 | B |
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 |