0% found this document useful (0 votes)
127 views5 pages

Vision Demo - How To Setup and Use AME For Inventory Approval Hierarchy Process For Cycle Count

Uploaded by

reco83
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
0% found this document useful (0 votes)
127 views5 pages

Vision Demo - How To Setup and Use AME For Inventory Approval Hierarchy Process For Cycle Count

Uploaded by

reco83
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
You are on page 1/ 5

2/1/22, 10:25 AM Document 2579544.

1
Copyright (c) 2022, Oracle. All rights reserved. Oracle Confidential.

Vision Demo - How to Setup and Use AME for Inventory Approval Hierarchy Process for Cycle
Count ? (Doc ID 2579544.1)

In this Document

Goal
Solution

APPLIES TO:

Oracle Inventory Management - Version 12.2.9 and later


Information in this document applies to any platform.

GOAL

How does AME approval hierarchy work for Cycle count approvals ?
The example shown in this note is based on data in the Vision Demo database including User, Responsibility, Item, Inventory
Organization etc.

SOLUTION

To demonstrate the steps necessary to back order staged sales order in INV Organization by API:

1 . Setup the AME approval hierarchy using - Approval Management Business Analyst Responsibility
2 . Define ABC analysis
3 . Create a new cycle count
4 . Verify if the approval goes to the users which has been setup in the approval hierarchy.
5 . Verify what happens when the approval is accepted , rejected and reassigned.

NOTE: In the images below and/or the attached document, user details / company name / address / email
/ telephone number represent a fictitious sample (based upon made up data used in the Oracle
Demo Vision instance). Any similarity to actual persons, living or dead, is purely coincidental and not
intended in any manner.

Inventory Cycle Count can be routed for approval using the AME Approval Management Engine. The document describes how
to setup AME for use with cycle count approvals. Approvers in the AME based approver list are assigned to the cycle count
based on the AME rules setup for the Inventory Cycle Count Approval transaction.

1. Approval Management Business Analyst > Business Analyst Dashboard > select the transaction type ‘INV Cycle Count
AME Approval > click on Setup icon.

https://support.oracle.com/epmos/faces/DocumentDisplay?_adf.ctrl-state=w2ul96k03_1817&id=2579544.1 1/5
2/1/22, 10:25 AM Document 2579544.1

2. 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 ‘INV Cycle
Count AME Approver’, and the user can create new attributes in AME for use in AME rules

List of seeded attributes for cycle count approval


" Organization Code
" Inventory Item
" Item Revision
" Sub-inventory
" Locator
" Lot Number
" Adjustment Account
" Cycle Count Class
" Quantity Variance % Upper Limit
" Quantity Variance % Lower Limit
" Adjustment Value Upper Limit
" Adjustment Value Lower Limit

In the above example , we used the attribute Organization code .

3. Create a Condition

Conditions identify values and value ranges for some or all of the attributes available. AME rules refer to these conditions to
determine if a particular rule is applicable for the cycle count being approved.

Specify whether the condition is ordinary, or an exception condition. . The condition will specify a value or range of values for
the attribute, so the attribute must be selected before the value(s) can be defined

Setup >Conditions > Create

Condition Type = Ordinary


https://support.oracle.com/epmos/faces/DocumentDisplay?_adf.ctrl-state=w2ul96k03_1817&id=2579544.1 2/5
2/1/22, 10:25 AM Document 2579544.1

Attribute = Organization Code (Use the Attribute List Of Values to choose the attribute on which the condition is based)

String = Enter the organization code you wish (we chose M1 )

4. Action Types

An action type is a collection of actions having similar functionality. Every action belongs to an action type. Action types are
enabled or disabled for a particular transaction type. AME may give an error when attempting to enable an action type for a
transaction if the transaction is not designed to allow that action type.

Select the Use Existing Action Type button to choose pre-defined action types available in AME.

Approval-group chain of authority with Ordering Mode=’Serial’ and Voting Method=’Serial’


Dual chains of authority Ordering Mode=’Serial’ and Voting Method=’Serial

In AME, select any or all of the following Action Types for 'JOB BASED' approvals if applicable
absolute job level / chains of authority based on absolute job level
final approver only / chains of authority containing only the final job-level approver
manager then final approver / chain of authority includes requestor's manager and then the final approver
relative job level / chains of authority based on relative job level
supervisory level / chains of authority based on number of supervisory levels
In AME, select any or all of the following Action types for 'APPROVER GROUP' approvals
post-chain-of-authority approvals / group approvals after the chain of authority
pre-chain-of-authority approvals / group approvals before the chain of authority
approval-group chain of authority / chain of authority includes an approval group
In AME, select any of all of the following Action types for 'POSITION BASED' approvals if applicable
hr position / chains of authority based on a particular HR position
hr position level / chains of authority based on HR positions

5. Approver Groups

Setup Approver Groups if additional approvers are required for particular conditions, or to specify a dynamic sql query for
additional approvers. The rules defined for the transaction can be based on Approver Groups, Jobs defined in HR setup, or

https://support.oracle.com/epmos/faces/DocumentDisplay?_adf.ctrl-state=w2ul96k03_1817&id=2579544.1 3/5
2/1/22, 10:25 AM Document 2579544.1

Positions defined in HR setup (only in R12); the rules may also use a combination of Job, Position, and Approver Group basis.

Create a approver group choosing the order number and different voting method like ‘Serial’, ‘First Responder Wins’, ‘
Consensus’ or ‘Order Number’. Add the approver types with their order numbers

For example, create XYZ approval group with Voting Method=’Serial ‘with three approvers Approver A, Approver B and
Approver C mentioning their order numbers

6. Rules

Define rules to specify approvers that should be included in the approval list under specific conditions for the requisition
approval transact.
Create a new rule for the transaction INV Cycle Count AME Approval
Specify a name for the new rule and choose the rule type and effective dates
The most common types are List Creation, Pre List Approver Group and Post List Approver Group
Use the Action Types feature to add or remove action types for the transaction
Specify one or more conditions that activate the rule. The Conditions are defined in the AME Setup, and they may be
seeded conditions or user defined conditions
Choose the Action Type and then choose a specific action. The list of actions available is dependent on the Action Type
selected

For example, create a new rule Approval Tolerance Less than 10 as below,

https://support.oracle.com/epmos/faces/DocumentDisplay?_adf.ctrl-state=w2ul96k03_1817&id=2579544.1 4/5
2/1/22, 10:25 AM Document 2579544.1

For the Cycle count Demo -review the attached document

Didn't find what you are looking for?

https://support.oracle.com/epmos/faces/DocumentDisplay?_adf.ctrl-state=w2ul96k03_1817&id=2579544.1 5/5

You might also like