Review EBS product's new releases & features, troubleshooting tips & tricks, best practices, upcoming webcasts

Oracle AME Integrated With GL Journal Approvals. Business Considerations In Implementing This Enhancement

Adriana Bacila
Senior Principal Technical Support Engineer

Oracle Approvals Management (AME) is an Application that provides the users with multiple options to define business rules applying to processes related to approving transactions in Oracle Applications where AME was integrated. 

Recently General Ledger Journals Approval process has been integrated with AME and Workflow, enabling enhanced methods for journals approval processes.

Find below a few relevant details that may help decide in bringing this enhancement to the business: 

  • Can Standard Journal Approval still be used? 

Yes, it is possible to use AME Journal Approval or the Standard GL processes; this is controlled by profile option setup: GL: Use Approval Management (AME).

  • How are organization changes affecting the approval process?
 AME recalculates the chain of approvers after each approval, therefore each transaction will be approved under the latest conditions being set up. 
  • Is the Preparer of the journal affected if AME Journal Approval is used?

The answer is Yes. If AME Journal Approval is enabled, this profile option will not be considered: Journals: Allow Preparer Approval; if the business requires to use this profile in order to control Preparer's access to approve the journal he creates, then use Standard Journal approval in GL as the only method that will take this profile into consideration.  However you may include the Preparer in the Approvers Group and get the same functionality working with AME  even without the profile setup. 

  • Is Approval Limits setup considered by AME?
Maintaining Approval Limits is not mandatory for AME but this setup step could be useful for subsequent AME definitions. 
  • What are the right business situations where AME Journal Approval should be used? 

There is no right or wrong here, this is entirely business decision depending on organizational structures and separations of duties. AME Journal Approval is more flexible, providing ways to be proactive by automatically detecting and routing the journals to approvers according to the separation of duties and not mandatory based on hierarchy; this is very relevant especially for those organizations where the hierarchy is very complex or the approval roles are granted based on skill sets and capabilities of individuals, rather than considering hierarchy only. 

This new feature enables enterprises to enhance their governance, control and compliance with pre-set business rules.  

See how it works here:

Oracle General Ledger Journal Approvals Integration with Oracle Approvals Management (AME) and Oracle Workflow (Doc ID 2038960.1)


Join the discussion

Comments ( 3 )
  • Maha Friday, December 2, 2016

    Is any patch required to be applied to enable the GL journal Approval AME?

    our application version is 12.2.3

  • Adriana Tuesday, December 6, 2016


    yes, the required patch is provided through

    Oracle General Ledger Journal Approvals Integration with Oracle Approvals Management (AME) and Oracle Workflow (Doc ID 2038960.1)

    Kind regards!

  • Abdellatif Mohamed Friday, February 28, 2020
    Nice article, very helpful
    Just one question:
    In GL builtin approval, the supervisory chain is based on the journal preparer 'the person who clicks the approve button'
    But in AME the supervisory chain is based on the journal creator

    Now, using AME is there any way to build the supervisory chain based on the preparer?

    I mean other than creating an approval group that gets the journal preparer superior from HR tables

    or changing the query of AME attribute 'TRANSACTION_REQUESTOR_PERSON_ID'

    on EBS 12.1.3

Please enter your name.Please provide a valid email address.Please enter a comment.CAPTCHA challenge response provided was incorrect. Please try again.