Results for “ame_attribute_usages”
50+ results
AI-generated from documented ETRM metadata — verify critical details on the linked pages.
Overview
AME_ATTRIBUTE_USAGES is an Oracle E-Business Suite table owned by the HR schema and associated with the PER (Human Resources) product family. It forms part of the Oracle Approvals Management Engine (AME) data model, the rules framework that drives approval routing, approver list generation, and workflow decisions across EBS applications such as Purchasing, Payables, iExpenses, and HR. The table records the usage definitions attached to AME attributes — the discrete data points (for example, requisition amount, cost center, or job level) that AME evaluates when constructing an approval chain.
Because AME attributes can be reused across many transaction types and business contexts, AME_ATTRIBUTE_USAGES acts as the associative layer that binds an attribute to a governance scope. In Data Vault modeling terms, the mined metadata classifies this object as standalone, suggesting it functions as a link-style or reference table connecting attribute definitions to their usage configuration rather than as a pure transactional fact. This classification is heuristic and should be validated against the surrounding AME entity relationships before being treated as definitive.
Key Information Stored
The documented physical schema for release 12.2.2 contains 17 columns. The most significant are:
- ATTRIBUTE_ID — identifies the AME attribute whose usage is being defined; a core business-key component.
- APPLICATION_ID — the owning EBS application, scoping the attribute usage to a specific product.
- START_DATE / END_DATE — the effective-dating pair that governs when a usage definition is valid. Together with ATTRIBUTE_ID and APPLICATION_ID these form the unique business key.
- QUERY_STRING — the SQL or query expression used to derive the attribute value at runtime.
- USE_COUNT — a counter tracking how frequently the usage definition has been referenced.
- USER_EDITABLE — flag indicating whether end users may modify the attribute value.
- IS_STATIC — indicates whether the attribute value is fixed rather than dynamically queried.
- SECURITY_GROUP_ID — foreign key to FND_SECURITY_GROUPS, controlling multi-tenant or organizational visibility.
- VALUE_SET_ID — foreign key to FRM_PART_VALUE_SETS, binding the usage to a permissible value set.
- OBJECT_VERSION_NUMBER — optimistic locking column used by the ORM framework to prevent concurrent update conflicts.
- ZD_EDITION_NAME — editioning column supporting Oracle EBS online patching in 12.2.x.
- Audit columns — CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN capture standard WHO information for every row.
The unique index AME_ATTRIBUTE_USAGES_UK1 (ATTRIBUTE_ID, APPLICATION_ID, START_DATE, END_DATE, ZD_EDITION_NAME) is the documented business-key candidate and reinforces the effective-dated, edition-aware nature of the design.
Common Use Cases and Queries
Developers and administrators query this table to inspect how an AME attribute is configured, to verify effective-dating windows, and to debug approval routing that produces unexpected results.
- Listing current usages for an attribute:
SELECT attribute_id, application_id, start_date, end_date,
query_string, user_editable, is_static
FROM ame_attribute_usages
WHERE attribute_id = :attribute_id
AND TRUNC(SYSDATE) BETWEEN start_date AND NVL(end_date, TRUNC(SYSDATE));
- Joining to the security group to determine organizational visibility.
- Confirming that a value set binding exists via VALUE_SET_ID.
- Auditing recent configuration changes using LAST_UPDATED_BY and LAST_UPDATE_DATE.
Related Objects
The following objects are most significant to this table based on documented foreign keys and the AME data model:
- FND_SECURITY_GROUPS — referenced through SECURITY_GROUP_ID.
- FRM_PART_VALUE_SETS — referenced through VALUE_SET_ID.
- AME_ATTRIBUTES — parent attribute definition joined on ATTRIBUTE_ID.
- FND_APPLICATION — joined on APPLICATION_ID to resolve the owning product.
- AME_ATTRIBUTE_TRANS_USAGES — companion usage table at the transaction-type level.
- AME_CONDITIONS / AME_RULES — consume attribute values during rule evaluation.
- AME_API1 / AME_API2 — public APIs that surface attribute usage at runtime.
-
To be Updated
-
To be Updated