Results for “sampling_event_id”

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

Overview

GMD_QC_E_SUPP_SMPEVT_DTLS_V is a reporting view owned by the APPS schema in Oracle E-Business Suite, registered under the GMD (Process Manufacturing Product Development) product family. It presents supplier-facing sampling event detail, denormalizing a quality sampling event together with the supplier, purchase order, and receiving information that describes the material's origin. The view is used primarily by Oracle Quality and Process Manufacturing quality modules when a sampling event must be traced back to an external supplier shipment.

The predicate GSMPEVT.SOURCE = 'S' restricts output to supplier-sourced sampling events, so the view excludes internal or production-sourced events. This makes it a targeted reporting surface for supplier quality analysis rather than a general-purpose sampling event listing.

Underlying Base Objects

The view is defined over seven base objects joined on the GMD_SAMPLING_EVENTS driving table:

• GMD_SAMPLING_EVENTS (SYNONYM) — the driving table; provides SAMPLING_EVENT_ID, SUPPLIER_ID, SUPPLIER_SITE_ID, PO_HEADER_ID, PO_LINE_ID, RECEIPT_ID, RECEIPT_LINE_ID, SOURCE, and ORG_ID.
• PO_VENDORS (VIEW) — supplies the supplier code (SEGMENT1) and vendor name. Joined on SUPPLIER_ID = VENDOR_ID as an inner join.
• PO_VENDOR_SITES_ALL (VIEW) — supplies the supplier site code. Joined with an outer join (+) on SUPPLIER_SITE_ID = VENDOR_SITE_ID.
• PO_HEADERS_ALL / PO_LINES_ALL (SYNONYMS) — provide the purchase order number and line number, both outer-joined.
• RCV_SHIPMENT_HEADERS / RCV_SHIPMENT_LINES (SYNONYMS) — provide the receipt number and receipt line number, both outer-joined.
• FND_GLOBAL (PACKAGE) — referenced for session/org context within the APPS environment.

Because the PO and receiving joins are outer joins, a sampling event can be reported even when no purchase order or receipt has yet been associated with it, provided a supplier exists.

Key Columns

• SAMPLING_EVENT_ID — Primary identifier of the quality sampling event; the join key back to GMD_SAMPLING_EVENTS.
• SUPPLIER_CODE — Vendor number from PO_VENDORS.SEGMENT1, used as the supplier's business key.
• SUPPLIER_NAME — Vendor name, useful for display and grouping in reports.
• SUPPLIER_SITE — Supplier site code from PO_VENDOR_SITES_ALL.VENDOR_SITE_CODE, the value most users associate with "supplier_site."
• PO_NUMBER / PO_LINE_NUMBER — Purchase order reference linked to the sampling event.
• RECEIPT_NUMBER / RECEIPT_LINE_NUMBER — Receiving transaction reference, enabling linkage to the inbound shipment.
• ORG_ID — Operating unit / organization identifier, supporting multi-org security filtering.

Common Use Cases and Queries

The view is typically used to answer supplier quality questions: which suppliers and sites generated sampling events, which purchase orders and receipts those events relate to, and how many events occur per supplier site. A typical query searching for a specific supplier site is:

• SELECT sampling_event_id, supplier_code, supplier_name, supplier_site, po_number, receipt_number FROM gmd_qc_e_supp_smpevt_dtls_v WHERE supplier_site = :p_site;
• Aggregation by supplier site for event counts: SELECT supplier_site, COUNT(sampling_event_id) FROM gmd_qc_e_supp_smpevt_dtls_v GROUP BY supplier_site;
• Joining back to GMD_SAMPLING_EVENTS on SAMPLING_EVENT_ID to retrieve additional sampling attributes not exposed here.
• Multi-org filtering by adding WHERE org_id = :p_org_id to respect operating unit security.

In integration and reporting contexts, the view serves as a denormalized source for supplier quality dashboards, receiving-to-inspection traceability, and procurement-linked quality analysis across 12.1.1 and 12.2.2 releases.