Search Results value_desc

Overview

GMD_TEST_VALUES_VL is a bilingual (VL suffix) view owned by the APPS schema in Oracle E-Business Suite, delivered as part of the Process Manufacturing Product Development module (GMD). It exposes quality assay test value definitions — the discrete permissible or expected values that can be recorded against a quality assay code — together with their translated descriptions. The view is a presentation-layer construct: it joins the base table holding the enterprise data to its translation table and filters the translation rows by the session language, so that callers see only the description appropriate to their current language environment. This makes the view the standard access point for any form, report, concurrent program, or integration that needs assay values in the user's own language rather than in the language in which they were originally entered.

Underlying Base Objects

The view is defined over two documented base objects:

• GMD_TEST_VALUES_B — the base ("_B") table that stores the actual test value records, including the assay type identifier, organisation code, assay code, the assay value itself, numeric minimum and maximum bounds, and the full set of descriptive flexfield attribute columns.
• GMD_TEST_VALUES_TL — the translation ("_TL") table that stores the language-dependent description (VALUE_DESC) for each test value, keyed by QCASSY_VAL_ID, QCASSY_TYP_ID, and LANGUAGE.

The view text confirms the join is on B.QCASSY_VAL_ID = T.QCASSY_VAL_ID AND B.QCASSY_TYP_ID = T.QCASSY_TYP_ID, with the additional predicate T.LANGUAGE = USERENV('LANG'). The ROW_ID column is sourced from B.ROWID, and the database records the underlying objects as synonyms referenced by the view. Some columns in the select list, such as VALUE_DESC, come from the translation table; the remainder are drawn from the base table.

Key Columns

• ROW_ID — the ROWID of the base-table row; useful for direct row identification and for building updatable-form constructs.
• QCASSY_VAL_ID / QCASSY_TYP_ID — the assay value and assay type identifiers, forming the logical key of the record and the join to the quality assay setup.
• ORGN_CODE, ASSAY_CODE, ASSAY_VALUE — the organisation code, the assay code being defined, and the specific value associated with it.
• VALUE_DESC — the language-specific description of the value, resolved through the translation table.
• VALUE_NUM_MIN / VALUE_NUM_MAX — the numeric lower and upper bounds for the value. VALUE_NUM_MAX, the term users most frequently search for, represents the maximum acceptable numeric limit associated with a test value, used in quality result validation and specification range checks.
• ASSAY_VALUE_RANGE_ORDER — controls the ordering of values when a range of assay values is presented.
• ATTRIBUTE_CATEGORY and ATTRIBUTE1–ATTRIBUTE30 — the descriptive flexfield context and segment columns, allowing customers to extend the test value definition without modifying the base table.
• CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN — standard WHO audit columns.

Common Use Cases and Queries

The view is typically queried when building quality specification reports, populating value-of-list style parameters, or integrating assay value data into external LIMS or manufacturing systems. A representative query retrieving a specific value with its numeric ceiling might be:

• SELECT qcassy_val_id, qcassy_typ_id, assay_code, assay_value, value_desc, value_num_min, value_num_max FROM apps.gmd_test_values_vl WHERE qcassy_typ_id = :p_type AND value_num_max IS NOT NULL ORDER BY assay_value_range_order;
• SELECT assay_code, value_desc, value_num_max FROM apps.gmd_test_values_vl WHERE orgn_code = :p_org ORDER BY assay_code, assay_value_range_order;

Because the language predicate is embedded in the view, callers never need to supply a language filter themselves; the correct translated VALUE_DESC is returned automatically for the running session's language.