Fusion Applications: Procurement Implementation 7 - 2

Information: This course discusses approval tasks at a high level. Fusion Procurement approvals
is covered in detail in a whitepaper available from My Oracle Support.

Fusion Applications: Procurement Implementation 7 - 3

Oracle SOA Suite:
• Is a comprehensive software suite used to build, deploy, and manage service-oriented
architectures (SOA).
( )
• Provides a human workflow service that handles all interactions with users or groups in
business processes
Approval management:
• Controls workflows for business objects such as purchase orders.
• Enables you to define complex, multistage task routing rules
• Integrates
g with the setup
p in Oracle Fusion Human Capital
p Management
g to derive approvers
pp
based on the supervisory hierarchy
Oracle BPM Worklist provides the user interface for:
• Users to access procurement setup tasks assigned to them and perform actions based on
their roles in the workflow
• Implementers to perform approval management setup and to define who should act on which
types of transactions under what conditions

Fusion Applications: Procurement Implementation 7 - 4

Information: To access these setup tasks you need the BPM Worklist Administration Duty role,
which is predefined for the Application Implementation Consultant job role.

Fusion Applications: Procurement Implementation 7 - 5

Stage
A stage allows you to organize approval routing rules into logical groupings. Each stage is
p
associated with a dimension. A dimension contains a set of attributes at a specific p
purchasing
g
document level, such as header or lines, which can be used to author routing rules. Approval
actions within each stage must be completed before entering the next stage.

Participant
There can be many participants within a stage. Properties set on the participants determine whether
approvals would be routed in serial or in parallel.

Oracle Fusion Procurement is seeded with one or more participants within each stage to enable
flexibility in document approvals routing.

Fusion Applications: Procurement Implementation 7 - 6

The following are two properties defined on a participant:

•Routing Type: The supported routing types are: Serial, Parallel and FYI. FYI participants cannot
directly impact the outcome of a task
task, but in some cases can provide comments or add attachments
attachments.
•Voting Regime: The supported voting regimes are: Serial, Consensus, and First Responder Wins.

Rule
Approval rules are routing policies or rules that determine the approvers or FYI recipients for a
business transaction.

•Condition: The IF clauses in an approval rule and evaluated to either true or false. For the rule to
apply to a transaction, all of its conditions must be true. An example of a condition is: If requisition
approval amount is less than 500 USD, or if requisition approval amount is between 500 USD and
10000 USD.
•Action: Instruction to include a given set of approvers within an approval rule.

Fusion Applications: Procurement Implementation 7 - 7

Employee Supervisor Hierarchy
Approvals can be set up to navigate the employee supervisory hierarchy, which is defined in Oracle
p
Fusion Human Capital Management,
g , up
p to a certain number of levels. Employees
p y must be set up
p
with appropriate jobs and supervisors.

Position Hierarchy
You can also choose to route document approvals to navigate the position hierarchy defined in
Oracle Fusion Human Capital Management, until a specified job level is reached. The position
hierarchy must be defined along with corresponding job levels, and the employees must be
assigned the appropriate positions.

Job Levels
Job level routings are based on the supervisory hierarchy defined in Oracle Fusion Human Capital
Management. The approval list will be generated based on the starting person specified in a rule
and continuing until an approver with a sufficient job level is found. The supervisory hierarchy must
b d
be defined
fi d along
l with
ith th
the corresponding
di jjob
b llevels.
l

Fusion Applications: Procurement Implementation 7 - <#>

Approvals will be routed to the seeded stages in the following sequence:

Header Pre Approval Stage

Pre approval stages are used if approvals are required before routing to, for example, fiscal
approvers

Header Stage

Header Post Approval Stage

Fusion Applications: Procurement Implementation 7 - 9

The controls on the Configurations Tab allow you to:
• Control if tasks should be aggregated
• Set
S t Error
E Notifications
N tifi ti
• Setup assignment and routing policies
• Control if assigned approvers can add additional approvers to the task
• Enable auto-claim
• Indicate if the approval task should be completed when a Reject or Approve action is
performed by a participant

Fusion Applications: Procurement Implementation 7 - <#>

