Payables-Invoice-Approval

8/16/2019 Payables-Invoice-Approval

1/20

Oracle ApplicationsRelease12.1.3

Payables Invoice Approval

White Paper

GreenChain Software Solutions Pvt. Ltd.

www.greenchain.biz


2/20

Payable Invoice Approval Introduction

Structure of AME

1. Transaction Type

2. Attribute:

3. Condition:

4. Action Type:

5. Approver Group:

Approver Group – Voting Regimes

6. Rule

Requisition Approval

Payable Invoice Approval Test Workbench


3/20

Payable Invoice Approval Introduction

Payable Invoice Approval is a workflow process that enables you to automate the approval process. Ithelps in customizing and setting approval methodology based ono Approver

o Sequence of approvalo Criteria for approval

In what cases Invoice Approval workflow will not apply• When the Expense Report is imported• In the case of Recurring invoices, if approval is not required as per the template• For those invoices before this feature is enabled

Structure of AMEAME is a framework of well-defined approval rules constructed using the following 5 components for agiven

1. Transaction Type2. Attributes3. Conditions4. Actions5. Approver Groups6. Rules

1. Transaction Type:

Transaction Type is a distinct set of approval rules used by certain category of transactions in anintegrating Application

2. Attribute:

Attributes in AME are placeholders for transaction data elements. They are basic elements of an AMErule.

Attributes can be static (fixed value) or dynamic (SQL Query based). AME comes with several seededattributes for each of the transaction types in the system. If the seeded attributes cannot be used forapproval rules, then organizations can define their own attributes.

Attributes can be shared across various transaction types. Attributes can be defined at 3 different levelsHeader, Line Item and Cost Center level.

3. Condition:

The “Condition” component is used to tell AME engine to trigger an AME rule if the result of the conditionis TRUE.One or more attributes are used to define a condition. In the condition setup, an attribute is associatedwith a value or range of values. At runtime, the transaction type value is evaluated against the attributevalue. If the value transaction type value qualifies with the attribute value, the outcome of the condition isTRUE and the AME rule is eligible to trigger. Otherwise, the condition will yield FALSE and the rule shallnot apply.


4/20

Ex: This condition states if the payable Invoice Total is > 0 and < 10000 and the currency is “INR”, thentell AME to enable the rule associated with this condition to fire.

4. Action Type:

An Action Type is a collection of one or more Actions having similar functionality. An Action tells AME howto modify a transaction’s approval process in a certain way.AME provides several seeded action types or

one may define a custom action type. The seeded Action Types available in AME can be used to ascendorganization hierarchies. Seeded Actions Types available in AME cannot be used with any transactiontype.

5. Approver Group:

Approver Group is used to fetch approvers from Oracle Applications (HRMS). Approver Group can bestatic or dynamic in nature.

Static approver group, the approvers are constant, added at the time of Approver Group setup and will belisted as Group Members.

Dynamic approver group, the approvers are generated at run time using an SQL Query in the approver

group setup and are later identified as Group Members at run time.

Approver Group may have a voting method assigned such as Consensus, First Responder Wins, OrderNumber and Serial. The voting method assigned to an approver group determines the order in which theGroup Members are notified and also how the decision of the group’s approval.

Approver Group – Voting Regimes

• Serial – Members are notified one after the other according to their member order (ties broken

arbitrarily). All members must approve.

• Consensus – Members notified in parallel. All must approve.

• First-Responder-Wins - Members notified in parallel. First responder = group’s decision.

• Order-Number – Members notified according to order, ties notified in parallel. All must respond.

6. Rule

A Rule (also called as “Approval Rule”) in AME is used to transform the business rules into approval rulesto specify approvers in the transaction’s approval list.

Rule is the last component step in AME configuration process. A rule is constructed using the followingcomponents: Rule Type, Item Class, Category, Conditions and Actions


5/20

List-Creation

If invoice amount > $1000 INR (condition), THEN require approval one job levels above requestor.

List-Creation Exception

If invoice amount > $500 INR and pay group = Employee, THEN require approval two job levels above

requestor.

List-Modification

If any approver = Sam Clark, THEN grant final authority.

Pre and Post

If expenditure category = Computers, THEN require approval from IS department.


6/20

Requisition Approval


7/20

Payable Invoice Approval Test Workbench

Setting up Responsibilities

1. Login as SYSADMIN user (or a user that has full User Management functionality.2. Create a New user account and give an appropriate effective date. Do NOT add any Approval

Responsibility.3. Save the record.


8/20

4 Switch the responsibility to User Management and Navigate to the Users function

5. Query for the newly created user.

6. Click on the update action from the result table.

7. Click on the Assign Roles button


9/20

8. Change the “Search By” field from “Roles and Responsibilities” to “Roles”9. in the search window, query for Approval%10. Following five roles will be displayed.11. Select only the “Approvals Management Administrator” and “Approvals Management Business

Analyst” roles.

12. After selecting the Roles, provide the Justification for the role and the effective date.


10/20

13. Now switch the responsibility to Functional Administrator.14. Click on create grants under the grants sub-tab.

15. Enter a Grant Name and provide an effective date.16. Navigate to the security Context region and select the Grantee Type as ‘Specific User’17. In the Grantee field select the newly created User18. In the Data Security region select ‘AME Transaction Types’ as the Object.


11/20

19. Clicking Next will take you to the ‘Select Object Data Context’ page’.20. You have a default value of ‘All Rows’ in the Data Context Type, leave it as it is, and navigate further.


12/20

21. In the ‘Object parameter and Select Set’ page, enter ‘AME calling applications’ as the value in the Setfield.

22. Clicking Next will take you to the Review page.23. Verify the information and submit the transaction.24. Now Switch the responsibility to System Adminstrator and Navigate to System Profiles.25. Query for the profile ‘AME: Installed’ at the required level and set the value to ‘Yes’.26. Save the data.

27. Now you can login as the newly created user.28. You should be able to see the following responsibilities:


13/20

a. Approvals Management Administratorb. Approvals Management Business Analyst

29 Select Payable Invoice Approval as Transaction type


14/20


15/20

Condition: Select “is greater than or equal to “0” and less than equal to “10000””

Fill in the required info included the name of the group


16/20

Create Rules with the help of condition and action.

Go to Payables Option select Approval (T), should be enable “use Invoice Approval workflow” and enable

“Require validation before Approval.


17/20

Enter supplier invoice details and amount should be “>0 and Before validate the invoice Approval status as “Required”


18/20

->After validate the invoice Approval status as “Initiated”

Once Invoice validates and create accounting completed, invoice goes to supervisor whom approves this

invoice.

Go to Reports(M)->select View Invoice Approval History. Here we can see Approval date, Action,

Approver name and Amount Reviewed.


19/20

Supervisor will approve/reject/reassign based on the terms.


20/20

->Once Approver has approved the invoice then invoice Approval status has changed to “Workflow

Approved”

Documents

Payables-Invoice-Approval