Search Results test_cls

Overview

APPS.PMITS_QC_TESTS_V is a reporting and integration view in Oracle EBS Process Manufacturing (formerly OPM/Quality). It presents a consolidated, denormalized picture of quality control test definitions together with the value/range rows that qualify each test. The view combines test master attributes (code, description, class, type, unit, precision and control limits) with the value detail rows that define the numeric minimum/maximum, textual range, descriptive value and expression references for a test. In Oracle EBS 12.1.1 and 12.2.2 it is used where a single query is required to retrieve test setup and its associated value validation data — for example in quality result entry, specification maintenance, reporting extracts and integration interfaces. Because the view is defined with outer joins between tests and their values, a test row is returned even when no value rows exist, which makes it safe for left-outer reporting against the test master. The view is owned by APPS and is intended to be queried through the APPS schema rather than from the underlying GMD tables directly.

Underlying Base Objects

The view is defined over three documented objects:

• GMD_QC_TESTS_VL (VIEW) — the alias QC_TESTS in the view text; supplies the test master/header columns and joins on TEST_ID to the value rows.
• GMD_QC_TEST_VALUES_VL (VIEW) — the alias TEST_VALS; supplies the qualifying value/range rows and joins to tests on TEST_ID. The join is outer (TEST_ID(+) on the TEST_VALS side), so tests without values are retained.
• GMD_TEST_CLASSES_VL (VIEW) — the alias TEST_CLS; supplies the class description and is joined on TEST_CLASS with an outer join, so tests with no matching class are still returned.

Since each referenced base object is itself a view (typically the VL “view-language” variant over the underlying GMD base tables), PMITS_QC_TESTS_V is effectively a two-level abstraction useful for read-only reporting, avoiding direct dependence on the physical tables.

Key Columns

• TEST_ID, TEST_CODE, TEST_DESC — identifier, short code and description of the test.
• TEST_CLASS, TEST_CLASS_DESC — classification code and its description from GMD_TEST_CLASSES_VL.
• TEST_TYPE, TEST_UNIT, TEST_METHOD_ID, TEST_PROVIDER_CODE — type, unit of measure, method and provider of the test.
• MIN_VALUE_NUM, MAX_VALUE_NUM, MIN_NUM, MAX_NUM — numeric limits at test and value level.
• BELOW_SPEC_MIN, ABOVE_SPEC_MIN, BELOW_SPEC_MAX, ABOVE_SPEC_MAX — specification limit indicators for the accepted range.
• BELOW_MIN_ACTION_CODE, ABOVE_MIN_ACTION_CODE, BELOW_MAX_ACTION_CODE, ABOVE_MAX_ACTION_CODE — action codes triggered when results fall outside the defined limits.
• EXPRESSION, EXPRESSION_REF_TEST_ID — calculated-test expression and reference to a related test used in the expression.
• DISPLAY_PRECISION, REPORT_PRECISION, PRIORITY, EXP_ERROR_TYPE — presentation and evaluation attributes.
• TEST_VALUE_DESC, VALUE_CHAR, DISPLAY_LABEL_NUMERIC_RANGE, TEXT_RANGE_SEQ — value-level descriptive and textual range data from GMD_QC_TEST_VALUES_VL.
• TEST_OPRN_ID, TEST_OPRN_LINE_ID — linkage to the operation and operation line where the test applies.

Common Use Cases and Queries

Typical uses include retrieving all tests and their value rows for a specification, listing numeric tests with defined limits, or extracting class-level test inventories for reporting. Because TEST_VALS and TEST_CLS are outer-joined, filtering on class description coalesces a test to NULL when no class exists; when filtering on value columns, the outer join inherently restricts output to tests that actually have values. A representative query returning tests and their numeric value rows is:

SELECT test_code, test_desc, test_class_desc, test_unit, min_num, max_num, test_value_desc FROM apps.pmits_qc_tests_v WHERE test_type = 'NUMERIC' ORDER BY test_code;

To list tests with their associated value rows filtered by a specific test code: SELECT test_id, test_code, test_value_desc, value_char, display_label_numeric_range FROM apps.pmits_qc_tests_v WHERE test_code = :p_test_code. For a specification-maintenance report, join to the specification tables on TEST_ID. When querying, note that duplicate TEST_ID rows may appear when a test has multiple value rows; use DISTINCT or aggregate when only one row per test is required.