Deadlines: Configure when tasks expire, are escalated, or renewed. Expired tasks are
automatically rejected. For example, you can define the expiration policy so that if no one acts
upon a requisition in two weeks, then it expires and the requester needs to resubmit it.

Fusion Applications: Procurement Implementation 7 - 11

Notification Settings: Indicates when a user or group is assigned a task or is informed that the
status of a task has changed. Notifications can be sent through email, voice message, instant
message, or SMS. You can also specify different types of participants to receive notifications for
different actions.

You can set up reminders to be sent before task expiration or after task assignment.

Fusion Applications: Procurement Implementation 7 - 12

Fusion Applications: Procurement Implementation 7 - 13
Approval Groups
• Can be nested within other approval groups.
• Are stored at the server level and not shared across domains
domains. For example
example, you cannot use
the same group for Financials and Procurement.

Fusion Applications: Procurement Implementation 7 - 14

Fusion Applications: Procurement Implementation 7 - 15
Fusion Applications: Procurement Implementation 7 - 16
Fusion Applications: Procurement Implementation 7 - 17
The following are two properties defined on a participant:
• Routing Type: The supported routing types are: Serial, Parallel and FYI. FYI participants
cannot directly impact the outcome of a task, but in some cases can provide comments or
add attachments.
• Voting Regime: The supported voting regimes are: Serial, Consensus, and First Responder
Wins.
Rule
Approval rules are routing policies or rules that determine the approvers or FYI recipients for a
business transaction.
• Condition: The IF clauses in an approval rule and evaluated to either true or false. For the
rule to apply to a transaction, all of its conditions must be true. An example of a condition is:
If requisition approval amount is less than 500 USD, or if requisition approval amount is
between 500 USD and 10000 USD.
• Action: Instruction to include a given set of approvers within an approval rule.

Fusion Applications: Procurement Implementation 7 - 18

Fusion Applications: Procurement Implementation 7 - 19
Note: Purchasing uses one task for both agreements and purchase orders.
Based on your unique business requirements, administrators can choose to send the approval
q
request to approvers
pp in p
parallel or in sequence.
q Approvals
pp can be sought
g using
g single
g approver,
pp ,
supervisory chain, position, job level hierarchy, or using a list of approvers.

Fusion Applications: Procurement Implementation 7 - 20

The following are two properties defined on a participant:
• Routing Type: The supported routing types are: Serial, Parallel and FYI. FYI participants
cannot directly impact the outcome of a task, but in some cases can provide comments or
add attachments.
• Voting Regime: The supported voting regimes are: Serial, Consensus, and First Responder
Wins.
Rule
Approval rules are routing policies or rules that determine the approvers or FYI recipients for a
business transaction.
• Condition: The IF clauses in an approval rule and evaluated to either true or false. For the
rule to apply to a transaction, all of its conditions must be true. An example of a condition is:
If requisition approval amount is less than 500 USD, or if requisition approval amount is
between 500 USD and 10000 USD.
• Action: Instruction to include a given set of approvers within an approval rule.

Fusion Applications: Procurement Implementation 7 - 21

Fusion Applications: Procurement Implementation 7 - 22
Fusion Applications: Procurement Implementation 7 - 23
The attribute can be used as follows:
• User Defined Attribute: Requisition Amount in USD
• Type: Currency based
• Attribute to Convert Type: Approval task attribute
• Attribute to Convert: Requisition Amount
• Convert To: USD
• Conversion Rate Type: Corporate
Once you have defined the attribute, then it can be used in the rule condition as follows:
Requisition Amount in USD greater than 500

Fusion Applications: Procurement Implementation 7 - 24

Fusion Applications: Procurement Implementation 7 - 25
Fusion Applications: Procurement Implementation 7 - 26
Fusion Applications: Procurement Implementation 7 - 27
Fusion Applications: Procurement Implementation 7 - 28
Fusion Applications: Procurement Implementation 7 - 29
Fusion Applications: Procurement Implementation 7 - 30
Fusion Applications: Procurement Implementation 7 - 31
The approvals UI displays only relevant fields to guide you along the setup of each type of routing
in an action. You can route using approval groups, supervisory hierarchy, job level, position
hierarchy, custom function or single approver.

There are three types of actions:

