Search Results ame_temp_deletions




Overview
Explore in AI Chat

Overview

AME_TEMP_DELETIONS is a table owned by the HR schema in Oracle E-Business Suite 12.1.1 and 12.2.2, registered under the PER (Human Resources) product. It forms part of the Oracle Approvals Management Engine (AME) infrastructure, which governs approver list generation and approval routing across EBS transaction types. The table name suggests a temporary or staging construct used during approval processing, most plausibly to record deletions or exceptions encountered while AME builds and reconciles approval hierarchies. The ETRM entry marks the description as "To be Updated," so authoritative functional documentation is not available; the object is confirmed VALID in the data dictionary and exposes 16 documented columns.

Under the heuristic Data Vault classification mined from the foreign key structure, the table is characterized as standalone. This is a modeling suggestion rather than a normative classification: the only documented outgoing foreign key is to FND_SECURITY_GROUPS, and no inbound dependencies were identified. As a result, AME_TEMP_DELETIONS behaves more like an isolated operational or transient table than a conformed hub, link, or satellite in a dimensional warehouse design.

Key Information Stored

The documented physical schema for 12.2.2 contains 16 columns. The most significant are:

  • TRANSACTION_ID — the transaction identifier anchoring each row to an AME approval transaction; the leading key column in practice.
  • APPLICATION_ID — the EBS application owning the transaction, referenced against FND_APPLICATION.
  • APPROVAL_TYPE_ID — links the row to a configured AME approval type.
  • GROUP_OR_CHAIN_ID — identifies the approval group or chain the deletion relates to.
  • OCCURRENCE — sequence or iteration counter within the approval process.
  • USER_ID and PERSON_ID — the system user and the HR person record, respectively.
  • SECURITY_GROUP_ID — the only documented foreign key, referencing FND_SECURITY_GROUPS; governs multi-tenant style data access in AME.
  • NAME — descriptive label for the approver, group, or chain entry.
  • APPROVER_CATEGORY — classifies the approver (for example, a specific role versus a supervisory relationship).
  • ITEM_CLASS and ITEM_ID — the AME item class and the specific item key being routed.
  • ACTION_TYPE_ID — the AME action type associated with the entry.
  • EFFECTIVE_DATE, REASON, and JUSTIFICATION — temporal and audit context for the recorded deletion or exception.

No surrogate primary key or unique index is documented in the ETRM metadata; the natural composite of TRANSACTION_ID, OCCURRENCE, and related identifiers appears to serve as the effective business key.

Common Use Cases and Queries

Because the table is operational and transient in nature, its primary use is diagnostic and audit-oriented rather than reporting. Typical scenarios include:

  • Investigating why a specific approver was dropped from a generated approval list for a transaction.
  • Reconciling AME approval history against expected routing during post-implementation testing.
  • Auditing approval changes attributable to a specific user, person, or security group.

A representative query pattern:

  • SELECT transaction_id, occurrence, person_id, name, approver_category, effective_date, reason FROM ame_temp_deletions WHERE transaction_id = :txn_id ORDER BY occurrence;
  • Join to FND_SECURITY_GROUPS on SECURITY_GROUP_ID to resolve the security group name.
  • Filter by EFFECTIVE_DATE to correlate deletions with a deployment or configuration change window.

Because rows may be purged by AME processing, extract volumes should be validated before using the table as a system of record.

Related Objects

The table's relationships are narrow. The most significant related objects are:

No AME public API is documented as writing to this table; it is maintained by internal AME processing logic.