Академический Документы
Профессиональный Документы
Культура Документы
Approvals Management
Engine
John Peters
JRPJR, Inc.
john.peters@jrpjr.com
01/17/07 NorCa
01/24/06 NorCa
01/24/06 NorCa
01/24/06 NorCa
01/24/06 NorCa
01/24/06 NorCa
10
11
12
01/24/06 NorCa
13
14
01/24/06 NorCa
15
AME Approvers
AME Approvers must be setup as
FND_USERs
AME Approvers must be setup as
Employees
01/24/06 NorCa
16
17
01/24/06 NorCa
18
Define Attributes
Define Conditions
Define Action Types
Define Approval Groups
Define Rules
Test Process
All of this takes place on the AME
Business Analyst Dashboard
01/24/06 NorCa
19
01/24/06 NorCa
20
AME Dashboard
01/24/06 NorCa
21
AME Attributes
01/24/06 NorCa
22
Boolean
True or False
Currency
(amount,denomination,conversion method)
Date
YYYY:MON:DD:HH24:MI:SS
Number
Integer or decimal
(using users character set decimal point)
String
Up to 100 characters in length
01/24/06 NorCa
23
Currency Attributes
An SQL routine which populates a
Currency Attribute must return three
columns:
Amount = decimal value
Denomination = 3 Char Currency Code
Conversion Method = Corporate
24
Number Attributes
SQL routines should run the
numeric values through the
PL/SQL function:
fnd_number.number_to_canonical
01/24/06 NorCa
25
Date Attributes
Stored as a string
There is a PL/SQL date format
mask you can use to format dates:
ame_util.versionDateFormatModel
YYYY:MON:DD:HH24:MI:SS
01/24/06 NorCa
26
Dynamic Attributes
01/24/06 NorCa
27
PL/SQL Usage
It is often advantageous to call a
PL/SQL function rather than embed
an SQL script in the attribute
definition.
This has the added benefit of
preventing functional users who can
setup AME from modifying the
underlying SQL.
01/24/06 NorCa
28
PL/SQL Example
01/24/06 NorCa
29
01/24/06 NorCa
30
Conditions
There are two types of conditions:
Regular Conditions
Simple logic statements
01/24/06 NorCa
31
Regular Conditions
01/24/06 NorCa
32
Regular Conditions
01/24/06 NorCa
33
01/24/06 NorCa
34
Action Types
Action Types are groups of similar
actions that build your approval list for
you.
Common Predefined Action Rule Types
are:
01/24/06 NorCa
35
Position
hr position
hr position level
Hierarchy
manager then final approver
supervisory level
01/24/06 NorCa
36
Job Level
01/24/06 NorCa
37
01/24/06 NorCa
38
01/24/06 NorCa
39
nonfinal authority
extend the chain of authority past an
approver
01/24/06 NorCa
40
01/24/06 NorCa
41
01/24/06 NorCa
42
01/24/06 NorCa
43
Approval Groups
Either static or dynamic lists of
approvers
Approvals can be:
01/24/06 NorCa
44
Approval Groups
01/24/06 NorCa
45
Rules
Rules are where one or more conditions result in an action.
This is what everyone has been waiting for.
01/24/06 NorCa
46
01/24/06 NorCa
47
01/24/06 NorCa
48
01/24/06 NorCa
49
01/24/06 NorCa
50
01/24/06 NorCa
51
01/24/06 NorCa
52
My Suggestion
AME is complex, dont try to
understand it all at once
Put in some OraApps Module
Transactions
Dive into AME and just try some
simple test cases
You will end up making changes
With the Test Workbench you can
easily see how your setups are
working
01/24/06 NorCa
53
Summary
Approvals Management Engine allows
for complex approval processes
Customizations are primarily
accomplished with minimal code to
pull in new Attribute values
This product is complex and the
documentation is very difficult to
understand, hopefully this
presentation has given you a brief
introduction to Approvals
Management Engine
01/24/06 NorCa
54
My contact information:
John Peters
john.peters@jrpjr.com
http://www.jrpjr.com
01/24/06 NorCa
55