Search Results ame_string_values_fk1

Overview

HR.AME_STRING_VALUES is a transactional configuration table within the Oracle E-Business Suite Approval Management Engine (AME), owned by the HR schema and registered under the application design data reference PER.AME_STRING_VALUES. AME is the rules framework that drives approval routing for requisitions, purchase orders, expenses, and other EBS transactions. Condition rules in AME are expressed against attributes, and when an attribute is of string type, the permissible comparison values are persisted in this table. In effect, HR.AME_STRING_VALUES stores the allowed string values of conditions based on string-type attributes, providing the value list that the AME rule engine consumes when evaluating a condition at runtime.

The table resides in the APPS_TS_TX_DATA tablespace with a PCT Free of 10, which is consistent with a low-to-moderate write volume configuration table that is queried frequently by the AME evaluation routines. From a Data Vault modeling perspective, this object is best characterized as a standalone structure; the mined dependency metadata identifies no outbound foreign keys beyond a legacy reference to FND_SECURITY_GROUPS, and no parent hub or link is implied. It can therefore be modeled as a standalone reference or satellite-style entity anchored on the condition identifier rather than as a hub or link.

Key Information Stored

The table contains twelve documented columns. The most significant are:

• CONDITION_ID (NUMBER) — Condition identifier. This is the principal join key back to the AME condition definition and drives both unique and non-unique index access paths.
• STRING_VALUE (VARCHAR2(4000)) — The permitted string value for the condition. This is the business payload of the row and the value evaluated against the transaction attribute.
• START_DATE (DATE) — The date on which the row becomes active.
• END_DATE (DATE) — The date on which the row is inactivated. Together with START_DATE these columns implement effective-dating of the allowed value list.
• ZD_EDITION_NAME (VARCHAR2(30)) — Editioning column supporting online patching in EBS 12.2.x.
• OBJECT_VERSION_NUMBER (NUMBER) — System-generated row version that increments by one on each update, used for optimistic locking.
• SECURITY_GROUP_ID (NUMBER(15)) — Documented as not used; retained for historical Multi-Org compatibility.
• CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN — Standard Who audit columns tracking row provenance and last modification.

The unique index AME_STRING_VALUES_UK1 spans CONDITION_ID, STRING_VALUE, START_DATE, END_DATE, and ZD_EDITION_NAME, making that composite the effective business key: no two rows may carry the same allowed value for the same condition over the same effective interval within an edition. The non-unique index AME_STRING_VALUES_FK1 on CONDITION_ID, START_DATE, END_DATE supports date-filtered lookups by condition. A synonym, AME_STRING_VALUES#, is maintained for the table.

Common Use Cases and Queries

Typical usage centers on verifying which string values a given AME condition will accept, and on diagnosing routing failures where a transaction attribute does not match any configured value. A common pattern filters by condition and effective date:

SELECT condition_id, string_value FROM hr.ame_string_values WHERE condition_id = :p_condition_id AND SYSDATE BETWEEN start_date AND NVL(end_date, SYSDATE + 1);

Reporting queries join CONDITION_ID to the AME condition and rule definitions to produce a listing of approval rules and their permitted values, which is useful during implementation reviews and post-upgrade validation. Because the unique key includes the edition name, queries executed during an online patching cycle should be aware of ZD_EDITION_NAME to avoid returning rows from more than one edition.

Related Objects

• HR.AME_CONDITIONS — the parent condition definition referenced through CONDITION_ID; the primary join for resolving rule context.
• HR.AME_RULES — the rule that owns the condition and, indirectly, the allowed string values.
• HR.AME_ATTRIBUTES — defines the string-type attribute whose values are constrained by this table.
• HR.AME_STRING_VALUES# — the editioning view/synonym counterpart of this table.
• FND_SECURITY_GROUPS — legacy reference via SECURITY_GROUP_ID, documented as not used.
• HR.AME_CONDITION_GROUPS and related AME condition structures — consumed alongside this table during rule evaluation.

Because AME metadata is heavily cached in the application tier, changes to HR.AME_STRING_VALUES generally require a cache refresh or concurrent program restart before the approval engine reflects new allowed values.