Search Results ame_temp_old_approver_lists




Overview
Explore in AI Chat

Overview

AME_TEMP_OLD_APPROVER_LISTS is an Oracle E-Business Suite table owned by the HR schema and associated with the PER (Human Resources) product family. It belongs to the Oracle Approvals Management Engine (AME) subsystem, which is the rules-based approval routing and authorization framework used throughout EBS to determine who must approve a given transaction and in what sequence. The table name indicates its role as a staging or transitional store for prior approver list data generated by the AME approval engine. During the approval process, AME materializes an ordered list of approvers and approval groups or chains for a transaction; AME_TEMP_OLD_APPROVER_LISTS retains a snapshot of an earlier or superseded version of that ordered list. This makes it useful for comparison, historical reconstruction of approval routing decisions, and troubleshooting when an approval list is regenerated or recalculated.

From a heuristic Data Vault modeling perspective, the table is classified as standalone, meaning no foreign keys from other tables point into it. A mined foreign key relationship exists internally, with SECURITY_GROUP_ID referencing FND_SECURITY_GROUPS, indicating that the table participates in Oracle's multi-tenant security model through the standard security group mechanism rather than through a rich network of parent-child dependencies.

Key Information Stored

The table contains 17 documented columns. The most significant are:

  • TRANSACTION_ID — Identifier linking the approver list rows to the originating AME transaction.
  • APPLICATION_ID — The EBS application that owns the transaction being approved.
  • APPROVAL_TYPE_ID — Identifies the AME approval type governing the routing rules.
  • GROUP_OR_CHAIN_ID — References the approval group or approval chain definition used to resolve the list.
  • OCCURRENCE and ORDER_NUMBER — Together define the position and sequence of each approver within the list.
  • USER_ID — The specific system user selected as approver.
  • PERSON_ID — The HR person record corresponding to the approver.
  • AUTHORITY — The authority level associated with the approver entry.
  • APPROVAL_STATUS — The workflow status of the approval entry.
  • APPROVER_CATEGORY — Classifies the approver (for example, an approval group member versus a chain participant).
  • ITEM_CLASS and ITEM_ID — Identify the primary item being routed.
  • ACTION_TYPE_ID — Specifies the approval action type.
  • API_INSERTION — Indicates whether the record was inserted through the AME API.
  • SECURITY_GROUP_ID — The security group owning the record, foreign keyed to FND_SECURITY_GROUPS.

No unique index or explicit business key is documented; the surrogate identity of a row is not confirmed in the available metadata, so TRANSACTION_ID combined with GROUP_OR_CHAIN_ID, OCCURRENCE, and ORDER_NUMBER is a reasonable composite candidate key for identifying a logical approver entry.

Common Use Cases and Queries

Typical scenarios include diagnosing why a transaction routed to a particular approver, auditing changes in approver sequences after rule changes, and reporting on historical approval chains for compliance. A representative query pattern joins the table to FND_SECURITY_GROUPS on SECURITY_GROUP_ID and filters by TRANSACTION_ID and APPLICATION_ID to reconstruct the ordered approver list:

  • SELECT transaction_id, order_number, user_id, person_id, authority, approval_status FROM ame_temp_old_approver_lists WHERE transaction_id = :transaction_id ORDER BY order_number;
  • Comparing a current live approver list against the snapshot rows to detect routing drift after an AME rule modification.
  • Extracting PERSON_ID values to resolve approver identities against HR employee records for reporting.

Related Objects

The most significant related object is FND_SECURITY_GROUPS, joined on SECURITY_GROUP_ID. Because the table is classified standalone, other dependencies fall outside the documented foreign key set:

  • FND_SECURITY_GROUPS — referenced via SECURITY_GROUP_ID.
  • AME_APPROVER_LISTS (conceptual counterpart) — the current or live approver list table.
  • AME_TRANSACTIONS — parent transaction context for TRANSACTION_ID.
  • AME_APPROVAL_TYPES / AME_ACTION_TYPES — referenced conceptually by APPROVAL_TYPE_ID and ACTION_TYPE_ID.
  • HR per-person tables — resolved via PERSON_ID and USER_ID.