Book Image

Oracle E-Business Suite Financials R12: A Functionality Guide

By : Mohan Iyer
Book Image

Oracle E-Business Suite Financials R12: A Functionality Guide

By: Mohan Iyer

Overview of this book

<p>Oracle EBS Financials provide organizations with solutions to a wide range of long- and short-term accounting system issues. Oracle E-Business Suite is the most comprehensive suite of integrated, global business applications that provides the most complete, integrated business intelligence portfolio<br /><br />Oracle E-Business Suite: A Functionality Guide – helps in binding the two skill sets together – knowledge of the software and the business knowledge of the user.<br /><br />This guide contains everything you need to know to maximize your implementation payback or return on investment.<br /><br />This book starts with an overview of Oracle E-Business Suite R12 where we cover the foundation features of Oracle Financial Management modules which include Navigation within Oracle E-Business Suite Release 12, Multiple Organization Access Control (MOAC), key aspects of Application Security and much more. The book then covers in detail General Ledger, Sub Ledger Accounting, Assets, Cash Management, Treasury, E-Business Tax, and much more.</p>
Table of Contents (24 chapters)
Oracle E-Business Suite Financials R12: A Functionality Guide
Credits
Foreword
About the Author
Acknowledgement
About the Reviewers
www.PacktPub.com
Preface
Index

Chapter 15. Approval Management Engine (AME)

Approval Management Engine (AME) is a product that was introduced in E-Business Suite 11i . This was on the persistent request of many users to provide a more flexible rules engine to manage approvals of transactions in the E-Business Suite software.

Prior to the introduction of this product approval was only possible by creating an approval hierarchy, job-supervisor relationship or positional. These hierarchies were driven by Oracle HRMS with data in HR organizations. This led many organizations to make extensions and modifications (customizations) to enable their approval rules to be implemented.

Prior to the introduction of AME, approvals were predominantly managed using standard approval hierarchies (based on HR data) and were built for procurement transactions. Approval of other transactions was not supported till the introduction of Oracle Workflow.

The approval hierarchies have been entrenched with most users in the positional or job-supervisor...