In PO there are two methods to route documents for approval.
1.Approval Hierarchies (uses position hierarchies, A tree of hierarchy more than one person above to approve)
2.Employee/Supervisor Relationships (use employee/supervisor relationship, Just one person above to approve)
Approval 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
Employee/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.
Thanks & Regards,
S.Grace Paul Regan.
6 comments:
Good one
Hi,
Could u throw some light about the document types which would use these hierarchies.
What kind of Oracle documents are being discussed above ? I do have knowledge about various business suites that are a part of Oracle but about documents I am learning for the first time from your article. Please provide some details to sole my confusion.
Documents are nothing but the types of Purchase Orders, It states
1. Purchase Requisition
2. Internal Requisition
3. Standard Purchase Order
4. Blanket Purchase Agreement &
Release
5. Contract Purchase Agreement &
Release
6. Planned Purchase Order
These are the different document types which can have its own Approval Hierarchy (Position or Supervisor Hierarchy)
Thanks & Regards,
S.Grace Paul Regan
In the approval hierarchy, if one approver has to modify the purchase order, then
1) does he need to be defined as a buyer?
2) do we need to buy a buyer license for him?
Thanks in advance for the clarification.
Kudos to the Fusion SCM team for their continuous updates and enhancements. The regular improvements ensure that we stay ahead of industry trends and maintain a competitive edge in the market. Fusion cloud SCM Training in hyderabad
Post a Comment