Results for “parameter_description”

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

Overview

GME_PROCESS_PARAMETERS_V is a supplementary database view owned by the APPS schema within the GME — Process Manufacturing Process Execution product family. It is defined over the transactional parameter records captured during process manufacturing batch execution and enriches those records with descriptive metadata drawn from the process parameter definition layer. The view exposes a consolidated, read-only projection of process parameter data, enabling reporting, integration, and inquiry without requiring consumers to join the underlying transactional and definition tables manually.

Because it is a simple join view rather than a materialized structure, it reflects the current committed state of its base objects at query time. This makes it well suited to ad hoc reporting, concurrent program data sources, and inbound/outbound integration extracts in Oracle EBS 12.1.1 and 12.2.2. The view is documented as VALID in the ETRM metadata, indicating that all referenced objects resolved correctly at the time of documentation.

Underlying Base Objects

The documented definition joins two referenced objects: the base transactional table GME_PROCESS_PARAMETERS (aliased GPP, accessed through a SYNONYM) and the definition view GMP_PROCESS_PARAMETERS_VL (aliased PP). The join is performed on PARAMETER_ID, linking each captured parameter instance on a batch to its corresponding process parameter definition. Parameter name and description are sourced from the VL (view-language) object, ensuring that translated/display descriptors are surfaced alongside the transactional values. All columns in the select list originate from these two objects; the view performs no aggregation or grouping, so cardinality matches the underlying parameter rows.

Key Columns

• PROCESS_PARAM_ID — Primary identifier for the captured process parameter record.
• BATCH_ID — The batch to which the parameter reading belongs.
• BATCHSTEP_ID — The batch step context for the parameter.
• BATCHSTEP_ACTIVITY_ID — The step activity under which the parameter is recorded.
• BATCHSTEP_RESOURCE_ID and RESOURCES — The resource context associated with the reading.
• PARAMETER_ID — Foreign key to the process parameter definition; the join key to GMP_PROCESS_PARAMETERS_VL.
• PARAMETER_NAME — Descriptive name of the parameter from the definition.
• PARAMETER_DESCRIPTION — Descriptive text of the parameter from the definition.
• TARGET_VALUE, MINIMUM_VALUE, MAXIMUM_VALUE — The specification limits for the parameter.
• ACTUAL_VALUE — The observed value captured during execution.
• PARAMETER_UOM — The unit of measure for the parameter values. Matching the user's search term, this column supplies the UOM context required to interpret TARGET_VALUE, MINIMUM_VALUE, MAXIMUM_VALUE, and ACTUAL_VALUE.

Common Use Cases and Queries

Typical scenarios include batch release reporting, out-of-specification analysis (comparing ACTUAL_VALUE against MINIMUM_VALUE and MAXIMUM_VALUE), and UOM-aware reporting that relies on PARAMETER_UOM to normalize or display measurements. The following sample retrieves all parameters for a batch:

SELECT process_param_id, batch_id, batchstep_id, parameter_name, target_value, actual_value, parameter_uom FROM apps.gme_process_parameters_v WHERE batch_id = :batch_id;

An out-of-specification query might filter where ACTUAL_VALUE falls outside the specification band. Because the view joins transactional and definition data, it simplifies such comparisons and supports integration extracts that require both the parameter measurement and its descriptive and UOM context in a single result set.