Search Results ame_approval_group_items




Overview
Explore in AI Chat

Overview

The AME_APPROVAL_GROUP_ITEMS table is a core configuration object within Oracle Approvals Management (AME), owned by the HR schema and categorized under the PER (Human Resources) product family. AME is the rules-based engine that determines approval routing, approval chains, and approver lists for transactions across Oracle E-Business Suite modules such as Purchasing, Payables, iExpenses, and HR. The AME_APPROVAL_GROUP_ITEMS table stores the individual items that make up an approval group — a reusable collection of approvers or parameters that AME evaluates when generating an approval list for a business transaction.

From a Data Vault modeling perspective, the heuristic classification derived from the foreign key structure treats this object as standalone. In practice, it functions as a satellite-type entity attached to the parent approval group, with its own surrogate key and effective-dating columns governing version history. This classification is offered as a modeling suggestion rather than a documented constraint.

Key Information Stored

The table contains 14 documented columns. The most significant are summarized below.

The documented unique index, AME_APPROVAL_GROUP_ITEMS_PK, spans APPROVAL_GROUP_ITEM_ID, START_DATE, and END_DATE, indicating that effective-dated versions of an item are maintained across time. The business-key candidate therefore combines the surrogate identifier with the date range.

Common Use Cases and Queries

Consultants and developers query this table when troubleshooting approval routing, auditing approval group membership, or migrating AME setups between environments. A typical query retrieves all active items for a given group:

  • SELECT approval_group_item_id, parameter_name, parameter, order_number FROM ame_approval_group_items WHERE approval_group_id = :group_id AND SYSDATE BETWEEN start_date AND end_date ORDER BY order_number;
  • Effective-dating analysis: compare START_DATE/END_DATE across rows to reconstruct the historical composition of a group.
  • Security validation: join to FND_SECURITY_GROUPS on SECURITY_GROUP_ID to confirm the correct operating unit context.
  • Migration and comparison: extract items filtered by CREATION_DATE or LAST_UPDATE_DATE to identify recent configuration changes.

Because AME caches approval group definitions, changes to this table generally require the AME cache to be refreshed before they take effect in transactional routing.

Related Objects

The following objects are most significant when working with AME_APPROVAL_GROUP_ITEMS:

  • FND_SECURITY_GROUPS — Referenced via SECURITY_GROUP_ID; enforces data security partitioning.
  • AME_APPROVAL_GROUPS — Parent table joined on APPROVAL_GROUP_ID, defining the group header.
  • AME_APPROVAL_GROUP_MEMBERS — Sibling table holding individual approver members of a group.
  • AME_APPROVERS — Defines approver definitions referenced by group items and members.
  • AME_RULES and AME_RULE_USAGES — Consume approval groups during rule evaluation to build approval lists.
  • FND_USER — Joined indirectly via audit columns (CREATED_BY, LAST_UPDATED_BY) for change attribution.

Together, these objects form the AME configuration layer that Oracle EBS relies upon for deterministic, rules-driven approval processing.