Search Results text_range_seq

Overview

GMD_QC_TEST_VALUES_VL is a read-only, language-aware reporting view in the Oracle E-Business Suite Process Manufacturing (OPM) module, owned by the APPS schema. In the context of Oracle EBS 12.1.1 and 12.2.2, it exposes quality control test value definitions—the permissible results, ranges, and coded values that a laboratory technician may select or record when executing a QC test against a specification or sample. The "_VL" suffix is standard EBS naming convention for a "Translation" view: the view joins the base table with its translated (language) table and restricts rows to the session's language using USERENV('LANG'), so that descriptive fields (TEST_VALUE_DESC, DISPLAY_LABEL_NUMERIC_RANGE) are returned in the caller's locale.

Because it presents a denormalized, descriptive-friendly projection of the underlying QC test value tables, the view is primarily consumed for reporting, inquiry-only forms, Discoverer/OBIEE extracts, and integration interfaces that must translate test value codes into user-facing text without implementing their own language join logic.

Underlying Base Objects

Per the documented ETRM metadata for 12.2.2, the view is defined over two base objects (exposed as APPS synonyms): GMD_QC_TEST_VALUES_B, the base table holding language-independent data, and GMD_QC_TEST_VALUES_TL, the translation table holding language-dependent descriptions. The two are joined on TEST_VALUE_ID, and the WHERE clause filters T.LANGUAGE = USERENV('LANG'). In the view text, these are aliased B (base) and T (translation), and B.ROWID is carried through as ROW_ID, consistent with EBS descriptive flexfield and DFF-enabled form handling.

Key Columns

• VALUE_CHAR – the character representation of the test value, the column most directly associated with the search term "value_char." It stores the textual value used when a QC test result is character-based rather than numeric.
• TEST_VALUE_ID – primary key of the test value definition, and the join key between the base and translation tables.
• TEST_ID – the parent QC test to which the value belongs.
• MIN_NUM / MAX_NUM – lower and upper bounds for numeric-range test values.
• DISPLAY_LABEL_NUMERIC_RANGE – translated label describing the numeric range.
• TEST_VALUE_DESC – translated description of the value.
• TEXT_RANGE_SEQ, EXPRESSION_REF_TEST_ID, TEXT_CODE – sequencing, cross-referenced expression/test, and text code driving character-range logic.
• ATTRIBUTE_CATEGORY and ATTRIBUTE1–30 – descriptive flexfield segments for extensibility.
• ROW_ID and the standard WHO columns (CREATION_DATE, CREATED_BY, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN) support auditing and EBS framework operations.

Common Use Cases and Queries

Typical scenarios include listing all valid values for a given QC test, filtering character-based results, and joining to test/specification tables for specification reporting. A sample query:

SELECT test_value_id, test_id, value_char, test_value_desc, min_num, max_num
FROM apps.gmd_qc_test_values_vl
WHERE test_id = :test_id
AND value_char IS NOT NULL
ORDER BY text_range_seq;

The view is also used to resolve a stored QC result back to a displayable description for character tests, or to drive LOVs in custom forms. Note that because the translation join filters on USERENV('LANG'), rows are returned only when a translation exists for the session language; joins should key on TEST_VALUE_ID and match the current language to avoid missing rows.