Approval Management

http://oracleapps88.blogspot.
com/
.C
T
APPROVAL MANAGEMENT
O
L
8
.B
8
S
P
A
E
http://oracleapps88.blogspot.com/
.C
T
What is AME?
O
Advantages of using AME
P
SSuite Application
Integration of AME with Oracle E-Business
G
O
Business Flow
L
.B
Structure of AME
8
8
Example of Approval management
used in Service Contracts
S
P
Q&A
P
A
E
What is AME?
.C
T
Oracle Approvals Management (AME)
is
a
O
Penables you
selfservice Web application that
S
G
to define business rules governing
the process
O
L
for approving transactions
in Oracle
.B
8 integrated AME.
applications that have
8
S
P
P
A
E
L
C
A
R
O
Advantages of using AME

M
Enables business analysts to specify the business rules in the form O

of
Approval Rules for an application
.C
without having to write code or customize the application. T
O
Provides a framework to define business rules for an application
so that
P
the application can communicate directly with AME
to manage the
S
approvals of a transaction.
G
Rules can be defined either specific to one application
or shared between
O
L
different applications
Provides parallel approval process, thus
.Bshortening transaction processing
8
time.
8 such as:
Supports the approval hierarchies
S
P
*Job
P
*Supervisor Hierarchy
A
*Position E
*By listC
ofL
individuals created during approval rule setup or generated
dynamically
A when the rule is invoked
Integration of AME with Oracle E-Business Suite Application
INTEGRATING APPLICATION
INTEGRATING APPLICATION.C
Service
Work in Process
Quoting
Enterprise G
Asset Management
L
Receivables
Partner Management
Field Service
E-Records
S
P
A
E
.B
8 Payables
Service Contracts
A
Payroll
Inventory
Purchasing
Work in process
Business Flow
.B
8
S
P
A
E
.C
T
Structure of AME
C
.
AME is a framework of well-defined approval
T
O
rules constructed using the following
P5
S type:
components for a given transaction
G
O
L
1. Transaction Type
.B
8
2. Attributes
8
S
3. Conditions PP
4. Actions EA
L Groups
5. Approver
C
A
6. R
Rules
O
Structure of a Rule in AME

P
.B
8
S
P
A
E
.C
T
Transaction Type
.C
A transaction type describes the type of
T
O
transaction for which business rules and
P approval
S
routings will be based. Examples of
G transaction types
O
are:
L
B
.
Purchase Requisition Approval
(Purchasing)
8
8
S Approval (Purchasing)
Requester ChangePOrder
PApproval(service contract)
Service contract
A
E
L Approval(EAM)
Work Order
C
A
R
O
.B
8
S
P
A
E
.C
T
Attributes
C
.
Attributes within AME are business variables that
T
O
represent the value of a data element of P
a given
transaction
S
G
Attributes in AME can be createdO
as being static or they
can be dynamic in nature BL
.
Attributes can be defined 8
at 3 different levels Header,
8
Line Item and Cost Center
S level.
P
Examples of attributes
are:
P
A
Contract_amount(service
contracts)
E
L
Request_Severity(service
Request)
C
A
Item_number(Purchasing)
R
O
List of AME attributes for service Request Approval
.B
8
S
P
A
E
.C
T
Conditions
.C of
Conditions are used to evaluate the value
T
O
attributes in a particular transaction
P
S
The Condition component tells
G AME engine
O
L result of the
to trigger an AME rule ifBthe
.
condition is TRUE 88
S
One or more attributes
are used to define a
P
P
condition.EA
L
Conditions defined for Purchase Requisition Approval

M
O
.C
T
O
P
S
G
O
L
.B
8
8
S
P
P
A
E
L
C
A
R
O
Action Types and Actions
.C
T in
Actions describes what should be done
O
P
AME if a particular condition is S
satisfied
by the
G
transaction
O
L
Action Type is a collection
.B of actions having
8
8 Every action belongs to
similar functionality.
S
P
an action type.
P
A
E
L
C
A
R
O
Action Types
Approver Type
final approver only
Job based
Approver Group
Abased
B
.
supervisory
8 level
8position
hr
S
P hr position level
HR Position based
.C
T
manager then final

