Search Results gmd_qc_test_type




Overview
Explore in AI Chat

Overview

The view APPS.GMD_QC_E_TEST_INSTANCE_V is a quality control (QC) inquiry view within the Oracle E-Business Suite Process Manufacturing (OPM) module. It is owned by the APPS schema and is catalogued in the E-Business Suite Technical Reference Manual (ETRM) for releases 12.1.1 and 12.2.2. The view presents the effective association between QC test results and the QC test definitions they reference, thereby exposing a consolidated picture of QC test instances along with descriptive attributes and the associated test method code. Because it joins the result records to the test master and to the descriptive test types, it acts as a denormalized reporting layer that shields callers from having to resolve multiple lookup and master relationships themselves.

This view is frequently surfaced in response to users searching the term gmd_qc_tests, since the underlying synonym GMD_QC_TESTS is one of the four base objects referenced by the view. Its intended use is read-only inquiry in reporting and integration scenarios, not transactional processing.

Underlying Base Objects

The documented base objects referenced by this view are:

  • GMD_RESULTS (SYNONYM) — the source of test result rows, referenced by alias RSLT. It supplies test_id, update_instance_id, and test_method_id.
  • GMD_QC_TESTS (SYNONYM) — the QC test master, referenced by alias TEST. It supplies test_code, test_desc, test_class, test_type, and expression.
  • FND_LOOKUP_VALUES_VL (VIEW) — the concurrent program lookup view, referenced by alias TEST_TYPES. It resolves the meaning of test_type through lookup type GMD_QC_TEST_TYPE.
  • GMD_TEST_METHODS_B (SYNONYM) — the test methods base table, referenced by alias TESTMETHODS. It supplies test_method_code.

The joins are strictly inner. RSLT.TEST_ID equals TEST.TEST_ID; TEST.TEST_TYPE equals the decoded lookup code within lookup type GMD_QC_TEST_TYPE; and RSLT.TEST_METHOD_ID equals TESTMETHODS.TEST_METHOD_ID. The result set is de-duplicated via SELECT DISTINCT and ordered by RSLT.TEST_ID. Consequently, a QC test instance appears only where results, a matching test definition, a valid test type lookup, and a valid test method all exist.

Key Columns

  • test_id — the primary key of the QC test instance, driving the ordering and joining.
  • update_instance_id — the update instance identifier associated with the result row, indicating the specific execution or instance-level context in which the test was evaluated.
  • test_code, test_desc — the code and description of the QC test.
  • test_class — classification grouping for the test.
  • test_type — carries the decoded, human-readable meaning of the QC test type from the GMD_QC_TEST_TYPE lookup.
  • expression — the expression or formula associated with the test, typically used in specification/result evaluation.
  • test_method_code — the code of the test method used to perform the test.

Common Use Cases and Queries

Typical use is reporting and integration, such as exporting QC test definitions with their methods and types, or driving an interface that needs a flattened test instance record. A representative query follows.

  • SELECT test_id, test_code, test_desc, test_type, test_method_code FROM apps.gmd_qc_e_test_instance_v WHERE test_code = 'PH999'; — retrieve a specific test instance by code.
  • SELECT test_class, test_type, COUNT(*) FROM apps.gmd_qc_e_test_instance_v GROUP BY test_class, test_type; — summarize instances by class and type.
  • SELECT v.test_id, v.expression, v.test_method_code FROM apps.gmd_qc_e_test_instance_v v WHERE v.update_instance_id = :instance_id; — report methods and expressions for a given update instance.

Because the view is read-only and based on synonyms to the underlying QC tables, its data freshness mirrors the base result and test tables. Access should be granted through the APPS schema or a reporting responsibility, consistent with standard OPM security practice.