My Oracle Support Banner

Approval Rule Action To Allow Routing Based On Job Level Or Supervisory Hierarchy (Doc ID 2368031.1)

Last updated on MARCH 01, 2018

Applies to:

Oracle Fusion Purchasing Cloud Service - Version and later
Information in this document applies to any platform.


Manage Purchasing Document Approvals

Is it possible to have the approval route to evaluate the job level first, if no approver with that job level is found, route be based on supervisory hierarchy only?

Currently, when Route Using Job Level is selected, the system retrieves approvers based on supervisory hierarchy and job level together.
The expected outcome would be to look at job level first, then if the job level is not found, look at supervisory hierarchy.

For example, the supervisory hierarchy/job levels are set up as follows:
User, Manager, Job Level
Requester, Requester Manager, job level 3
Job Level Manager, CEO, job level 100

Approval Rule Action is set up to route by job level:
Action type = Approval Required
Route Using = Job Level
Approval Chain of = Requester
Start With = Requester
Minimum Job Level = 4
Top Worker in the hierarchy = CEO

If the Requester's Manager job level is less than the job level assigned, the system assigns the task to CEO (next job level available).

The desired outcome is:
Retrieve the Manager with the job level that matches the minimum job level (in this scenario the manager's job level does not match the job level in the Action);
If not found,
Retrieve the Requester's manager (supervisory hierarchy only).


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

My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.