Element Entry Override Flag Remains Checked Even If Element Name Is Changed
(Doc ID 2431908.1)
Last updated on FEBRUARY 20, 2019
Applies to:
Oracle Payroll - Version 12.2.4 and laterInformation in this document applies to any platform.
Symptoms
On : 12.2.4 version, UK Payroll
ACTUAL BEHAVIOR
---------------
1. An element entry exists for an assignment eg 'Basic Pay' which is recurring and multiple entries not allowed
2. The user mistakenly adds a second 'Basic Pay' element entry instead of 'Basic Pay Adjust' and received the message:
"Note the entry must be an override cause all other possibilities of this
element have already been used"
This is set to 'Override' due to Basic Pay not allowing multiple entries of this type (based on definition of this element).
3. Instead of deleting the override 'Basic Pay' element entry the users, retype the name 'Basic Pay Adjust' over the Element Name 'Basic Pay'. This
correctly changes the Processing Type from 'Recurring' to 'Non-Recurring' but leaves the 'Override' flag checked. This override cannot be manually
unchecked. FRM-40200: Field is protected against update.
4. This has led to users mistakenly leaving the element with the override causing hundreds of instances of overpayments where additional entries for
'Basic Pay Adjust' were ignored due to the user not noticing this flag.
EXPECTED BEHAVIOR
-----------------------
The override flag should removed when element is changed
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 |