Rollback of MIX BEE Load has not Removed Entries
(Doc ID 396651.1)
Last updated on APRIL 04, 2025
Applies to:
Oracle Payroll - Version 11.5.10.2 to 11.5.10.2 [Release 11.5]Information in this document applies to any platform.
Symptoms
On 11.5.10.2 in Production:
Find the Rollback of MIX BEE load has not removed element entries against employee even though batch status reset to Unprocessed.
Found that the problem occurs only for assignment records with multiple batch rows where MIX BEE
processing 'Actions If Exist parameter' = Change Existing Entry
i.e. single element entry for all records, with those with multiple rows having this set to their last batch row.
After BEE rollback, element entry removed for assignment records with single row in the batch but
not for those with multiples rows in the batch.
Checked the "Rollback Entry Updates" option but same problem occurs i.e. records with >1 entry in
Batch did not revert after BEE Rollback.
As previously stated the other Batch Control options are "Change Existing Entry" (action if entry
exists) and "Override" (date effective changes).
BEE Rollback works fine for "Create New Entry" but not "Change Existing Entry" whether or not the
"Rollback Entry Updates" option is checked.
EXPECTED BEHAVIOR
Expect to successfully rollback the entries with >1 entry in Batch also.
STEPS
The issue can be reproduced at will with the following steps:
1. UK HRMS Manager -> Submit Processes and Reports > Single Request > Rollback > Batch Element Entry
BUSINESS IMPACT
The issue has the following business impact:
Due to this issue, users have to manually delete element entries for incorrectly processed MIX BEE
- multiple elements across several employees.
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 |