Search Results test_method_desc




Overview
Explore in AI Chat

Overview

The view APPS.GMD_QC_E_RESULTS_V belongs to the Oracle EBS Process Manufacturing Product Development module (product code GMD) and is a central reporting object for quality control (QC) result data. It consolidates information from the sample, result, and specification domains into a single denormalized structure, allowing concurrent programs, Oracle Reports, OAF pages, and integration extracts to retrieve QC results with all relevant context in one pass. The view is documented as VALID and owned by the APPS schema, which is the standard convention for Oracle EBS seed objects that must be accessed through a synonym with APPS as the connecting user.

The "E" prefix in the object name typically denotes an "enterprise" or extract-oriented view, and the presence of SAMPLE_ID as a leading column confirms that the view is a primary entry point for queries searching on sample_no, the user-visible sample identifier. Organizations commonly expose SAMPLE_ID to end users through sample numbering flexfields or generated sample numbers, and this view is the natural retrieval path when correlating a sample number with its associated test results and specification limits.

Underlying Base Objects

The documented base objects referenced by this view are:

The view is defined in part over public synonyms, so its dependencies resolve to the same base tables regardless of whether the caller connects as APPS or an application user.

Key Columns

Common Use Cases and Queries

A frequent requirement is to retrieve all results for a given sample number. Because the view exposes SAMPLE_ID rather than a formatted sample number, the query typically joins to GMD_SAMPLES or filters by the numeric surrogate key resolved from the sample number:

A representative query is:

SELECT r.sample_id, r.test_id, r.test_result, r.result_meaning, r.spec_min_value, r.spec_target_value, r.spec_max_value, r.result_date FROM apps.gmd_qc_e_results_v r WHERE r.sample_id = :sample_no ORDER BY r.seq;

Because the view is a database object rather than a table, it carries no indexes of its own; performance depends on the indexes of the underlying base tables and on the efficiency of the specification and lookup joins.