Results for “attribute_value_2”

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

Overview

The AME_TEST_TRANS_ATT_VALUES table is a repository object within the Oracle E-Business Suite Approvals Management Engine (AME) subsystem, owned by the HR schema and classified under the PER – Human Resources product family. It stores attribute values captured during test executions of AME transaction simulations. When an administrator or implementer configures approval rules and then runs the AME Test Workbench to verify how a transaction (for example, a requisition, purchase order, or expense report) would be routed, the engine generates a test transaction against a selected transaction type. The attribute values evaluated for that transaction are persisted in this table.

The table stores the resolved values of each approval attribute that AME examined during the test run. This allows the test workbench to display, after the fact, exactly which attribute values drove the approval determination and which rules were satisfied or bypassed. The presence of ITEM_ID and ITEM_CLASS_ID suggests support for line-level attributes in addition to header-level attributes.

From a dimensional modeling perspective, the mined foreign-key structure classifies this object heuristically as a standalone table; the Data Vault classification suggests treating it as a satellite-like structure attached to the AME test transaction hub, though no enforced parent relationship beyond the security group reference is documented.

Key Information Stored

The table contains 14 documented columns. The most significant include:

• TRANSACTION_ID – Identifies the AME test transaction to which the attribute value belongs; the principal business-key candidate linking back to the test run.
• ATTRIBUTE_ID / ATTRIBUTE_NAME – The identifier and descriptive name of the approval attribute being evaluated (for example, transaction amount or cost center).
• ATTRIBUTE_TYPE – Indicates the data type or category of the attribute, guiding interpretation of the stored value.
• IS_MANDATORY – Flags whether the attribute was required for rule evaluation.
• LINE_ITEM_ID – Identifies the transaction line when the attribute is line-level rather than header-level.
• ATTRIBUTE_VALUE_1, ATTRIBUTE_VALUE_2, ATTRIBUTE_VALUE_3 – The resolved values of the attribute, spanning up to three value slots to accommodate varying attribute representations.
• APPLICATION_ID – The application owning the transaction context.
• ITEM_ID / ITEM_CLASS_ID – Reference the specific item and item class where line-level attributes apply.
• SECURITY_GROUP_ID – The security group context, with a documented foreign key to FND_SECURITY_GROUPS.
• ROW_TIMESTAMP – Audit/versioning column supporting change tracking.

Common Use Cases and Queries

The primary use case is diagnosing why a particular approval routing occurred during AME testing. Implementers query the table after running the test workbench to inspect the values AME actually evaluated. A representative query pattern joins the attribute values to the test transaction:

• Retrieve all attribute values for a given test transaction: SELECT attribute_name, attribute_value_1, attribute_value_2, attribute_value_3 FROM ame_test_trans_att_values WHERE transaction_id = :transaction_id;
• Filter for mandatory attributes only: add AND is_mandatory = 'Y' to isolate required attributes.
• Identify line-level evaluations by filtering on line_item_id IS NOT NULL.

Reporting scenarios include validating approval rule configuration before production deployment and troubleshooting unexpected routing results. Data should be treated as transient test data and purged periodically.

Related Objects

• FND_SECURITY_GROUPS – Referenced through SECURITY_GROUP_ID; the only documented foreign key relationship.
• AME_TEST_TRANSACTIONS – The parent test transaction record joined on TRANSACTION_ID.
• AME_ATTRIBUTES / AME_ATTRIBUTE_USAGES – Define the attribute metadata referenced by ATTRIBUTE_ID.
• AME_TRANSACTIONS / AME_TRANSACTION_TYPES – Describe the production transaction types simulated by the test runs.
• AME_RULES / AME_RULE_USAGES – Consume the attribute values to determine rule evaluation outcomes.
• AME_TEST_WORKBENCH – The AME user interface that generates and reads these records.