Search Results ame_temp_insertions




Overview
Explore in AI Chat

Overview

AME_TEMP_INSERTIONS is an Oracle E-Business Suite table owned by the HR schema and registered under the PER (Human Resources) product family. It is part of the Oracle Approvals Management Engine (AME) infrastructure, which governs approval routing, approver list generation, and approval rule evaluation across EBS transaction types. The table functions as a staging and audit repository for approver insertions and related approval-routing records generated during AME processing of a transaction. When an approval workflow is initiated, AME evaluates its rule definitions and materializes the resulting approver list, insertion order, and supporting attributes into structures such as this one before the approval hierarchy is consumed by downstream workflow or notification activities.

From a Data Vault modeling perspective, the mined metadata classifies this object heuristically as standalone, with no foreign keys other than a reference to FND_SECURITY_GROUPS via SECURITY_GROUP_ID. This suggests treating the table as a satellite-like structure keyed on the AME transaction, rather than as a hub or link. The classification is a modeling suggestion only; in EBS the table is transactional in nature and is tightly coupled to AME's runtime processing.

Key Information Stored

The table contains 20 documented columns in the ETRM 12.2.2 schema definition. The most significant are listed below.

  • TRANSACTION_ID — identifier of the AME transaction to which the insertion belongs; the principal business-key candidate for grouping rows.
  • APPLICATION_ID — the EBS application (for example, PO, AP, or HR) that owns the transaction.
  • INSERTION_ORDER — the sequence in which the approver or insertion is positioned in the generated approver list.
  • ORDER_TYPE — classification of the ordering rule applied (for example, by authority or by hierarchy).
  • PARAMETER — the parameter value used to resolve the insertion.
  • DESCRIPTION — free-text description of the insertion or rule outcome.
  • USER_ID — the application user associated with the insertion.
  • PERSON_ID — the HR person identifier of the approver or forwardee.
  • API_INSERTION — flag or code indicating an insertion made through an AME API call.
  • AUTHORITY — the approval authority value used to qualify the approver.
  • APPROVAL_STATUS — current status of the insertion within the approval process.
  • SECURITY_GROUP_ID — the security group under which the row is visible; the single documented foreign key to FND_SECURITY_GROUPS.
  • NAME — the approver or insertion name.
  • APPROVER_CATEGORY — category of the approver (for example, job level or supervisory level).
  • ITEM_CLASS / ITEM_ID — the items to which the insertion applies.
  • SPECIAL_FORWARDEE — flag for special forwarding handling.

A separate surrogate primary key is not enumerated in the documented metadata; the effective transactional identity is the combination of TRANSACTION_ID with the insertion ordering and approver attributes.

Common Use Cases and Queries

Typical uses include auditing which approvers AME inserted for a given transaction, diagnosing unexpected approval routings, and reporting on approval authority distributions.

  • List all insertions for a transaction: SELECT insertion_order, name, person_id, authority, approval_status FROM ame_temp_insertions WHERE transaction_id = :p_txn ORDER BY insertion_order;
  • Identify insertions by approver: SELECT transaction_id, application_id, approval_status FROM ame_temp_insertions WHERE person_id = :p_person;
  • Filter by security group: SELECT * FROM ame_temp_insertions WHERE security_group_id = :p_grp;
  • Reporting on approval status distribution across applications and item classes.
  • Troubleshooting forwarded approvals using SPECIAL_FORWARDEE and APPROVER_CATEGORY.

Related Objects

  • FND_SECURITY_GROUPS — joined via SECURITY_GROUP_ID; controls row-level visibility.
  • AME_TRANSACTIONS (and AME_TRANSACTION_* variants) — the parent transactional context for TRANSACTION_ID.
  • AME_APPROVERS / AME_APPROVER_GROUPS — approver definitions that feed insertion attributes such as AUTHORITY and APPROVER_CATEGORY.
  • AME_RULES / AME_RULE_DETAILS — rules whose evaluation produces these insertion rows.
  • AME_API_PUB / AME_ENGINE — AME public APIs and engine that populate this table during approval list generation.
  • PER_ALL_PEOPLE_F — joined via PERSON_ID to resolve person and assignment details.
  • FND_USER — joined via USER_ID to resolve the application user.