Approval Hierarchies – Pros and Cons
Oracle Purchasing mandates that some kind of document routing method be used for approval of purchase documents in oracle apps. Document security, routing and approval is controlled by document type. These documents are routed to certain kinds of hierarchies for approval, and hence, these can also be called as approval hierarchies, which can be classified into 2 types:
1) Position based hierarchy:
– Obey position relationship.
– Oracle Purchasing uses ‘position’ as a roadmap to determine how and where the documents will be routed once the approval process has been initiated.
Pros of using Position hierarchy:
- Assuming Human Resources is installed and the data is being maintained, purchasing can make an employee representation of the position approval hierarchy by simply running the Fill Employee Hierarchy process. This will allow changes occurring in personnel assignments to be updated in the position approval hierarchy.
- Documents can get hung up less frequently due to the lower volume of structural hierarchy changes compared to the higher volume of personnel changes that typically occur in companies.
- Cannot be used with jobs, but must be used with positions.
2) Employee/Supervisor based hierarchy:
– Obeys a hierarchy for document routing, which is based solely on employee and the supervisor relation which is defined in the ‘enter person’ window.
Pros of using Employee supervisor hierarchy:
- Allows flexibility of establishing approval groups around either jobs or positions.
- Assuming Oracle Human Resources (HR) is installed and the data is being maintained, Purchasing uses the supervisor name on the employee record which should be entered and maintained for HR purposes already.
- Documents may not travel by the employee/supervisor relationship for approval purposes, but take a different path in part or entirely.
- Documents can get hung up more frequently due to the volume of personnel changes that typically occur in companies.
- Higher volumes of documents need to be re-routed using the Forward-To settings. Recall that the first name alphabetically appears as the default.