Results for “test_type”

50+ results




Overview
Explore in AI Chat

AI-generated from documented ETRM metadata — verify critical details on the linked pages.

Overview

The GMD_QC_E_TEST_INSTANCE_V view is a public Oracle E-Business Suite database object owned by the APPS schema and registered as VALID in the ETRM 12.2.2 inventory. It belongs to the GMD product family — Process Manufacturing Product Development — which encompasses Oracle Quality, quality test definitions, results capture, and specification management for process manufacturing organizations.

The view presents a denormalized, reporting-friendly projection of quality test results. Rather than requiring report authors and integrators to join the raw results table to the test definition table, the lookup-driven test type view, and the test methods table independently, GMD_QC_E_TEST_INSTANCE_V exposes the resolved result row alongside the human-readable test code, description, class, lookup meaning, and method code. It is intended for read-only consumption — typically by Oracle Discoverer worksheets, Oracle Reports, BI Publisher data templates, OBIEE repositories, or custom PL/SQL and interface programs that need to surface quality test instance data without re-implementing the canonical join logic.

The name itself reflects its purpose: it identifies a specific test instance tied to an UPDATE_INSTANCE_ID, which is the key by which results captured against a particular quality instance (such as a batch, lot, or sample) are correlated.

Underlying Base Objects

The view is defined over four documented base objects:

Joins are performed on RSLT.TEST_ID = TEST.TEST_ID and RSLT.TEST_METHOD_ID = TESTMETHODS.TEST_METHOD_ID. The view text uses SELECT DISTINCT, indicating that the results table may contain multiple rows per test/method combination and that deduplication is intentional.

Key Columns

  • TEST_ID — Primary identifier of the quality test definition underlying the result row; also the view's ORDER BY key.
  • UPDATE_INSTANCE_ID — Identifier of the quality instance (for example, a specific lot, batch, or sample) against which the result was captured.
  • TEST_CODE — Short alphanumeric code of the quality test, commonly the field users search on.
  • TEST_DESC — Descriptive name of the test.
  • TEST_CLASS — Classification grouping applied to the test.
  • TEST_TYPE — Resolved lookup meaning for the test type (LOOKUP_TYPE GMD_QC_TEST_TYPE), presented in the user's display language via the VL lookup view.
  • EXPRESSION — The calculation or expression associated with the test, where defined.
  • TEST_METHOD_CODE — Code of the analytical or inspection method used to obtain the result.

Common Use Cases and Queries

Typical scenarios include quality result reporting by instance, test definition listings, and integration extracts that need resolved test type meanings rather than internal lookup codes.

Search for a specific test by code:

SELECT test_id, update_instance_id, test_code, test_desc, test_type, test_method_code
FROM apps.gmd_qc_e_test_instance_v
WHERE test_code = 'PH';

List all tests captured for a given instance:

SELECT test_code, test_desc, test_class, test_type, expression, test_method_code
FROM apps.gmd_qc_e_test_instance_v
WHERE update_instance_id = :instance_id
ORDER BY test_code;

Because the view returns only test definition and method attributes — not the numeric result value itself — reports requiring the actual measured result must join back to GMD_RESULTS on TEST_ID and UPDATE_INSTANCE_ID. All queries should be issued with the APPS schema or through a synonym, and the view should be treated as read-only in all integrations.