Search Results ame_approval_groups




Overview
Explore in AI Chat

Overview

AME_APPROVAL_GROUPS is a core configuration table in the Oracle E-Business Suite Approval Management Engine (AME), owned by the HR schema and catalogued under the PER – Human Resources product family. The table stores named approval groups, which define reusable sets of approvers and the rules by which those approvers are resolved at runtime. In Oracle EBS 12.1.1 and 12.2.2, AME serves as the rules engine behind the approval routing for many transaction types, including purchase requisitions, purchase orders, expense reports, journals, and HR transactions. An approval group effectively binds a business-friendly name to a query that returns the appropriate approvers for a given transaction context.

The ETRM metadata classifies this object as standalone based on heuristic Data Vault modeling, meaning it does not depend on an upstream parent in the mined FK structure. As a modeling suggestion, this table is best treated as a hub-like reference entity, since it carries its own surrogate identity and lifecycle attributes rather than serving as a link or descriptive satellite.

Key Information Stored

The table contains 15 documented columns that support identification, rule definition, and audit purposes.

  • APPROVAL_GROUP_ID – The surrogate primary key and the single most important identifier for the approval group. It is part of the composite unique index AME_APPROVAL_GROUPS_PK.
  • NAME – The user-facing name of the approval group displayed in AME setup and rule configuration screens.
  • QUERY_STRING – The SQL expression that dynamically returns the list of approvers when the group is evaluated.
  • IS_STATIC – A flag indicating whether the group is statically defined (a fixed list) versus dynamically resolved through a query.
  • DESCRIPTION – Free-text explanation of the group's business purpose.
  • SECURITY_GROUP_ID – Foreign key to FND_SECURITY_GROUPS, governing visibility and access control across the AME configuration.
  • START_DATE and END_DATE – Date-effective columns defining the validity window of the group; together with APPROVAL_GROUP_ID and ZD_EDITION_NAME they form the business-key candidate in the primary unique index.
  • OBJECT_VERSION_NUMBER – Optimistic locking column used to detect concurrent updates.
  • ZD_EDITION_NAME – Editioning attribute supporting online patching and edition-based redefinition.
  • CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN – Standard EBS audit columns capturing who created and last modified the record and when.

Common Use Cases and Queries

Administrators and technical consultants query AME_APPROVAL_GROUPS to audit approval routing, troubleshoot why a transaction routed to an unexpected approver, and confirm that a group's validity window is active. A typical reporting query joins the security group and filters on active dates:

  • List active groups: SELECT approval_group_id, name, is_static, start_date, end_date FROM ame_approval_groups WHERE SYSDATE BETWEEN start_date AND NVL(end_date, SYSDATE + 1);
  • Inspect dynamic group logic by reviewing QUERY_STRING for any group where IS_STATIC is 'N'.
  • Join to AME_APPROVAL_GROUP_MEMBERS to enumerate the members associated with a static group.
  • Cross-reference SECURITY_GROUP_ID with FND_SECURITY_GROUPS to determine which security context owns a given group.

These queries are frequently used in diagnostics for approval workflow failures and in reconciliation reports for governance and SOX audits.

Related Objects

Because the metadata documents only one explicit foreign key, the following relationships are the most significant for practical work:

  • FND_SECURITY_GROUPS – Joined on SECURITY_GROUP_ID; controls access to the approval group.
  • AME_APPROVAL_GROUP_MEMBERS – Joined on APPROVAL_GROUP_ID; holds the individual approvers belonging to the group.
  • AME_RULES / AME_RULE_DETAILS – Reference groups when defining approval routing rules.
  • AME_APPROVERS – Stores resolved approver information generated during rule evaluation.
  • AME_ACTION_TYPES and AME_CONDITIONS – Combine with approval groups to build complete transaction approval logic.
  • Public AME PL/SQL APIs, notably AME_API_PUB, retrieve and evaluate approval groups programmatically.