Search Results ame_string_values




Overview
Explore in AI Chat

Overview

AME_STRING_VALUES is a reference table in the Oracle E-Business Suite HR (PER) schema that supports the Oracle Approvals Management Engine (AME). The table stores the discrete string literals that satisfy a defined AME condition, allowing the approvals engine to determine whether a given condition evaluates to true for a transaction. In the AME rule model, a condition typically consists of an attribute tested against one or more allowed values; AME_STRING_VALUES holds those allowed string values alongside their effective-date range.

Although the object is owned by the HR schema and registered under the PER product, its functional purpose is tightly bound to AME transaction-type rule configuration rather than to core HR records. From a Data Vault modeling perspective, the ETRM heuristic classifies AME_STRING_VALUES as standalone. This suggests that, in a warehoused model, the table is best represented as an independent reference or lookup set rather than as a hub or link. In practice it functions as a value-set satellite attached to AME condition definitions: it carries no inbound foreign-key dependencies beyond its own security group and is primarily read to resolve condition values during approvals processing.

Key Information Stored

The documented 12.2.2 physical schema for HR.AME_STRING_VALUES contains 12 columns. The most significant are:

The unique index AME_STRING_VALUES_UK1 spans CONDITION_ID, STRING_VALUE, START_DATE, END_DATE, and ZD_EDITION_NAME. This composite business key enforces that a given condition cannot hold duplicate string values within the same effective-date range, while permitting multiple string values per condition and date-versioned reuse of the same value.

Common Use Cases and Queries

Typical uses include auditing AME condition configuration, troubleshooting why an approval rule did or did not fire, and migrating AME setup between environments. A representative query joins the value table to its security group and filters on effective dates:

SELECT s.CONDITION_ID,
       s.STRING_VALUE,
       s.START_DATE,
       s.END_DATE,
       g.SECURITY_GROUP_KEY
  FROM hr.ame_string_values s,
       fnd_security_groups g
 WHERE s.security_group_id = g.security_group_id
   AND SYSDATE BETWEEN s.start_date AND NVL(s.end_date, SYSDATE);

A second pattern enumerates all values for a specific condition to verify that the intended literals are present and active. Reporting use cases include comparing condition-value sets across instances for release validation, and extracting configuration to document approval matrices for audit or governance purposes. Because the table is effective-dated, historical queries should constrain START_DATE and END_DATE rather than assuming a single current row per value.

Related Objects

  • FND_SECURITY_GROUPS — Referenced by SECURITY_GROUP_ID; the only documented foreign key target.
  • AME_CONDITIONS — Parent definition of the condition identified by CONDITION_ID; the principal functional join.
  • AME_CONDITION_ATTRIBUTES — Defines the attribute that the stored STRING_VALUE is compared against.
  • AME_RULES and AME_RULE_DETAILS — Consume conditions (and therefore their string values) when evaluating approvals.
  • AME_TRANSACTION_TYPES — Scopes the conditions for which these string values are configured.
  • AME_UTIL and the AME engine APIs (for example, AME_API) — Runtime consumers that resolve conditions against transaction data.

Because the object is classified as standalone, it has no dependent child tables; maintenance is performed through AME configuration forms and the AME setup APIs rather than through direct DML.