How to identify all unassigned transactions caused by Unable to build the Supervisor Hierarchy error?
(Doc ID 1162984.1)
Last updated on FEBRUARY 07, 2024
Applies to:
Oracle Self-Service Human Resources - Version 11.5.10.2 and laterInformation in this document applies to any platform.
Goal
What is the best way to identify all unassigned transactions caused by Unable to build the Supervisor Hierarchy error?
Example:
Supervisor hierarchy was broken within terminated employee but now fixed.
During time the Supervisor hierarchy was broken, absences were raised by employees and those absences are currently stuck in the workflow.
Supervisor hierarchy was broken within terminated employee but now fixed.
During time the Supervisor hierarchy was broken, absences were raised by employees and those absences are currently stuck in the workflow.
How to identify these transactions?
Solution
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
| Goal |
| Solution |
| References |