O approver
L
relative job level
Action Type
absolute job level
pre-chain-of-authority approvals
post-chain-of-authority approvals
approval-group chain of authority
Approver Group
.C
Approver Group is used to fetch approversT
from
O
Oracle Applications (HRMS).
P
S
G
Static or Dynamic in nature
O
L the order in which
The voting method determines
.B
the Group Members are8notified and also how the
8
S approval
decision of the groups
P
P
A
E
L
C
A
R
O
Approver Groups
.B
8
S
P
A
E
.C
T
Voting Methods
Voting Regime Name
Serial
.C
T
Description
Members are notified one after the other;O

All members
P
must approve for the group to approve.
Members are notified in parallel;

GAll members must
O
approve for the group to approve.
Consensus
First-Responder-Wins Response of the first member

to respond to the
B
.
notification requesting
8 approval becomes the group's
8
approval decision.
ResponsesS
of the remaining group members are stored in
P
the AME
P transaction log and their responses are ignored.
A
Members
are notified in the order of their order
Enumbers. Members
with same order numbers are
L
notified in parallel.
C
Order-Number
Rule
O
C
.
Transforms the business rules into approval T
rules to
O list
specify approvers in the transactions approval
P
Sor Approval.
Rules can also be categorized as FYI
G
O
A rule is constructed using theLfollowing
components:
1. Rule Type
.B
8
2. Item Class
8
S
3. Category
P
P
4. ConditionsA
E
5. Actions
L
C
A
R
O
Structure of AME Rule

P
.B
8
S
P
A
E
.C
T
.B
8
S
P
A
E
.C
T
Rule Types
Description
List Creation
List Creation
Exception
List Modification
Substitution
Combination
Production
O
Rules
.C
Builds a chain-of-authority list of approvers thatT
ascend some
Oof approvers.
organizational hierarchy to generate the chain
P
Builds a chain-of-authority list of approvers
S as well. However, it is
G rule so as to require
used often used to suppress a list-creation
approvals from a certain groupO
of approvers if an additional
L
condition is met.
.B
Modify the default 8
chain of authority generated by all applicable
8 List Creation Exception rules
List Creation and
S
P approver's authority to another approver
Delegate one
P
Used
Awhen several business rules apply to exactly the same
E
business case
Rule Type
Pre/Post C
ApprovalA
Rules
Allows for additional approvers outside of a transactions generated

chain of-authority to be added to the list of approvers.
Outputs runtime values to a particular integrating transaction
AME Test Workbench
C
.
Test Workbench is an AME diagnostic utility to test and
T validate
O
the approval rules setup for a given transactionPtype.
S
G
O
L
.B
8
8
S
P
P
A
E
L
C
A
R
O
Enable AME for Purchase Requisition approval in iprocurement
.B
8
S
P
A
E
.C
T
Roles
.C
T
Approvals Management Process Owner
O
P
Approvals Management SystemSViewer
G
O
Approvals Management Business
Analyst
L
B
.
Approvals Management
8 System Administrator
8
S
Approvals Management
Administrator
P
P
A
E
L
C
A
R
O
Profile option
.B
8
S
P
A
E
.C
T

Approval Management

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

Approval Management

Uploaded by

Copyright:

Available Formats

http://oracleapps88.blogspot.

Advantages of using AME

Enables business analysts to specify the business rules in the form O

Integration of AME with Oracle E-Business Suite Application

Structure of a Rule in AME

List of AME attributes for service Request Approval

Conditions defined for Purchase Requisition Approval

Action Types and Actions

final approver only

manager then final

Members are notified one after the other;O

Members are notified in parallel;

First-Responder-Wins Response of the first member

Structure of AME Rule

Allows for additional approvers outside of a transactions generated

AME Test Workbench

Enable AME for Purchase Requisition approval in iprocurement

You might also like