• Approval Required: The document or object will be routed for approvals.
• Automatic: The document or object can be approved or rejected automatically.
• Information Only: FYI tasks will be sent to notify the specified persons.

Fusion Applications: Procurement Implementation 7 - 32

The approvals UI displays only relevant fields to guide you along the setup of each type of routing
in an action. You can route using approval groups, supervisory hierarchy, job level, position
hierarchy, custom function or single approver. Instead of having to know the specific function calls
to use, the UI translates the setup into a syntax that the approval management extension engine
understands.
d t d
There are three types of actions:
• Approval Required: The document or object will be routed for approvals.
• Automatic: The document or object can be approved or rejected automatically.
• Information Only: FYI tasks will be sent to notify the specified persons.

You can also choose to route approvals through a specific worker chain by selecting the name of
the worker.
Approval Chain Of
Select the approval chain of the persons within a document. For example, preparer and requester
in purchase requisitions, or a buyer in purchasing documents.
Start With
• Identify the first participant in a list. The Start With attribute can be:
Manager (Default value).
• The value selected in the Approval Chain Of choicelist.
Minimum Job Level
• Indicate the number of job levels that are required to perform the approval action if the rule
applies. For example, using the figure below, if Mary (Job Level 1) submits a document for
approval and the Minimum Job Level is set to 3, then only John Allens needs to approve.

Top Worker in Hierarchy

• Identify the person at the top of the employee hierarchy, or the top person in the approval
chain. In most cases, this is the CEO.
Include
• Indicates if everyone returned in the list of participants from this action will be included, the
first and last approver from the list will be included, or only the last approver will be included.

Fusion Applications: Procurement Implementation 7 - 33

Position Hierarchy
Defined in Oracle Fusion Human Capital Management, positions are defined along with
corresponding job levels, and employees are assigned appropriate positions. For example, the
position Buyer is an instance of a position in the Purchasing Department. The job level of that
Buyer could be any job level assigned to that position.
Position Hierarchy
• Indicates if everyone returned in the list of participants from this action will be included, the
first and last approver from the list will be included, or only the last approver will be included.
Position Chain Of
• Select the approval chain of the persons within a document. For example, preparer and
requester in purchase requisitions, or a buyer in purchasing documents.
Start With
• Identify the first participant in a list. The Start With attribute can be:
Next Position (Default value).
• The value selected in the Approval Chain Of choicelist.
Minimum Job Level
• Indicate the number of job levels that are required to perform the approval action if the rule
applies. For example, using the figure below, if Job Level 1 submits a document for approval
and the Minimum Job Level is set to 3, then only Job Level 3 needs to approve.
Top Worker in Hierarchy
• Identify the person at the top of the employee hierarchy, or the top person in the approval
chain. In the most cases, this is the CEO.
Include
• Indicates if everyone returned in the list of participants from this action will be included, the
first and last approver from the list will be included, or only the last approver will be included.
Single Approver
Single approver allows you to route the approval to a specific person on the document, or a
specific worker.

Fusion Applications: Procurement Implementation 7 - 34

Supervisory Hierarchy
Approval Chain Of
• You can select the approval chain of the persons within a document. For example, preparer
and requester in purchase requisitions, or a buyer in purchasing documents.
• You can also choose to route approvals through a specific worker chain by selecting the
name of the worker.
Start With
• Start With identifies the first participant in a list. The Start With attribute can be:
Manager (Default value).
• The value selected in the Approval Chain Of choicelist.
choicelist
Number of Approval Levels
• The number of approvers in the supervisory hierarchy starting with the person specified in
Start With.
Top Worker in Hierarchy
• The Worker in Hierarchy identifies the person at the top of the employee hierarchy, or the top
person in the approval chain. In the most cases, this is the CEO.
User-Defined Routing
You can setup user-defined attributes with custom type. The custom user-defined attributes can
be set up to return a single user, or a list of users to whom human tasks can be routed.

Fusion Applications: Procurement Implementation 7 - 35

Fusion Applications: Procurement Implementation 7 - 36
Fusion Applications: Procurement Implementation 7 - 37
Fusion Applications: Procurement Implementation 7 - 38
Fusion Applications: Procurement Implementation 7 - 39