How to identify all unassigned transactions caused by Unable to build the Supervisor Hierarchy error? (Doc ID 1162984.1)

Last updated on JUNE 22, 2017

Applies to:

Oracle Self-Service Human Resources - Version 11.5.10.2 to 12.1.1 [Release 11.5.10 to 12.1]
Information 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.

How to identify these transactions?



Solution

Sign In with your My Oracle Support account

Don't have a My Oracle Support account? Click to get started

My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms