Ame PDF

http://oracleapps88.blogspot.
com/
M
O
.C
T
O
P
S
APPROVAL MANAGEMENT G
O
L
.B
8
8
S
P
P
A
E
L
C
A
R
O
http://oracleapps88.blogspot.com/
M
O
•
.C
What is AME? T
• O
Advantages of using AME P
•
SSuite Application
G
Integration of AME with Oracle E-Business
• O
Business Flow L
• Structure of AME .B
8
• 8
Example of Approval management used in Service Contracts
S
• Q&A P
P
A
E
L
C
A
R
O
What is AME? M
O
.C
• Oracle Approvals Management (AME) O
T is a
self‐service Web application that Penables you
S
G
to define business rules governing the process
O
for approving transactions L in Oracle
.B
applications that have8 integrated AME.
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 Oof
“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 S to manage the
approvals of a transaction. G
O
 Rules can be defined either specific to one application or shared between
different applications L
.Bshortening transaction processing
 Provides parallel approval process, thus
time. 8
8 such as:
S
 Supports the approval hierarchies
*Job P
P
A
*Supervisor Hierarchy
*Position E
ofL
*By listC individuals created during approval rule setup or generated
A when the rule is invoked
dynamically
R
O
Integration of AME with Oracle E-Business Suite Application

M
O
INTEGRATING APPLICATION INTEGRATING APPLICATION.C
T
Service Work in Process O
P
Quoting Enterprise G
S
Asset Management
O
Partner Management L
Receivables
.B
8 Payables
Service Contracts
8
S
Field Service P Inventory
P
A
E-Records E Purchasing
L
C
A
Payroll Work in process
R
O
Business Flow M
O
.C
T
O
P
S
G
O
L
.B
8
8
S
P
P
A
E
L
C
A
R
O
Structure of AME M
O
. C
• AME is a framework of well-defined approval
T
rules constructed using the following O
P5
components for a given transactionS type:
G
O
L
1. Transaction Type .B
8
2. Attributes 8
S
3. Conditions PP
4. Actions EA
L Groups
5. Approver
C
6. R A
Rules
O
Structure of a Rule in AME M

O
.C
T
O
P
S
G
O
L
.B
8
8
S
P
P
A
E
L
C
A
R
O
Transaction Type M
O
.C
T
A transaction type describes the type of
O
P approval
transaction for which business rules and
S
routings will be based. Examples of
G transaction types
are: O
L
. B
• Purchase Requisition Approval
8 (Purchasing)
8
• S Approval (Purchasing)
Requester ChangePOrder
• Service contract PApproval(service contract)
A
E
• Work OrderL Approval(EAM)
C
A
R
O
M
O
.C
T
O
P
S
G
O
L
.B
8
8
S
P
P
A
E
L
C
A
R
O
Attributes M
O
. C
• T
Attributes within AME are business variables that
represent the value of a data element of P O
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
S level.
Line Item and Cost Center
P
• P
Examples of attributes are:
A
E
Contract_amount(service contracts)
L
C
Request_Severity(service Request)
A
R
Item_number(Purchasing)
O
List of AME attributes for service Request Approval
M
O
.C
T
O
P
S
G
O
L
.B
8
8
S
P
P
A
E
L
C
A
R
O
Conditions M
O
• Conditions are used to evaluate the value.C of
T
O
attributes in a particular transaction
P
S
• The “Condition” component tellsG AME engine
O
L result of the
to trigger an AME rule ifBthe
.
condition is TRUE 88
S
• One or more attributes
P are used to define a
P
condition.EA
L
C
A
R
O
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 M

O
.C
• Actions describes what should be doneO
T in
AME if a particular condition is S P
satisfied by the
transaction G
O
L
• .B of actions having
Action Type is a collection
8
8 Every action belongs to
similar functionality.
S
an action type. P
P
A
E
L
C
A
R
O
Action Types M
O
.C
Approver Type Action Type T
O
absolute job level
P
final approver only S
Job based G
O approver
manager then final
L
B
relative job level
.
8 level
supervisory
8position
HR Position based Shr
P hr position level
P
Abased
Approver Group pre-chain-of-authority approvals
E
L post-chain-of-authority approvals
C approval-group chain of authority
A
R
O
Approver Group M
O
.C
• Approver Group is used to fetch approversT from
O
Oracle Applications (HRMS). P
S
• Static or Dynamic in nature G
O
• The voting method determines L the order in which
.B
the Group Members are8notified and also how the
8
S approval
decision of the group’s
P
P
A
E
L
C
A
R
O
Approver Groups
M
O
.C
T
O
P
S
G
O
L
.B
8
8
S
P
P
A
E
L
C
A
R
O
Voting Methods M
O
.C
Voting Regime Name Description
T
Serial Members are notified one after the other;O
All members
P
S
must approve for the group to approve.
Consensus GAll members must
Members are notified in parallel;
O
approve for the group to approve.
L
. B
First-Responder-Wins Response of the first member to respond to the
8 approval becomes the group's
notification requesting
8
approval decision.
ResponsesS
P of the remaining group members are stored in
P transaction log and their responses are ignored.
the AME
A
Order-Number
Enumbers. Members
Members are notified in the order of their order
L with same order numbers are
C notified in parallel.
A
R
O
Rule M
O
. C
• Transforms the business rules into approval Trules to
O list
specify approvers in the transaction’s approval
P
• Rules can also be categorized as “FYI”Sor “Approval”.
G
O
• A rule is constructed using theLfollowing components:
 1. Rule Type .B
8
 2. Item Class 8
S
 3. Category P
 4. ConditionsA
P
 5. ActionsE
L
C
A
R
O
Structure of AME Rule M

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

O
. C
T validate
Test Workbench is an AME diagnostic utility to test and
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

M
O
.C
T
O
P
S
G
O
L
.B
8
8
S
P
P
A
E
L
C
A
R
O
Roles M
O
.C
• Approvals Management Process Owner
O
T
P
• Approvals Management SystemSViewer
G
• O
Approvals Management Business Analyst
L
. B
• Approvals Management8 System Administrator
8
• S
Approvals Management Administrator
P
P
A
E
L
C
A
R
O
Profile option M
O
.C
T
O
P
S
G
O
L
.B
8
8
S
P
P
A
E
L
C
A
R
O

Ame PDF

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

Ame PDF

Uploaded by

Copyright:

Available Formats

http://oracleapps88.blogspot.

Advantages of using AME

Integration of AME with Oracle E-Business Suite Application

Structure of a Rule in AME M

List of AME attributes for service Request Approval

Conditions defined for Purchase Requisition Approval

Action Types and Actions M

Structure of AME Rule M

AME Test Workbench M

Enable AME for Purchase Requisition approval in iprocurement

You might also like