Values Updated In UDT Are Not Reflecting Properly As Per The Effective Date
(Doc ID 2488687.1)
Last updated on FEBRUARY 06, 2019
Applies to:Oracle Fusion Global Payroll Cloud Service - Version 184.108.40.206.0 and later
Information in this document applies to any platform.
Unexpected behavior when updating the UDT XX_EXAMPLE_USER_TABLE_NAME_HERE values.
User updates the Effective Start Date value for a rate from 1-Jan-1951 to 1-Jan-2019.
User submits and comes back to the page and sees several other rates were updated to 1-Jan-2019 and other rates still showing the 1-Jan-1951
-As a test case, user confirmed:
he updated UDT 'XX_EXAMPLE_USER_TABLE_NAME_HERE' and 'XX_EXAMPLE_USER_TABLE_NAME_HERE_RATE'. As checked, rates updated in 'XX_EXAMPLE_USER_TABLE_NAME_HERE_RATE' is working fine, whereas 'XX_EXAMPLE_USER_TABLE_NAME_HERE' is behaving differently.
-"the UDT 'XX_EXAMPLE_USER_TABLE_NAME_HERE' was originally set to an effective date 1/1/1951 and now we are updating new rates with effective from 1/1/2019."
- the rates are directly pulled into the application from UDT via fast formula 'XX_EXAMPLE_USER_TABLE_NAME_HERE'.
STEPS TO REPRODUCE
Navigator > Edit User-Defined Tables
When updating one value, other values should not get updated
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