Results for “gmp_parameter_values_vl”

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

Overview

The GMP_PARAMETER_VALUES_VL view is a public, language-translated (VL) database object owned by the APPS schema in Oracle E-Business Suite. It belongs to the GMP product family, specifically Process Manufacturing Process Planning (Oracle Process Manufacturing). The view presents parameter value definitions along with their user-facing, language-specific descriptions, providing a consolidated read interface for reporting, integrations, and concurrent programs that need to resolve parameter values without joining the underlying base and translation tables manually.

As a "_VL" view, it follows the standard Oracle EBS multilingual pattern: rows are restricted to the session's language using USERENV('LANG'), so a query returns the description appropriate to the logged-in user's locale rather than every available translation. The view is documented as VALID in both Oracle EBS 12.1.1 and 12.2.2, and its definition is stable across those releases. It is intended primarily for read access; DML against a translated view of this kind is not supported, and inserts or updates must target the base tables.

Underlying Base Objects

The ETRM metadata documents the view as being defined over two synonyms, which resolve to tables in the APPS schema:

• GMP_PARAMETER_VALUES_B — the base ("B") table holding language-independent data, including the primary key and audit columns.
• GMP_PARAMETER_VALUES_TL — the translation ("TL") table holding the language-specific description, keyed by LANGUAGE.

The view joins these two objects on both PARAMETER_ID and PARAMETER_VALUE, and filters the translation side by T.LANGUAGE = USERENV('LANG'). Because the join requires a matching translation row in the session's language, a value that has no entry in the installed language will not appear when queried through the view. The view also exposes the base table's ROWID as ROW_ID, which is useful for identifying base rows in update logic against GMP_PARAMETER_VALUES_B.

Key Columns

• ROW_ID — the ROWID of the corresponding row in GMP_PARAMETER_VALUES_B; a non-persistent identifier exposed for base-table operations.
• PARAMETER_ID — identifier of the parent parameter to which the value belongs; one component of the composite join to the translation table.
• PARAMETER_VALUE — the stored code value for the parameter; the second component of the join and the value typically referenced by dependent setup data.
• PARAMETER_VALUE_DESCRIPTION — the language-specific, user-facing description sourced from GMP_PARAMETER_VALUES_TL; the primary reason for using the VL view.
• CREATION_DATE, CREATED_BY — standard audit columns recording when and by whom the value was created.
• LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN — standard audit columns recording the most recent modification and the login of the updating session.

Common Use Cases and Queries

Typical uses include parameter value list-of-values reporting, validation of planning parameter setup, and extract programs that supply parameter values and their descriptions to downstream systems. The view is also convenient for ad-hoc SQL where a readable description is needed without an explicit join to the translation table.

Query all values for a given parameter:

SELECT parameter_value,
       parameter_value_description
FROM   apps.gmp_parameter_values_vl
WHERE  parameter_id = :p_parameter_id
ORDER  BY parameter_value;

Locate values updated within a date range for audit reporting:

SELECT parameter_id,
       parameter_value,
       parameter_value_description,
       last_update_date,
       last_updated_by
FROM   apps.gmp_parameter_values_vl
WHERE  last_update_date >= :p_from_date
ORDER  BY last_update_date DESC;

If an expected value is missing from the results, the absence of a translation row in the current session language is the most common cause; querying GMP_PARAMETER_VALUES_B directly, or switching the session language, will confirm this. For performance, filter on PARAMETER_ID so that the join between the base and translation tables is driven by an indexed key.