Results for “ak_am_parameter_registry”

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

Overview

AK_AM_PARAMETER_REGISTRY is a reference table in the AK (Common Modules – Application Object Library) schema of Oracle E-Business Suite 12.1.1 and 12.2.2. It stores application module parameter names and their corresponding values, functioning as a central registry that maps configurable parameters to the application modules that consume them. The table supports the broader AK runtime framework, which underpins setup-driven behavior across multiple EBS products by allowing parameters to be resolved dynamically rather than hard-coded.

The object is classified as a standalone entity based on its foreign key structure; no outgoing or incoming foreign key dependencies were mined. From a Data Vault modeling perspective, this table is best treated as a hub-like reference (a lookup/dimension candidate) because its primary key is a natural composite business key rather than a generated surrogate. Each row represents one unique parameter definition instance scoped to a module and a parameter source.

Key Information Stored

The table contains five documented columns and is uniquely identified by a composite primary key. The most significant columns are:

• APPLICATIONMODULE_DEFN_NAME – The name of the application module definition that owns or consumes the parameter. This is the highest-level grouping key for parameter configuration.
• PARAM_NAME – The identifier of the parameter being registered. Combined with the module name, it identifies the specific configurable setting.
• PARAM_SOURCE – Indicates where the parameter value originates (for example, the source system, profile option, or lookup that supplies the value). This column is central to the user query "param_source" and is part of the business key.
• APPLICATION_ID – The numeric identifier of the owning application in EBS (referencing FND_APPLICATION), useful for filtering parameters by product.
• ZD_EDITION_NAME – The editioning column introduced in 12.2.x for online patching support; it distinguishes rows by edition in multi-tenant editioning environments.

The surrogate primary key AK_AM_PARAMETER_REGISTRY_PK is defined over (APPLICATIONMODULE_DEFN_NAME, PARAM_NAME, PARAM_SOURCE). A second unique constraint, AK_AM_PARAMETER_REGISTRY_U1, extends the business key with ZD_EDITION_NAME to guarantee uniqueness per edition.

Common Use Cases and Queries

Typical uses include auditing module parameter configuration, tracing the value source for a given parameter, and reporting on parameters by application. Common query patterns follow the documented key columns:

• Retrieve all parameters for a module: SELECT PARAM_NAME, PARAM_SOURCE FROM AK.AK_AM_PARAMETER_REGISTRY WHERE APPLICATIONMODULE_DEFN_NAME = :mod;
• Locate the source of a specific parameter: SELECT PARAM_SOURCE FROM AK.AK_AM_PARAMETER_REGISTRY WHERE APPLICATIONMODULE_DEFN_NAME = :mod AND PARAM_NAME = :param;
• Edition-aware lookup in 12.2.2: SELECT ... WHERE ZD_EDITION_NAME = 'ORA$BASE';
• Filter by product: SELECT ... WHERE APPLICATION_ID = :app;

Reporting use cases include configuration baselines prior to patching, comparing parameter sets across editions, and building migration scripts that reconcile parameter definitions between environments.

Related Objects

Because the FK structure is documented as standalone, the relationships below are logical rather than enforced constraints. Key objects in the AK runtime framework include:

• AK_APPLICATION_MODULE_DEFNS – joins on APPLICATIONMODULE_DEFN_NAME, providing the module definition metadata.
• AK_ATTRIBUTE_DEFNS / AK_REGION_ITEMS – the AK metadata hierarchy that consumes module parameters at runtime.
• FND_APPLICATION – joins on APPLICATION_ID for product and application naming.
• FND_PROFILE_OPTION_VALUES – a potential value source referenced through PARAM_SOURCE profile-based parameters.
• FND_LOOKUP_VALUES – often supplies parameter values where PARAM_SOURCE indicates a lookup.

These objects provide the surrounding context needed to interpret parameter definitions and their resolved values.