3.09 Peters

7/31/2019 3.09 Peters

1/55

01/17/07 NorCal OAUG TrainingDay, Paper 3.9

John Peters, JRPJR, Inc. 1

Getting Started With ApprovalsManagement Engine

John Peters

JRPJR, [email protected]

7/31/2019 3.09 Peters

2/55



How many of you have used approvalsin Workflow?

How many of you have had tocustomize the Workflow to accomplishthe required approvals?

How many of you have tried ApprovalsManagement Engine?

Before We Start A QuickAudience Survey

7/31/2019 3.09 Peters

3/55



E-Business Suite Modules that currently utilizeApprovals Management Engine

Technically where is AME

Where does Approvals Management Engine

fit into the Workflow approvals processing

System Administration steps to enableApprovals Management Engine (briefly)

Definition of AME processes Testing AME processing

Quick Demo of AME (time permitting)

What we are going to cover

7/31/2019 3.09 Peters

4/55



Modules that currently utilize AMEApplications Module Transaction Types

Advanced Benefits 2

Bills of Material 4

Cash Management 1

E-Records 13

Engineering 9

Enterprise Performance Foundation 1

Human Resources 2

Internal Controls Manager 3

Inventory 11

Labor Distribution 1

Learning Management 1Lease Management 8

Partner Management 4

Payables 2

Process Manufacturing Inventory 13

Process Manufacturing Logistics 2

Process Manufacturing Process Execution 14

Process Manufacturing Product Development 44

Public Sector HR 1

Purchasing 8Quality 23

Quoting 1

Receivables 4

Sourcing 1

Trade Management 2

Work in Process 3

iAssets 2

7/31/2019 3.09 Peters

5/55



Requisition Approvals can not beforwarded to other approvers

Quote Approvals can not processapprovals in parallel

Please review the restrictions for yourOraApps Module on Metalink

Many OraApps Modules Have Restrictions

7/31/2019 3.09 Peters

6/55



Tables exist in HR schema

Tables begin with AME_%

This tells us that Oracle views this as acomponent of HR

This is very important to realize since thefunctionality is HR centric in the approval listbuilding process

Technically Where is AME

7/31/2019 3.09 Peters

7/55



AME builds approval lists.AME uses the logic you setup to controlthe building of the approval list.

AME does not send notifications orhandle any of the other required gluein an approval process.

Typically AME is just a few new

processes/functions on an existingapproval process defined in Workflow.

How does AME fit in?

7/31/2019 3.09 Peters

8/55



Using the Requisition Approval process as an example

7/31/2019 3.09 Peters

9/55



Using the Requisition Approval process as an example (cont.)

7/31/2019 3.09 Peters

10/55



Using the Requisition Approval process as an example (cont.)

7/31/2019 3.09 Peters

11/55



1. Assign responsibilities/roles to your system

administrators2. Setup AME System Wide Configuration3. Setup module specific Profile Options4. Assign responsibilities/roles to your

functional users who will be setting up AME5. Setup AME functionality for module

Steps 1-4 are only covered briefly here and

are quite involved, we are going to insteadconcentrate on step 5

Sysadmin steps to enable AME

7/31/2019 3.09 Peters

12/55



AME uses the new User Managementfunctionality

You must assign the responsibility UserManagement to the people who will

assign AME responsibilities to others Have to do this assignment as the

SYSADMIN OraApps user

The role to be assign is SecurityAdministrator

Assign resp/roles to Sys. Admins

7/31/2019 3.09 Peters

13/55



Using the responsibility ApprovalsManagement Administrator theSysAdmins can assign setup the AMEConfiguration Parameters.

For the most part these parameters canremain with their default values.

Setup AME Configuration Parameters

7/31/2019 3.09 Peters

14/55



The SysAdmins must assign AMEfunctional roles to the required OraAppsuser accounts using the UserManagement

The responsibility ApprovalsManagement Business Analyst isassigned along with the required roles,viewable in the Indirect Responsibilitiestab of the Define Users form.

Assign resp/roles to functional super users

7/31/2019 3.09 Peters

15/55



'AME:Installed' at the Application Levels Oracle Quoting = Yes

