Search Results ship_to_site_name




Overview
Explore in AI Chat

Overview

The GMD_QC_E_CUST_SMPEVT_DTLS_V view is a customer-facing sampling event reporting object owned by the APPS schema within the Process Manufacturing Product Development (GMD) module of Oracle E-Business Suite. It exposes quality sampling events that originate from customer-initiated sources and enriches them with descriptive attributes drawn from Oracle's trading partner, order management, and human resources data models. Rather than surfacing raw foreign key identifiers, the view resolves those identifiers into business-friendly names such as the customer name, operating unit name, ship-to site name, order number, order type, and order line number.

This view is particularly relevant to reporting and integration scenarios where users need a consolidated, denormalized picture of quality sampling activity tied to a specific customer and sales order. Its defining filter, GSMPEVT.SOURCE = 'C', restricts the result set to sampling events flagged as customer-related, distinguishing them from internal or process-driven sampling events.

Underlying Base Objects

The view is defined over eight documented base objects. The driving table is GMD_SAMPLING_EVENTS, which supplies the sampling event ID and the foreign keys to customer, operating unit, ship-to site, order, and order line. The remaining objects participate through joins:

Because most joins outside of the customer account relationship are outer joins, the view tolerates sampling events that lack an associated order, line, ship-to site, or operating unit, returning those columns as null.

Key Columns

  • SAMPLING_EVENT_ID — the primary identifier of the sampling event, inherited directly from GMD_SAMPLING_EVENTS.
  • CUSTOMER_NAME — the party name resolved from HZ_PARTIES, identifying the customer associated with the event.
  • OPERATING_UNIT_NAME — the organizational unit name from HR_OPERATING_UNITS.
  • SHIP_TO_SITE_NAME — the location/ship-to site description resolved from HZ_CUST_SITE_USES_ALL. This is the column most commonly used to associate sampling activity with a specific delivery destination.
  • ORDER_NUMBER — the sales order number from OE_ORDER_HEADERS_ALL.
  • ORDER_TYPE — the transaction type name from OE_TRANSACTION_TYPES.
  • ORDER_LINE_NUMBER — the order line number from OE_ORDER_LINES_ALL.

Common Use Cases and Queries

Typical usage includes quality dashboards that summarize customer-linked sampling events, traceability reports linking a sample to a specific shipment destination, and extracts feeding downstream quality or logistics systems.

To locate sampling events for a given ship-to site:

  • SELECT sampling_event_id, customer_name, ship_to_site_name, order_number FROM apps.gmd_qc_e_cust_smpevt_dtls_v WHERE ship_to_site_name = :site_name;

To report all customer-originated sampling events against a sales order:

  • SELECT order_number, order_line_number, customer_name, ship_to_site_name FROM apps.gmd_qc_e_cust_smpevt_dtls_v WHERE order_number = :order_number ORDER BY order_line_number;

Because the view already constrains SOURCE = 'C', queries should not re-filter on source. Given the outer joins, consumers should expect nullable values in the order, operating unit, and ship-to columns and design reporting logic accordingly.