Results for “variable_value”

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

Overview

AME_CONFIG_VARS is a configuration table residing in the HR schema and delivered under the PER (Human Resources) product family in Oracle E-Business Suite 12.1.1 and 12.2.2. It stores the runtime configuration parameters used by the Oracle Approvals Management (AME) engine, the rules-based framework that evaluates approval hierarchies, routing, and authorization limits for transactions originating in modules such as Purchasing, Payables, Order Management, and Human Resources. The table effectively acts as the persistent home for AME setup variables — application-scoped values that AME rule definitions and conditions reference during transaction approval processing. Its presence in the HR schema reflects AME's architectural dependency on HR security and date-effective configuration structures.

From a data-modeling perspective, the heuristic Data Vault classification derived from the foreign-key structure is standalone. This suggests the table should be treated as an independent reference or configuration entity rather than as a hub, link, or satellite in a conventional Data Vault build. It carries its own business key and versioning semantics without participating in the hub-and-link topology that characterizes transactional EBS tables.

Key Information Stored

The table contains 14 documented columns. The most significant for functional and integration purposes are:

• APPLICATION_ID — identifies the EBS application context to which a configuration variable applies, typically populated from FND_APPLICATION.
• VARIABLE_NAME and VARIABLE_VALUE — the core name/value pair representing the AME configuration parameter being set.
• DESCRIPTION — human-readable explanation of the variable's purpose.
• START_DATE and END_DATE — the date-effective window during which a given variable value is active, enabling configuration changes over time without overwriting history.
• SECURITY_GROUP_ID — foreign key to FND_SECURITY_GROUPS, enforcing Multi-Org/security-group access isolation.
• OBJECT_VERSION_NUMBER — optimistic locking column used by the Oracle Application Framework (OAF) and concurrent update protection.
• ZD_EDITION_NAME — the editioning column that supports Oracle EBS 12.2 Online Patching (adop) edition-based redefinition.
• CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN — standard EBS audit who/when columns.
• LAST_UPDATE_LOGIN — captures the login session that performed the most recent change, useful for forensic and SOX audit trails.

The documented business-key candidate is the unique index AME_CONFIG_VARS_UK1, defined over (START_DATE, END_DATE, VARIABLE_NAME, APPLICATION_ID, ZD_EDITION_NAME). This means a given variable name may appear multiple times with different effective date ranges, and each edition of the data carries its own uniqueness scope.

Common Use Cases and Queries

Typical uses include auditing current AME configuration, comparing variable values between environments, and troubleshooting approval routing that behaves unexpectedly due to a stale or misconfigured variable.

Query the effective configuration for a given application as of today:

• SELECT variable_name, variable_value, description, start_date, end_date FROM ame_config_vars WHERE application_id = :app_id AND TRUNC(SYSDATE) BETWEEN start_date AND NVL(end_date, TRUNC(SYSDATE)+1);

Detect overlapping or conflicting date ranges for the same variable, which often explains inconsistent approval behavior:

• SELECT variable_name, COUNT(*) FROM ame_config_vars WHERE application_id = :app_id GROUP BY variable_name HAVING COUNT(*) > 1;

Trace historical changes for change-management evidence:

• SELECT variable_name, variable_value, last_updated_by, last_update_date FROM ame_config_vars WHERE variable_name = :name ORDER BY start_date;

Reporting use cases frequently join to FND_APPLICATION to resolve the application short name, and to FND_USER on last_updated_by to attribute changes to named administrators. Because AME configuration is date-effective, any BI extract must filter on the effective window rather than pulling the raw table.

Related Objects

• FND_SECURITY_GROUPS — joined on SECURITY_GROUP_ID; enforces data security group isolation for the configuration row.
• FND_APPLICATION — joined on APPLICATION_ID; resolves the application short name and description.
• FND_USER — joined on LAST_UPDATED_BY and CREATED_BY for audit attribution.
• AME_RULES / AME_RULE_USAGES — the AME rule definition tables whose conditions frequently reference variables held in AME_CONFIG_VARS.
• AME_ATTRIBUTES / AME_CONDITIONS — AME metadata that consumes configuration values during rule evaluation.
• AME_ACTIONS / AME_ACTION_USAGES — action definitions that can be parameterized by configuration variables.
• FND_LOOKUPS — often supplies the allowable values for specific configuration variable names.
• AME_API / AME_ENGINE PL/SQL packages — runtime consumers that read AME_CONFIG_VARS during approval processing.