I am happy to announce that my contribution to metalink on Hiding Search Option in Manager Self Service Pages in E-Business Suite Release 12 has been accepted via an SR and been posted as a Metalink Note.
Once again I am happy that I have contributed something small to my company as well as Metalink Community.
You can read the content from Metalink Note ID: 858526.1.
Happy Reading!
Showing posts with label Oracle Apps Functional. Show all posts
Showing posts with label Oracle Apps Functional. Show all posts
Jan 15, 2009
Approval Hierarchy in Oracle Purchasing
Approval Hierarchy in Oracle Purchasing
Customers want to undergo some kind of approval mechanism for their PO's. Oracle Purchasing gives two flavors of it based on best industrial practices, they are:
We will then use the Approval Groups window to map the jobs to the approval limits/accounts/items/categories that relate to a PO. Then ofcourse the Approval Assignment step where we say what positions have what authority to approve various flavors of documents like Standard PO, Planned PO, Purchase Requisition etc.
2. Position Hierarchy: Positions are declared before hand and referred in Employee screen. In Approval Groups we specify the Positions and map them to Approval Assignments. We then use the Position Hierarchy screen to specify the hierarchy / level through which the PO goes for approval (imagine a flow chart).
Apart from these two, we have to look at a key setup option to make sure that everything works as specified. This is the Financial Options screen. Navigate to the Human resources tab. Check box "Use Approval Hierarchies" determines whether we are using the Position Hierarchy or Employee - Supervisor Relationship for Approval of documents. If this is checked then we are using the former else the latter.
Customers want to undergo some kind of approval mechanism for their PO's. Oracle Purchasing gives two flavors of it based on best industrial practices, they are:
- Employee - Supervisor Relationship
- Position Hierarchy
- Employee - Supervisor Relationship: Employees are connected by their Supervisors. Each Employee is assigned to a Supervisor level by level until it reaches the head of a depratment or a CEO or CFO for that matter. While defining employees, their Supervisor and Job is set. As you can clearly see, all supervisors must be set first and also all jobs defined in the Shared/Full HRMS module.
We will then use the Approval Groups window to map the jobs to the approval limits/accounts/items/categories that relate to a PO. Then ofcourse the Approval Assignment step where we say what positions have what authority to approve various flavors of documents like Standard PO, Planned PO, Purchase Requisition etc.
2. Position Hierarchy: Positions are declared before hand and referred in Employee screen. In Approval Groups we specify the Positions and map them to Approval Assignments. We then use the Position Hierarchy screen to specify the hierarchy / level through which the PO goes for approval (imagine a flow chart).
Apart from these two, we have to look at a key setup option to make sure that everything works as specified. This is the Financial Options screen. Navigate to the Human resources tab. Check box "Use Approval Hierarchies" determines whether we are using the Position Hierarchy or Employee - Supervisor Relationship for Approval of documents. If this is checked then we are using the former else the latter.
Subscribe to:
Posts (Atom)