Search Results test_cls

Overview

PMITS_QC_TESTS_V is a PL/SQL view owned by the APPS schema and validated in Oracle E-Business Suite releases 12.1.1 and 12.2.2. It belongs to the PMI – Process Manufacturing Intelligence product family, which delivers the analytical and reporting layer for process manufacturing operations. The view provides the definitions of quality control (QC) tests used in process manufacturing, exposing test identity, classification, expected values, numeric bounds, and reporting attributes. Because QC tests drive acceptance decisions for incoming materials, in-process batches, and finished goods, this view is frequently used as the source for quality reporting, dashboards, and integration extracts.

The view is read-only and is not intended as a data entry surface; it serves as a denormalized, report-friendly projection of the underlying QC test definition tables. For a search on test_method_id, the view is the principal published location where that identifier can be retrieved alongside the descriptive attributes of the test itself. This makes it suitable for both ad hoc queries and packaged integration interfaces written directly against the APPS schema.

Underlying Base Objects

The view text is defined over three underlying views, all of which follow the standard Oracle EBS translation-enabled (_VL) pattern:

• GMD_QC_TESTS_VL — the driving object, aliased QC_TESTS, supplying the core QC test definition, including TEST_ID, TEST_CODE, TEST_METHOD_ID, TEST_CLASS, and specification limits.
• GMD_QC_TEST_VALUES_VL — aliased TEST_VALS, supplying value-range and text-range rows associated with each test, such as MIN_NUM, MAX_NUM, VALUE_CHAR, and DISPLAY_LABEL_NUMERIC_RANGE.
• GMD_TEST_CLASSES_VL — aliased TEST_CLS, supplying TEST_CLASS_DESC, the translated description of the test class.

Joins are defined as outer joins from the test definition: QC_TESTS.TEST_ID = TEST_VALS.TEST_ID (+) and QC_TESTS.TEST_CLASS = TEST_CLS.TEST_CLASS (+). Consequently, a test with no value rows or no matching class row still appears in the result set, with nulls in the corresponding columns. Because both child objects are themselves views, the physical base tables reside further down the GMD schema stack, and direct reads against this view incur the cost of resolving that entire chain.

Key Columns

• TEST_ID — primary identifier of the QC test and the anchor of all joins in the view.
• TEST_CODE, TEST_DESC — the short code and translated description of the test.
• TEST_METHOD_ID — identifier of the test method associated with the QC test; this is the column targeted by the user's search.
• TEST_CLASS, TEST_CLASS_DESC — the classification code and its translated description, used to group tests for reporting.
• TEST_PROVIDER_CODE, TEST_TYPE, TEST_UNIT — the provider, category, and unit of measure for the test.
• MIN_VALUE_NUM, MAX_VALUE_NUM, MIN_NUM, MAX_NUM — specification and value-level numeric boundaries.
• EXP_ERROR_TYPE, BELOW_SPEC_MIN, ABOVE_SPEC_MIN, BELOW_SPEC_MAX, ABOVE_SPEC_MAX — expected error handling and out-of-specification flags.
• EXPRESSION, EXPRESSION_REF_TEST_ID — calculated test expression and its referenced test.
• DISPLAY_PRECISION, REPORT_PRECISION, PRIORITY — presentation and ordering attributes.

Common Use Cases and Queries

Typical usage includes quality test master reports, specification range validation, and integration extracts that feed laboratory or LIMS systems. To retrieve the test method for a given test code:

SELECT test_id, test_code, test_desc, test_method_id FROM apps.pmits_qc_tests_v WHERE test_code = :p_test_code;

To list tests grouped by method with their specification limits:

SELECT test_method_id, test_code, test_class_desc, min_value_num, max_value_num FROM apps.pmits_qc_tests_v ORDER BY test_method_id, test_code;

Because the view contains outer-joined value rows, reporting queries should account for potential duplicates of TEST_ID when multiple value rows exist, and should apply the appropriate DISTINCT or GROUP BY clause when a single row per test is required.