For quoting there are several others to

setup, these are module specific 'ASO : Enable Approvals' = Yes

'ASO : Allow Skip Approvers' = No

Setup AME Profile Options

7/31/2019 3.09 Peters

16/55



AME Approvers must be setup asFND_USERs

AME Approvers must be setup asEmployees

AME Approvers

7/31/2019 3.09 Peters

17/55

01/24/06 NorCal OAUG TrainingDay, Paper 3.9 John Peters, JRPJR, Inc. 17

The responsibility to be used is:Approvals Management Business Analyst

Each OraApps module has differentspecific values, but the same generalsetup process holds true for each.

Setup AME Module Functionality

7/31/2019 3.09 Peters

18/55


An example of Quote Approval Requirements:

Discounts have different approval limits by product line byoperating unit

Terms non-standard (non-default)

If the Sales Person is New

Sales Person Technical Review Required

Total Quote Price is $0

Verify quote total is not less than GSA total

Remove Service Agreement items from quote/discount totals

Quote approvals go no higher than the VP of Sales

All of these were implemented through customized ofAME Attributes

AME Allows For Very Complex Approval Rules

7/31/2019 3.09 Peters

19/55


1. Define Attributes

2. Define Conditions

3. Define Action Types

4. Define Approval Groups

5. Define Rules

6. Test Process

All of this takes place on the AMEBusiness Analyst Dashboard

Definition of the AME Process

7/31/2019 3.09 Peters

20/55


Example of Approval Rules

7/31/2019 3.09 Peters

21/55


AME Dashboard

7/31/2019 3.09 Peters

22/55


AME Attributes are the variables which areevaluated by your AME Process as it runs

AME Attributes can be Header or Line Item

Dynamic Attributes are filled in at run time by anSQL query

AME Attribute values are all stored internally as

string values limited to a length of 100 characters

Most customization activity is around Attributes

AME Attributes

7/31/2019 3.09 Peters

23/55


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

AME Attributes Data Types

7/31/2019 3.09 Peters

24/55


An SQL routine which populates aCurrency Attribute must return threecolumns:

Amount = decimal value

Denomination = 3 Char Currency Code

Conversion Method = Corporate

Static definitions are like the following:5000.00,USD,Corporate

Currency Attributes

7/31/2019 3.09 Peters

25/55


SQL routines should run the numericvalues through the PL/SQL function:fnd_number.number_to_canonical

Number Attributes

7/31/2019 3.09 Peters

26/55


Stored as a string

There is a PL/SQL date format maskyou can use to format dates:ame_util.versionDateFormatModel

YYYY:MON:DD:HH24:MI:SS

Notice there are no spaces.

Date Attributes

7/31/2019 3.09 Peters

27/55

7/31/2019 3.09 Peters

28/55


It is often advantageous to call aPL/SQL function rather than embed anSQL script in the attribute definition.

This has the added benefit ofpreventing functional users who cansetup AME from modifying theunderlying SQL.

Drawback is that Currency values requirethree PL/SQL function calls.

PL/SQL Usage

7/31/2019 3.09 Peters

29/55


PL/SQL Example

7/31/2019 3.09 Peters

30/55

01/24/06 NorCal OAUG Training

Day, Paper 3.9


PL/SQL Currency Example

You end up with Currency PL/SQL calls like the following.

select MY_PACKAGE.GET_MY_AMOUNT(:transactionId),MY_PACKAGE.GET_MY_CURRENCY(:transactionId),MY_PACKAGE.GET_MY_CONVERSION_TYPE(:transactionId)

from dual

7/31/2019 3.09 Peters

31/55


Day, Paper 3.9


There are two types of conditions: Regular Conditions

Simple logic statements Technical Review Required = Y

Discount is greater than -12 and less than orequal to -7.23

List Modifier Conditions

Any approver is Adams, John

Conditions

7/31/2019 3.09 Peters

32/55


Day, Paper 3.9


Regular Conditions

7/31/2019 3.09 Peters

33/55


Day, Paper 3.9


Regular Conditions

7/31/2019 3.09 Peters

34/55


Day, Paper 3.9


List Modifier Conditions

7/31/2019 3.09 Peters

