Approval Hierarchy in Oracle Apps

Approval Hierarchy in Oracle Apps
Aravinda Reddy, Associate Consultant – Financials
Mohit Monga, Associate Consultant – Financials
Rahul Guhathakurta, Associate Consultant -SCM

SlideShare Version (c) 2009 Evolutionary Systems Pvt. Ltd ~
1
Ahmedabad

Position - Approval Hierarchy
• Position Hierarchies are hierarchies that have a position
relationship. By position, we mean position that are
attached to employees.
• 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.

(c) 2009 Evolutionary Systems Pvt. Ltd ~
2
Ahmedabad

Position Approval Hierarchy
Set Up Flow
• Define Job
• Define Position
• Position Hierarchies
• Define Employees
• Approval Groups
• Approval Assignments
• Run Request (Fill employee hierarchy)
• Create Responsibilities
• Create users &attaché the above responsibilities
• Create the PO and see the notification summary to
check whether system has sent that PO for the
approval or not
3
Ahmedabad

Approval Hierarchy Logic

Employe
User ID
e

Position Hierarchy Document Type

Approva Approval
l Assignmen
Group t

Documen
t Amount (c) 2009 Evolutionary Systems Pvt. Ltd ~
4
Ahmedabad

Case
• We will set up a 3-tier approval hierarchy
which will full-fill the following.
• Purchaser, Department Head & Branch Head
• We create the three tire hierarchy for the Re
1, Rs 30,000 & Rs 100000.
• If a PO is more than Re 1 and within Rs 30001,
the approver will be the Department head.
• If a PO is within the range of Rs 30,001 - Rs
1,00,001, the approver will be the Branch
Head. (c) 2009 Evolutionary Systems Pvt. Ltd ~
5
Ahmedabad

STEP 1: Define Job

Navigation: Human Resource -> Work Structures -> Job -> Description
6
Ahmedabad

Defining a Job Name : Purchaser

Purchaser will be
responsible for
preparing POs

7
Ahmedabad

Job: Purchaser(060) Defined
Similar way Define Department Head (070) & Branch Head (080)

8
Ahmedabad

STEP 2: Define Positions

Navigation: Human Resource -> Work Structures -> Position ->
Description
9
Ahmedabad

Define Position : Purchaser (061)

10
Ahmedabad

Position: Purchaser
(061)Defined
Similar way Define positions for Department Head
(071) & Branch Head (081)

Linking
the job
to a
particula (c) 2009 Evolutionary Systems Pvt. Ltd ~
11
Ahmedabad
r position

12
Ahmedabad

STEP 3: Define Position
Hierarchy

Navigation: Human Resource -> Work Structures -> Position ->
Hierarchy
13
Ahmedabad

14
Ahmedabad

Query: Top Most Position
“Branch Head” (081)

15
Ahmedabad

Press Down
Assign Subordinate “Department Head Tab to
(071)” to “Branch Head (081)” assign
subordinate
to
Department
Head

16
Ahmedabad

Assign Subordinate “Purchaser (061)” to
As NO employee
“Department Head (071)” has been assigned
to this position

17
Ahmedabad

Position Hierarchy Diagrammer

Navigation: Human Resource -> Work
Structures -> Position -> Position
Hierarchy Diagrammer
18
Ahmedabad

STEP 4: Define Employee

Navigation: Human Resource -> People -> Enter &
Maintain
19
Ahmedabad

Create Employee :
Purchaser
Similarly Create Employee: Department Head &
Branch Head

20
Ahmedabad

Assign Address to Employee
“Purchaser”

21
Ahmedabad

Assign Job and Position to
Employee - Purchaser

Assigning Job and
Position to Employee
– Purchaser

22
Ahmedabad

Employee – Department
Head

Assigning Job and
– Department Head

23
Ahmedabad

Employee – Branch Head

Assigning Job and
– Branch Head

24
Ahmedabad

STEP 5: Approval Groups

Navigation: Purchasing -> Set Up -> Approvals -> Approval
Groups
25
Ahmedabad

Define Tier 1 Approval Group

26
Ahmedabad

LOVs -> we
can restrict a
particular
position by
defining the
approval
rules through
the
mentioned
objects

27
Ahmedabad

Document Amount &
Ranges Assigned
Approval
Authority or
exclude from the
approval of
many ranges

28
Ahmedabad

STEP 6: Approval Assignment

Navigation: Purchasing -> Set Up -> Approvals -> Approval Assignments
29
Ahmedabad

Select the Document Type
– Approve Standard PO

30
Ahmedabad

Select the Approval Group –
Tier 1

31
Ahmedabad

Select the Approval Group – Tier 2

32
Ahmedabad

Select the Approval Group – Tier 3

33
Ahmedabad

STEP 7: Update Document Type

Navigation: Purchasing -> Control L -> Document %

34
Ahmedabad

Click on this Tab
to Update PO
Standard

35
Ahmedabad

Attach Hierarchy

Note: The Default Hierarchy option will only appear on the Document Type form if
the option Use Approval Hierarchies is checked on the Human Resources zone on the
Financial Options screen. The Default Hierarchy field has a LOV. This list is derived
from the hierarchies created (c) 2009 Evolutionary Systems Pvt. Ltd ~ form
using the Position Hierarchy 36
Ahmedabad

Run Request : Fill Employee
Hierarchy

37
Ahmedabad

38
Ahmedabad

Fill Employee Hierarchy
Phase: Completed Status: Normal

39
Ahmedabad

STEP 8: Define Users

40
Ahmedabad

Create User ~Buyer –
Named Mr. Purchaser

41
Ahmedabad

42
Ahmedabad

Attach Buyer – “Purchaser”

43
Ahmedabad

44
Ahmedabad

45
Ahmedabad

46
Ahmedabad

47
Ahmedabad

Create PO and
Approve it!

48
Ahmedabad

49
Ahmedabad

Check Notifications

50
Ahmedabad

Approval Notification to
Branch Head

51
Ahmedabad

Log in as “Branch Head”

52
Ahmedabad

Check the Notification Summary

53
Ahmedabad

54
Ahmedabad

55
Ahmedabad

56
Ahmedabad

57
Ahmedabad

Thank You!

Aravinda Reddy, Associate Consultant – Financials
aravindar@evosys.co.in
Mohit Monga, Associate Consultant – Financials
mohitm@evosys.co.in
Rahul Guhathakurta, Associate Consultant –SCM
rahulg@evosys.co.in

58
Ahmedabad

Approval Hierarchy in Oracle Apps

Recommandé

Recommandé

Contenu connexe

Tendances

Tendances (20)

Similaire à Approval Hierarchy in Oracle Apps

Similaire à Approval Hierarchy in Oracle Apps (20)

Dernier

Dernier (20)

Approval Hierarchy in Oracle Apps