The two types of approval Hierarchy in Oracle Apps Purchasing are
-
Position Approval Hierarchy
-
Grade Approval Hierarchy
-
Employee/Supervisor Hierarchy
-
Job Approval Hierarchy
Oracle Purchasing supports two main approval hierarchies: Position Hierarchy, which routes documents based on organizational positions, and Employee/Supervisor Hierarchy, which routes documents based on the direct reporting structure. Grade and Job hierarchies are not standard approval routing methods.
To answer this question, you need to have knowledge of the approval hierarchies in Oracle Apps Purchasing. Let's go through each option to understand why it is correct or incorrect:
Option A) Position Approval Hierarchy - This option is correct. In Oracle Apps Purchasing, the Position Approval Hierarchy is based on the positions held by individuals within the organization. Approval requests are routed to individuals in higher positions for approval.
Option B) Grade Approval Hierarchy - This option is incorrect. There is no Grade Approval Hierarchy in Oracle Apps Purchasing. Grades are not used for determining approval routing.
Option C) Employee/Supervisor Hierarchy - This option is correct. In Oracle Apps Purchasing, the Employee/Supervisor Hierarchy is based on the reporting relationships between employees and their supervisors. Approval requests are routed to the supervisors for approval.
Option D) Job Approval Hierarchy - This option is incorrect. There is no Job Approval Hierarchy in Oracle Apps Purchasing. Jobs are not used for determining approval routing.
The correct answer is A, C. The Position Approval Hierarchy and Employee/Supervisor Hierarchy are the two types of approval hierarchies in Oracle Apps Purchasing.