Aid To Understanding How A Selected Purchasing Positional Approval Hierarchy Is Structured (Doc ID 1603054.1)

Last updated on JUNE 01, 2016

Applies to:

Oracle Purchasing - Version 12.0.0 and later
Information in this document applies to any platform.

Goal

Oracle Purchasing uses Approval Hierarchies for the approval of Purchasing Documents.  
There are two types of Approval Hierarchies:

 - Job
 - Positions

When a Positional Hierarchy is used the Approval Workflow reads data from the View PO_EMPLOYEE_HIERARCHIES table.  
The table used by the View is populated by running the report 'Fill Employee Hierarchy Report' (FEH).  
The table contains a link to employees that are assigned positions within a hierarchy.

The table on which the View PO_EMPLOYEE_HIERARCHIES is based, contains internal ID numbers for the employee, their superior(s), the positions they hold and the superior level above the employee and performing a SELECT on the base Table or the View will return meaningless numbers.

The only methods available to view the names of the employees is either through the Human Resources (HR) form Position Hierarchy (PERWSDPH) or the HR Position Hierarchy Diagrammer.

These forms will provide information on the structure, but will not provide the following:

 - Jobs held by the Employee or Superior
 - The FND Username held associated with the Employee
 - Whether there is more than one Employee linked to an FND Username
 - Whether the Position is included in the base table for the View PO_EMPLOYEE_HIERARCHIES (only filled positions are included in the Purchasing (PO) table)

The purpose of the script attached to this document is to provide a method of extracting, and expanding, meaningful data from the PO Approval Hierarchy so to understand how the selected hierarchy is constructed in PO_EMPLOYEE_HIERARCHIES.

So the resulting output will include

 - The employee and superior full name
 - The Job name held by the employee and superior
 - The Position name held by the employee and superior
 - The FND Username linked to the employee
 - Whether more than one employee or superior is linked to single FND Username
 - Whether the employee or superior is linked to any FND Username

Once the data is returned and exported into a spreadsheet, the columns can be sorted to suit the required purposes.  
For example, you may wish to group the data by Job name or Position Name.
You may wish to see which employees are included in the hierarchy and who their supervisor(s) is/are or you may wish to see which employees are not included in the hierarchy.

Disclaimer Notice:
The script provided by this document is for educational purposes only and is not supported by Oracle Global Customer Support.


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