Search Results gmp_process_parameters_vl




Overview
Explore in AI Chat

Overview

GMP_PROCESS_PARAMETERS_VL is a bilingual (language-dependent) view owned by the APPS schema in Oracle E-Business Suite. It belongs to the GMP product family, Process Manufacturing Process Planning, and presents the definition of process parameters used within process manufacturing. A process parameter represents a measurable or controllable quality or operating characteristic — for example temperature, pressure, pH, viscosity, or duration — that is associated with process operations and recipes. The view exposes both the descriptive name of the parameter and its translated description, together with the valid range and unit of measure.

The "_VL" suffix denotes a "view language" object, the standard EBS pattern that joins a base (_B) table to its translation (_TL) table and filters the translation by the session language. Because of this design, the view returns exactly one row per parameter per language, delivering the parameter name from the base table and the description from the translation table matching USERENV('LANG'). This makes the view the natural reporting and integration surface for parameter metadata across both 12.1.1 and 12.2.2, insulating callers from the underlying multilingual storage.

Underlying Base Objects

The view is defined over two synonyms, which resolve to the corresponding GMP base tables in the APPS schema:

The join condition is B.PARAMETER_ID = T.PARAMETER_ID AND T.LANGUAGE = USERENV('LANG'). The view text selects the base table's ROWID as ROW_ID and all base columns, taking only the description from the translation table. The DBA metadata lists the view as VALID under the APPS schema.

Key Columns

  • ROW_ID — the base table ROWID, useful for row-level referencing and debugging.
  • PARAMETER_ID — the unique surrogate key for the parameter; the primary join and lookup column.
  • PARAMETER_NAME — the untranslated, language-independent name of the parameter.
  • PARAMETER_DESCRIPTION — the translated description for the session language.
  • PARAMETER_TYPE — the classification or data type of the parameter.
  • MINIMUM_VALUE / MAXIMUM_VALUE — the permissible lower and upper bounds of the parameter.
  • UNITS — the unit of measure in which the parameter values are expressed.
  • DELETE_MARK — soft-delete indicator; records with DELETE_MARK = 1 are logically deleted.
  • TEXT_CODE — the descriptive flexfield context reference.
  • ATTRIBUTE1–ATTRIBUTE30 and ATTRIBUTE_CATEGORY — the descriptive flexfield segments for customer-defined extensions.
  • Standard WHO columns — CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN for audit tracking.

Common Use Cases and Queries

The view is typically used to validate process parameter definitions, drive user-facing parameter lists or LOVs, and supply parameter metadata to reports and integrations. A basic query filtering out logically deleted records follows:

SELECT parameter_id, parameter_name, parameter_description, minimum_value, maximum_value, units FROM apps.gmp_process_parameters_vl WHERE NVL(delete_mark,0) = 0 ORDER BY parameter_name;

To resolve a specific parameter by identifier or validate its range:

SELECT parameter_id, parameter_name, minimum_value, maximum_value, units FROM apps.gmp_process_parameters_vl WHERE parameter_id = :p_parameter_id;

For flexfield-aware queries, the ATTRIBUTE columns can be projected to surface customer-extended data. Because the view resolves the description through USERENV('LANG'), reports rendered in different languages automatically display the appropriately translated description without any changes to calling code.