Results for “attribute_value_1”

AI-generated from documented ETRM metadata — verify critical details on the linked pages.

Overview

AME_TEMP_TRANS_ATT_VALUES is a table owned by the HR schema within the Oracle E-Business Suite (EBS) environment, sitting under the PER (Human Resources) product/module, though its name and function tie it directly to the Approvals Management Engine (AME) framework used across EBS 12.1.1 and 12.2.2. The table stores the attribute values associated with a temporary or transient AME transaction — that is, the evaluated attribute data captured while AME determines an approval routing plan for a particular business transaction such as a purchase requisition, iPO, expense report, or HR transaction. Each row represents one attribute value belonging to one transaction, and the set of rows for a given TRANSACTION_ID defines the attribute context AME uses when evaluating approval rules.

From a data modeling perspective, the ETRM metadata classifies this object heuristically as a standalone (Data Vault hub, link, or satellite candidate). In practice the table behaves most like a satellite keyed to a transaction identifier, holding descriptive attribute payloads against the AME_TEMP_TRANS_ATT_VALUES.TRANSACTION_ID as a business-key candidate, with SECURITY_GROUP_ID providing the only documented foreign key relationship.

Key Information Stored

The documented physical schema defines 14 columns. The most operationally significant are:

• APPLICATION_ID — identifies the owning EBS application (e.g., PO, iProcurement, AP).
• TRANSACTION_ID — the AME transaction instance to which this attribute value belongs; the primary grouping key.
• ROW_TIMESTAMP — temporal marker for the row, useful for auditing and cache-invalidation logic.
• ATTRIBUTE_ID — surrogate identifier for the attribute definition.
• ATTRIBUTE_NAME — the human-readable attribute label referenced in AME rule conditions.
• ATTRIBUTE_TYPE — the datatype/classification of the attribute (string, number, date, and similar).
• IS_MANDATORY — flag indicating whether the attribute must be supplied for the transaction.
• LINE_ITEM_ID — associates the attribute value with a specific document line where applicable.
• ATTRIBUTE_VALUE_1 / ATTRIBUTE_VALUE_2 / ATTRIBUTE_VALUE_3 — the actual stored value(s) of the attribute; three columns allow for multi-part or multi-valued attributes.
• SECURITY_GROUP_ID — foreign key to FND_SECURITY_GROUPS, controlling row-level access.
• ITEM_ID and ITEM_CLASS_ID — reference identifiers for inventory/transaction items and their classification, enabling item-driven approval logic.

The surrogate primary key is not separately documented beyond the column list; TRANSACTION_ID combined with ATTRIBUTE_ID/LINE_ITEM_ID functions as the effective business key.

Common Use Cases and Queries

Typical uses include troubleshooting why an approval routed a particular way and building diagnostics for AME rule evaluation. A representative query retrieves all attribute values for a transaction:

• SELECT attribute_name, attribute_type, attribute_value_1, attribute_value_2, attribute_value_3 FROM hr.ame_temp_trans_att_values WHERE transaction_id = :tid AND application_id = :app_id;
• Joining to FND_SECURITY_GROUPS on security_group_id to validate access scope.
• Reporting on mandatory attributes (IS_MANDATORY = 'Y') to detect incomplete transaction context.
• Auditing by ROW_TIMESTAMP to see the most recently populated attribute sets.

These patterns are common in approval-route debugging, AME configuration validation, and reconciliation of approval outcomes.

Related Objects

• FND_SECURITY_GROUPS — referenced via SECURITY_GROUP_ID; controls row-level security.
• AME_TEMP_TRANSACTIONS — the parent transaction header that TRANSACTION_ID correlates to.
• AME_TRANSACTION_ATTRIBUTES / AME_CALL_ATTRIBUTES — define the attribute metadata mirrored here at runtime.
• AME_RULES / AME_CONDITIONS — consume these values during rule evaluation.
• AME_APPROVAL_GROUPS / AME_APPROVERS — downstream routing objects resulting from evaluation.

Because the table is transient in nature, its rows are typically short-lived and regenerated each time AME processes a transaction.