Search Results ame_temp_transactions




Overview
Explore in AI Chat

Overview

The AME_TEMP_TRANSACTIONS table resides in the HR schema and belongs to the Oracle Human Resources (PER) product family within Oracle E-Business Suite 12.1.1 and 12.2.2. It forms part of the Oracle Approvals Management Engine (AME) infrastructure, which governs approval routing, hierarchy evaluation, and transaction authorization for a wide range of EBS business flows such as requisitions, purchase orders, expense reports, and HR personnel actions.

Despite the "TEMP" naming convention, this table is a persistent staging and processing structure that captures transaction metadata submitted to AME for approval evaluation. Each row represents a discrete transaction instance — identified by an application context and a transaction identifier — together with requestor information, descriptive text, deviation flags, and a set of generic attribute columns used by AME rule evaluation logic. The presence of ROW_TIMESTAMP and END_DATE columns suggests the table supports temporal tracking of transaction state transitions or versioning.

From a Data Vault modeling perspective, the ETRM metadata classifies this object heuristically as standalone. The only documented foreign key relationship (SECURITY_GROUP_ID referencing FND_SECURITY_GROUPS) confirms that the table functions independently as an operational staging entity rather than as a strictly conformed dimension or transactional fact, since it does not participate in a multi-hub integration pattern within the mined FK structure.

Key Information Stored

The table contains 19 documented columns. The primary key is defined by the unique index AME_TEMP_TRANSACTIONS_PK on the composite business key (APPLICATION_ID, TRANSACTION_ID), which uniquely identifies each transaction submitted to AME within the context of its owning application.

  • APPLICATION_ID — Identifies the EBS application (e.g., Purchasing, iProcurement, OTL) that originated the transaction. Part of the composite primary key.
  • TRANSACTION_ID — The transaction identifier within the source application. The second component of the composite primary key.
  • TEMP_TRANSACTIONS_ID — A surrogate identifier used internally for row-level tracking.
  • SECURITY_GROUP_ID — Foreign key to FND_SECURITY_GROUPS, controlling row-level security and access isolation across operating units or business groups.
  • TRANSACTION_REQUESTOR — The person or user who initiated the transaction, enabling AME to resolve the requestor's approval hierarchy.
  • TRANSACTION_DESCRIPTION — Human-readable description of the transaction, useful for reporting and audit trails.
  • TRANS_DEVIATION_FLAG — Indicates whether the transaction deviates from standard AME routing rules, typically triggering exception handling.
  • ROW_TIMESTAMP — Timestamp of the row's last modification, supporting concurrency control and change tracking.
  • END_DATE — Effective end date, indicating when the transaction record or its approval context expires.
  • TXN_ATTRIBUTE_1 through TXN_ATTRIBUTE_8, TXN_ATTRIBUITE_9, TX_ATTRIBUTE_10 — Generic attribute columns populated by the calling application to supply AME rule evaluation criteria (e.g., amounts, categories, cost center values).

Common Use Cases and Queries

This table is primarily queried during AME troubleshooting and approval-cycle diagnostics. A common pattern retrieves all transactions for a given application and security group within a time window:

  • SELECT * FROM AME_TEMP_TRANSACTIONS WHERE APPLICATION_ID = 200 AND ROW_TIMESTAMP >= SYSDATE - 7;
  • SELECT TRANSACTION_ID, TRANSACTION_REQUESTOR, TRANS_DEVIATION_FLAG FROM AME_TEMP_TRANSACTIONS WHERE SECURITY_GROUP_ID = :p_sec_group;

Reporting use cases include auditing deviation-flagged transactions, reconciling AME-routed approvals against source documents, and analyzing requestor approval patterns. The generic TXN_ATTRIBUTE_* columns are frequently inspected when debugging why AME selected a particular approver chain, since these values feed directly into rule evaluation.

Related Objects

  • FND_SECURITY_GROUPS — Referenced via SECURITY_GROUP_ID; governs row-level access.
  • AME_TRANSACTIONS — The primary AME transaction store; AME_TEMP_TRANSACTIONS typically stages or mirrors data before or during processing.
  • AME_APPROVAL_TRANSACTIONS — Holds approval history for processed transactions.
  • AME_RULES / AME_RULE_USAGES — Rules evaluated against the attribute columns in this table.
  • FND_APPLICATION — Resolves APPLICATION_ID to application short names.
  • PER_ALL_PEOPLE_F — Resolves TRANSACTION_REQUESTOR to a person record for hierarchy evaluation.