35/55


Day, Paper 3.9


Action Types are groups of similar actionsthat build your approval list for you.

Common Predefined Action Rule Types are:

Chain of authority action types List Modification action types

Post List Approval Group

Pre List Approval Group

Action Types

7/31/2019 3.09 Peters

36/55


Day, Paper 3.9


Job Level

absolute job level chains of authority based on absolute job level relative job level

chains of authority based on relative job level

final approver only chains of authority containing only the final job-level approver

Position hr position

chains of authority based on a particular HR position

hr position level chains of authority based on HR positions

Hierarchy manager then final approver

chain of authority includes requestor's manager and then the final approver

supervisory level chains of authority based on number of supervisory levels

Some of the Chain of Authority Action Types

7/31/2019 3.09 Peters

37/55


Day, Paper 3.9


Job Level

7/31/2019 3.09 Peters

38/55


Day, Paper 3.9


Chain of authority action types

7/31/2019 3.09 Peters

39/55


Day, Paper 3.9


Actions:

Require approvals up to at most level 2 Require approvals up to at most level 3

or

Require approvals up to at least level 2

Require approvals up to at least level 3

Whats the difference: Chain of approvers have levels 1,2,3,5 (4 is missing)

Requires Level 4 approval At most => 1,2,3

At least => 1,2,3,5

Absolute Job Level

7/31/2019 3.09 Peters

40/55


Day, Paper 3.9


final authority

grant final authority to an approver

nonfinal authority

extend the chain of authority past anapprover

List Modification Action Types

7/31/2019 3.09 Peters

41/55


Day, Paper 3.9


List modification action types

7/31/2019 3.09 Peters

42/55


Day, Paper 3.9


These actions add a list of approverseither before or after the approval isbuilt.

Approvals in group can be serial orparallel.

Pre or Post List Approval Groups

7/31/2019 3.09 Peters

43/55


Day, Paper 3.9


Pre or Post List Approval Groups

7/31/2019 3.09 Peters

44/55


Day, Paper 3.9


Either static or dynamic lists ofapprovers

Approvals can be:

Serial Voting (one after another, all for approval)

Consensus Voting (majority wins)

First-Responder-Wins Voting (parallel voting)

Order-Number Voting(one after another, all for approval)(allows for parallel voting)

Approval Groups

7/31/2019 3.09 Peters

45/55


Day, Paper 3.9


Approval Groups

7/31/2019 3.09 Peters

46/55


Day, Paper 3.9


Rules Rules are where one or more conditions result in an action.

This is what everyone has been waiting for.

7/31/2019 3.09 Peters

47/55


Day, Paper 3.9


Rules Level 2 Approval Actual Definition form

7/31/2019 3.09 Peters

48/55


Day, Paper 3.9


Rules List Modification Actual Definition form

7/31/2019 3.09 Peters

49/55


Day, Paper 3.9


Testing the Process AME has an excellent Test Workbench for seeing how

all these rules will actually work in real life.

7/31/2019 3.09 Peters

50/55


Day, Paper 3.9


Testing the Process Put in Transaction ID. For Quoting that is the Quote Header ID.

Historical transactions are required.

7/31/2019 3.09 Peters

51/55


Day, Paper 3.9


Testing the Process This dumps the attribute values

7/31/2019 3.09 Peters

52/55


Day, Paper 3.9


Testing the Process This dumps rules and final approver list

7/31/2019 3.09 Peters

53/55


Day, Paper 3.9


AME is complex, dont try to understand

it all at once

Put in some OraApps ModuleTransactions

Dive into AME and just try some simpletest cases

You will end up making changes

With the Test Workbench you can easilysee how your setups are working

My Suggestion

7/31/2019 3.09 Peters

54/55


Day, Paper 3.9


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 tounderstand, hopefully this presentation

has given you a brief introduction toApprovals Management Engine

Summary

7/31/2019 3.09 Peters

55/55

01/24/06 NorCal OAUG Training John Peters JRPJR Inc 55

My contact information:

John [email protected]://www.jrpjr.com

Additional reference papers can befound at:http://www.norcaloaug.org

http://www.jrpjr.com

Documents

3.09 Peters