Search Results gmd_qc_e_samples_used_v




Overview
Explore in AI Chat

Overview

GMD_QC_E_SAMPLES_USED_V is a reporting view owned by the APPS schema in Oracle E-Business Suite, delivered as part of the GMD product family — Process Manufacturing Product Development, also referred to as Oracle Quality or E-Records/ETRM. The view presents the association between composite quality results and the individual sample results that contribute to them, enriching each row with descriptive sample information and a decoded exclusion flag. Its name reflects its purpose: it lists samples used within a composite result context, exposing the human-readable SAMPLE_DESC column that users commonly search on when auditing which physical sample a given result originated from.

As a view rather than a base table, GMD_QC_E_SAMPLES_USED_V carries no persistent storage of its own. It is a read-only projection intended for inquiry screens, concurrent program extracts, and ad hoc reporting. In EBS 12.1.1 and 12.2.2 the object is registered as VALID in the APPS schema, and the compiled text resolves entirely against other APPS-owned synonyms and views.

Underlying Base Objects

The view is constructed from a five-table join plus two lookup references. The documented base objects are:

Each GMD object is surfaced to APPS through a synonym, so the view depends on the GMD base tables beneath those synonyms. The joins are strictly inner joins on RESULT_ID, SAMPLE_ID, and TEST_ID, meaning a row appears only when a result is associated with a composite, belongs to a valid sample, and references a defined test.

Key Columns

  • COMPOSITE_RESULT_ID — identifier of the parent composite result record.
  • RESULT_ID — identifier of the individual result contributing to the composite.
  • SAMPLE_NO — the sample number, aliased from GMD_SAMPLES.SAMPLE_NO, useful for operational reference.
  • SAMPLE_ID — the internal surrogate key of the sample.
  • SAMPLE_DESC — the free-text sample description; this is the column users most frequently search, and it is the primary human-readable attribute in the view.
  • TEST_RESULT — a DECODE-derived value that returns RESULT_VALUE_NUM for test types 'E' (numeric), 'N' (numeric), and 'L' (numeric/lookup), and RESULT_VALUE_CHAR for type 'T' (text), normalising heterogeneous result storage into a single column.
  • EXCLUDE_IND — the exclusion indicator resolved through the GMD_QC_YES_NO lookup, returning the Y or N meaning via DECODE on EXCLUDE_IND.
  • TEST_UNIT — the unit of measure associated with the test definition.

Common Use Cases and Queries

Typical uses include reconciliation of composite versus contributing results, sample traceability audits, and extracts that feed quality data warehouses. Because SAMPLE_DESC is the searched term, filtering on it is the most frequent access pattern.

List all samples used with their results for a given composite:

  • SELECT sample_no, sample_desc, test_result, test_unit, exclude_ind FROM apps.gmd_qc_e_samples_used_v WHERE composite_result_id = :p_composite_id;

Search by sample description, the user's stated interest:

  • SELECT sample_no, sample_id, sample_desc, test_result FROM apps.gmd_qc_e_samples_used_v WHERE UPPER(sample_desc) LIKE UPPER('%' || :p_search || '%');

Identify excluded results for quality review:

  • SELECT sample_desc, test_result, exclude_ind FROM apps.gmd_qc_e_samples_used_v WHERE exclude_ind = 'Yes';

Joining to GMD_RESULTS or GMD_SAMPLES on SAMPLE_ID or RESULT_ID is straightforward when additional base-table attributes are required, since the view exposes both keys.