Search Results gmd_qc_e_supp_sample_dtls_v




Overview
Explore in AI Chat

Overview

GMD_QC_E_SUPP_SAMPLE_DTLS_V is a critical reporting view within the Oracle E-Business Suite (EBS) Process Manufacturing (GMD) module, specifically focused on Product Development and Quality Control. The view provides a consolidated, denormalized perspective of supplier-related quality sample records. It serves as a bridge between the Quality module's sample tracking and the Procurement and Receiving sub-ledgers. By joining sample data with purchasing and receiving information, this view enables quality managers and supply chain analysts to trace a specific quality sample directly back to its originating purchase order (PO) and receipt. The inclusion of the RECEIPT_LINE_NUMBER and PO_LINE_NUMBER columns makes it an essential tool for reconciling quality inspections with physical inventory movements, ensuring that supplier quality issues can be pinpointed to exact shipment lines.

Underlying Base Objects

The view is defined over a complex join of several key EBS tables and views, primarily located in the APPS schema. The core driving table is GMD_SAMPLES (synonym for the base sample table), which holds the quality sample header information. It is joined to procurement entities including PO_VENDORS and PO_VENDOR_SITES_ALL to retrieve supplier details, and PO_HEADERS_ALL and PO_LINES_ALL to capture PO context. Receiving information is sourced from RCV_SHIPMENT_HEADERS and RCV_SHIPMENT_LINES. Operational unit data is derived from HR_OPERATING_UNITS, and inventory organization details are fetched from MTL_PARAMETERS. The view employs outer joins (indicated by (+)) on the PO and RCV tables, meaning that a quality sample will still appear even if it is not yet linked to a PO or receipt. The join condition GSMP.SOURCE = 'S' restricts the view to supplier-sourced samples only.

Key Columns

The view exposes a focused set of columns that map the quality sample lifecycle:

  • SAMPLE_ID: The unique identifier for the quality sample from GMD_SAMPLES.
  • SUPPLIER_CODE, SUPPLIER_NAME, SUPPLIER_SITE: Identify the vendor and specific site associated with the sample.
  • PO_NUMBER, PO_LINE_NUMBER: The purchasing document number and its line, providing procurement context.
  • RECEIPT_NUMBER, RECEIPT_LINE_NUMBER: The receiving transaction number and the specific line on that receipt. The receipt_line_number is critical for identifying which item on a multi-line receipt was sampled.
  • SUPPLIER_OPERATING_UNIT: The name of the HR operating unit responsible for the supplier relationship.
  • ORGANIZATION_ID, ORGANIZATION_CODE: The inventory organization where the sample or associated receipt is processed.

Common Use Cases and Queries

This view is typically used in quality assurance reports, supplier scorecards, and receiving discrepancy inquiries. A common requirement is to list all supplier quality samples alongside their receipt details to investigate a specific receipt line. The following query demonstrates retrieving samples for a given receipt number:

SELECT sample_id, supplier_name, po_number, receipt_number, receipt_line_number, organization_code
FROM apps.gmd_qc_e_supp_sample_dtls_v
WHERE receipt_number = :p_receipt_num;

Another frequent use case is analyzing supplier quality by operating unit, which can be achieved by grouping on SUPPLIER_OPERATING_UNIT and counting sample occurrences. The view is also useful for integration with external quality systems, as it provides a flat, query-friendly structure that avoids the complexity of joining the underlying transactional tables directly. Because the view includes outer joins, users should be aware that PO_NUMBER or RECEIPT_NUMBER may be null for samples that are not yet tied to a procurement or receiving transaction.