Professional Documents
Culture Documents
Copyright © 2017, Oracle and/or its affiliates. All rights reserved. 6-2
Topics
• Approval Management
• Task Configurations
• Managing Approvals
• Managing Rules
Copyright © 2017, Oracle and/or its affiliates. All rights reserved. 6-3
Procurement Process
Requisitions
Catalog and
Content Management
Purchase Orders
RFQs/Quotations
P2P
Sourcing
Receiving
Analysis
Invoice/Payment
Supplier Management
Reporting
Supplier Performance
Copyright © 2017, Oracle and/or its affiliates. All rights reserved. 6-4
Approval Management for Procurement Setup and Maintenance
The tasks in the Approval Management functional area are used to define approval routing
structures and controls for Procurement usage.
Copyright © 2017, Oracle and/or its affiliates. All rights reserved. 6-5
Approval Management Foundation
• Workflow is an automated process in which tasks are passed from a user, a group of
users, or the application to another user or group for consideration or action. The tasks
are routed in a logical sequence to achieve an end result.
• A workflow human task is anything that requires attention or action from users.
Examples of tasks include approving a requisition or purchasing documents.
• For workflows, Oracle Applications Cloud uses the approval management extensions of
the human workflow services from Oracle SOA Suite, as well as the Oracle BPM
Worklist application.
Copyright © 2017, Oracle and/or its affiliates. All rights reserved. 6-6
Approval Management: Overview
Use the following setup tasks, accessed from the
Approval Management functional area, to set up
approval management. These tasks take you to Oracle
BPM Worklist.
• Manage Approval Groups: Optionally create and
maintain sets of users who can act on workflow
tasks, for example, a chain of approvers for expense
reports. Uses Oracle BPM Worklist.
• Manage Task Configurations for Procurement:
Create task-level settings. Uses Oracle BPM
Worklist.
Use the other Manage <area> Approvals tasks to
manage approval configuration for the given area.
Copyright © 2017, Oracle and/or its affiliates. All rights reserved. 6-7
Approval Management: Key Concepts
Copyright © 2017, Oracle and/or its affiliates. All rights reserved. 6-8
Hierarchies and Job Levels
Header Stage
You can optionally use the Manage Approval Groups interface to define sets of users that
can be selected for an Approval Group. Tasks would be routed to the specified group of
users. Example:
• You have a special, ongoing project that involves a wide range of employees. You can
create an approval group of the managers involved, who must approve expenses related
to the project.
• You have certain categories of requisitions that require preapproval from a select group
of people. You can create an approval group containing the users who must all approve
such requisitions in parallel before additional approvals can be made.
Approval Groups are managed in the Oracle BPM Worklist. Access it by clicking the Manage
Approval Groups task on the Setup page, in the Approval Management functional area.
Approval Groups: You select specific users to include in the group and specify the flow of
tasks from one user to another. If the group is used in a rule set that is predefined with
parallel routing, then the task is passed to all users in the group at the same time.
• When setting up approval rules for an approval task, you can create user-defined
attributes. Attributes are defined once and can be used across rules within the same
approval task.
• You can create two types of user-defined attributes:
– Currency-based attributes
– Summation attributes
You can define currency-based attributes to convert transaction amounts into a common
currency, then define approval rules for only that specific currency. For example, requesters
may be creating requisitions in multiple currencies. If your approval policy requires that
requisitions with amounts over 500 USD need approval from the requester manager, then
you can define this approval routing rule by defining an attribute Requisition amount in USD
and use it in a rule condition.
Summation allows you to use values computed based on specific attributes across lines,
schedules, and distributions within a document. You can specify a rule condition to use a
value based on summation data. For example, you can set up a Procurement Category
Hierarchy through the setup task: Manage Procurement Category Hierarchy where you can
define a hierarchy of grouping of purchasing categories.
If the approval policy is: If the requisition contains lines from IT where the lines total is
greater than 500, then route the requisition to the IT group for approval.
To achieve this, create a User Defined attribute for IT Spend as follows:
• User-Defined Attribute: IT Spend
• Type: Summation
• Attribute: Distribution Amount
• Match Using: Hierarchy
• Category Name Rolls up To: IT
When defining summation attribute, you can use distribution amount or the distribution
approval amount. You can also apply up to three filter criteria on the lines or distributions of
the transaction by using attribute or hierarchy. For a match using hierarchy, the following
hierarchies can be used:
• Balancing Segment
• Category Name
• Cost Center
• Management Segment
• Natural Account
In addition to user-defined attributes, each approval workflow has its own standard
attributes. These are documented in the Setting up Document Approvals, Oracle
Procurement Cloud whitepaper for each of the following workflows:
• Self Service Procurement
• Purchasing
• Supplier Registration
• Sourcing
• Supplier Spend Authorization
• Supplier Profile Change Request (very limited set of attributes updated through Supplier
Qualification Management only)
Documentation
Available in the Oracle Help Center: http://docs.oracle.com/
• Oracle Procurement Cloud Implementing Procurement
• Oracle Procurement Cloud Using Procurement
White Paper
Available on My Oracle Support (MOS):
• Setting Up Document Approvals in Oracle Procurement Cloud
(document ID 2264952.1)
https://support.oracle.com/epmos/faces/DocumentDisplay?id=2264952.1