You are on page 1of 22

AME

An Overview in Apps
Ravikumar Singh Suyog Manwatkar Deloitte Consulting LLP 09 Oct,2013

Agenda or contents slide


What is AME? Advantages of AME How to get AME access Definition Process of AME Components 1)Rules 2)Conditions 3)Action Types 4)Approval Group 5)Transaction Types

Examples in Purchasing and HR Questions and Answers?

What is AME ?

A way for Oracle to manage Approvals for its applications

AME has self service business analyst dashboard to perform maintenance.

Uses Business specific rule to manage the approval required for a specific type of transactions

Client logo

-3-

Client logo

AME.pptx

Advantages of AME
Enables business analysts to specify the business rules in the form of "Approval Rules" for an application without having to write code or customize the application. Provides a framework to define business rules for an application so that the application can communicate directly with AME to manage the approvals of a transaction. Rules can be defined either specific to one application or shared between different applications. Provides parallel approval process, thus shortening transaction processing time. Supports the approval hierarchies such as:

o Job o Supervisor Hierarchy

o Position
o By list of individuals created during approval rule setup or generated dynamically when the rule is invoked
Client logo

-4-

Client logo

AME.pptx

Modules that currently utilize AME


Applications Module Advanced Benefits Bills of Material Cash Management E-Records Engineering Enterprise Performance Foundation Human Resources Internal Controls Manager Inventory Labor Distribution Learning Management Lease Management Partner Management Payables Process Manufacturing Inventory Process Manufacturing Logistics Process Manufacturing Process Execution Process Manufacturing Product Development Public Sector HR Purchasing Quality Quoting Receivables Sourcing Trade Management Work in Process iAssets Transaction Types 2 4 1 13 9 1 2 3 11 1 1 8 4 2 13 2 14 44 1 8 23 1 4 1 2 3 2

Client logo Client logo


AME.pptx

-5-

Sys admin steps to enable AME


Assign responsibilities/roles to your system administrators Setup AME System Wide Configuration Setup module specific Profile Options Assign responsibilities/roles to your functional users who will be setting up AME Setup AME functionality for module Steps 1-4 are only covered briefly here and are quite involved, we are going to instead concentrate on step 5

Client logo

-6-

Client logo

AME.pptx

Assign Resp/roles to Sys. Admins


AME uses the new User Management functionality You must assign the responsibility User Management to the people who will assign AME responsibilities to others

Have to do this assignment as the SYSADMIN Ora Apps user


The role to be assigned is Security Administrator Using the responsibility Approvals Management Administrator the SysAdmins can assign setup the AME Configuration Parameters. For the most part these parameters can remain with their default values. The SysAdmins must assign AME functional roles to the required OraApps user accounts using the User Management The responsibility Approvals Management Business Analyst is assigned along with the required roles, viewable in the Indirect Responsibilities tab of the Define Users form. 'AME: Installed' at the Application Levels
Client logo

-7-

Client logo

AME.pptx

AME Approvers

AME Approvers must be setup as FND_USERs

AME Approvers must be setup as Employees

Client logo

-8-

Client logo

AME.pptx

Definition of the AME Process


1. 2. 3.

Define Attributes Define Conditions Define Action Types

4.
5. 6.

Define Approval Groups


Define Rules Test Process

All of this takes place on the AME Business Analyst Dashboard

Client logo

-9-

Client logo

AME.pptx

Structure of Rule in AME

Client logo

- 10 -

Client logo

AME.pptx

AME Attributes

AME Attributes are the variables which are evaluated by your AME Process as it runs AME Attributes can be Header or Line Item Dynamic Attributes are filled in at run time by an SQL query AME Attribute values are all stored internally as string values limited to a length of 100 characters Most customization activity is around Attributes

Client logo

- 11 -

Client logo

AME.pptx

Attributes

Attributes are the base element for an AME Rule. Attribute values are retrieved from the Oracle E-Business Suite Applications database or derived from values in the database. AME is seeded with attributes relevant to the transaction type, and the user can create new attributes in AME for use in AME rules. Select the Attributes link to view or add attributes for the selected transaction type Use the Previous and Next links to scroll through the existing attributes. Some of the attributes include ITEM_CATEGORY, ITEM_NUMBER as well as other attributes. When AME approvals is enabled, these values get populated for the purchasing document, and AME uses this information to determine the appropriate AME rule(s) to use.

In addition to the seeded attributes, a customized attribute can be created.

Client logo

- 12 -

Client logo

AME.pptx

AME Attributes Data Types


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

Client logo

- 13 -

Client logo

AME.pptx

Dynamic Attributes

Dynamic attributes can be populated by an SQL expression.Select to_char(sysdate, ame_util.versionDateFormatModel) from dual; All Attributes are stored internally as strings. Must return one row. The :transactionid is passed as a bind variable to the query. This is the key for the AME processes execution. Limitation on SQL of 2000 characters. 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. Drawback is that Currency values require three PL/SQL function calls

Client logo

- 14 -

Client logo

AME.pptx

Conditions
There are two types of conditions: Regular Conditions (Ordinary) Simple logic statements Technical Review Required = Y Discount is greater than -12 and less than or equal to -7.23

List Modifier Conditions


Any approver is Adams, John

Client logo

- 15 -

Client logo

AME.pptx

Action Types
Action Types are groups of similar actions that 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

Client logo

- 16 -

Client logo

AME.pptx

Some of the Chain of Authority Action Types


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
- 17 Client logo Client logo
AME.pptx

Absolute Job Level


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

Client logo

- 18 -

Client logo

AME.pptx

List Modification Action Types


final authority grant final authority to an approver nonfinal authority extend the chain of authority past an approver

- 19 -

Client logo

AME.pptx

19

Client logo

Pre or Post List Approval roups


These actions add a list of approvers either before or after the approval is built.

Approvals in group can be serial or parallel.

Client logo

- 20 -

Client logo

AME.pptx

Approval Groups
Either static or dynamic lists of approvers 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)

Client logo

- 21 -

Client logo

AME.pptx

Copyright 2012 Deloitte Development LLC. All rights reserved.

You might also like