Free Oracle Magazine Profit:The Executive's Guide to Oracle Applications

Enter your e-mail address to receive notifications when there are new posts

Profit Magazine: The Executive's Guide to Oracle Applications

Purchasing Approvals

Posted on March 24th, 2008 by Sanjit Anand |Print This Post Print This Post |Email This Post Email This Post

In PO there are two methods to route documents for approval.

1Approval Hierarchies (uses position hierarchies)

2Employee/Supervisor Relationships (use employee/supervisor relationship)

1Approval Hierarchies

Purchasing utilizes positions as a roadmap to determine how and where documents will be routed once the approval process has been initiated. It is first necessary to have created all positions that are going to be used in the system. Once all positions have been created, it is necessary to build the position hierarchy.

Each position has approval limits, so when a purchase order exceeds the limits of the position, the purchase order is forwarded onto the next position in the Hierarchy

2Employee/Supervisor Relationships

This type of hierarchy does not use the Approval Hierarchy form,but is defined by the employee/supervisor relationship. The supervisor of an employee is defined on the Assignment region of the Employee form

If the purchase order entered by the employee exceeds the approval limits, the purchase order is forwarded onto the employees’ supervisor, as defined on the Employee form

To implement this form of approval routing, you need only to define JOBS. The JOB will then serve as the tie to the Approval group, and based on the approval limits from the Approval Group, the Document will either be Approved or Forwarded to the Employees’ Supervisor.

Similar Post

Posted in Oracle Purchasing | Email This Post Email This Post | Print This Post Print This Post

Leave a Comment

Please note: Comment moderation is enabled and may delay your comment. There is no need to resubmit your comment.