Results for “param_source”

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

Overview

The AK_AM_PARAMETER_REGISTRY_V view is a reporting and integration layer within the Oracle E-Business Suite Applications Object Library (product group AK – Common Modules-AK). It is owned by the APPS schema and holds a VALID status in both Release 12.1.1 and 12.2.2. The view presents the contents of the underlying configuration table AK_AM_PARAMETER_REGISTRY in a denormalized, user-friendly form by joining it to FND_APPLICATION_VL. Its principal role is to expose the registry of application module parameters—that is, the named parameters that Oracle's Application Object Library uses to drive runtime behavior of application modules—together with their owning application in a readable format. Because it resolves the numeric APPLICATION_ID into the application short name and the translated application name, the view is a convenient source for ad hoc queries, custom reports, and integration logic that must determine which parameters are registered for a given application module. For users who search on application_name, this view is the natural entry point, since it is one of the few registry objects that surfaces the human-readable application name directly rather than requiring an additional lookup.

Underlying Base Objects

The view is defined over two base objects, as documented in the ETRM metadata:

• AK_AM_PARAMETER_REGISTRY (SYNONYM) – the primary table storing each registered parameter, its owning application, its application module definition, and the source of the parameter value.
• FND_APPLICATION_VL (VIEW) – the Applications Object Library's translated view of FND_APPLICATION, supplying APPLICATION_SHORT_NAME and APPLICATION_NAME.

The join condition is FAV.APPLICATION_ID = AKAMPR.APPLICATION_ID, so the view returns one row for every row in the parameter registry that has a matching application. The view text also selects AKAMPR.ROWID as ROW_ID, which means the view is key-preserving with respect to the registry table and can, in principle, be used for updates against it. Because FND_APPLICATION_VL returns the application name in the session's language, the APPLICATION_NAME column is language-sensitive.

Key Columns

• ROW_ID – the ROWID of the underlying AK_AM_PARAMETER_REGISTRY row; identifies the physical registry record.
• APPLICATION_ID – the numeric identifier of the owning application.
• APPL_SHORT_NAME – the application short name (UNIX-style short name), used widely in profile options and APIs.
• APPLICATION_NAME – the translated, user-facing application name; the column most relevant to searches on "application_name".
• APPLICATIONMODULE_DEFN_NAME – the definition name of the application module that owns the parameter.
• PARAM_NAME – the name of the registered parameter.
• PARAM_SOURCE – the source from which the parameter value is derived.

Common Use Cases and Queries

Typical uses include verifying which parameters are registered for a module, confirming the application that owns a parameter, and building custom reports that list parameters alongside friendly application names. A representative query is:

SELECT application_name, appl_short_name, applicationmodule_defn_name, param_name, param_source FROM apps.ak_am_parameter_registry_v WHERE application_name = :p_application ORDER BY applicationmodule_defn_name, param_name;

To locate a specific parameter across all applications:

SELECT application_name, applicationmodule_defn_name, param_name FROM apps.ak_am_parameter_registry_v WHERE param_name = :p_param;

Because APPL_NAME resolution relies on FND_APPLICATION_VL, always query the APPS synonym and ensure the MO or language context is set so the translated name is returned correctly.