Results for “order_line_number”

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

Overview

GMD_QC_E_CUST_SAMPLE_DTLS_V is an APPS-owned, VALID database view shipped with the Oracle E-Business Suite Process Manufacturing Product Development (GMD) module. It is a denormalized reporting view that presents customer sample records from the Quality Control and sample management functions alongside their associated sales order context. The view is designed to answer a specific business question: for a given customer sample, what sales order and order line does it correspond to, and who is the customer, operating unit, and ship-to site involved?

The view exposes seven columns: SAMPLE_ID, CUSTOMER_NAME, OPERATING_UNIT_NAME, SHIP_TO_SITE_NAME, ORDER_NUMBER, ORDER_TYPE, and ORDER_LINE_NUMBER. Because the join to OE_ORDER_HEADERS_ALL, OE_TRANSACTION_TYPES, and OE_ORDER_LINES_ALL uses the Oracle outer join operator (+), the view returns sample rows even when no related sales order or line exists, making it suitable for reporting on samples that have not yet been tied to order activity. The inclusion of ORDER_LINE_NUMBER directly addresses the common search term "order_line_number," which is the line-level identifier on a sales order. The view filters exclusively on GSMP.SOURCE = 'C', restricting output to customer-sourced samples.

Underlying Base Objects

The view is defined over eight documented base objects across two product families. The driving table is GMD_SAMPLES (synonym), which holds sample master records including SAMPLE_ID, CUST_ID, ORG_ID, SHIP_TO_SITE_ID, ORDER_ID, ORDER_LINE_ID, and SOURCE. Customer master data is drawn from HZ_PARTIES (PARTY_NAME) joined to HZ_CUST_ACCOUNTS_ALL on PARTY_ID and CUST_ACCOUNT_ID, and ship-to site information from HZ_CUST_SITE_USES_ALL. Organizational context comes from HR_OPERATING_UNITS (a view) on ORGANIZATION_ID.

Order data is supplied entirely through outer-joined objects: OE_ORDER_HEADERS_ALL (ORDER_NUMBER), OE_TRANSACTION_TYPES (NAME as ORDER_TYPE via ORDER_TYPE_ID), and OE_ORDER_LINES_ALL (LINE_NUMBER via LINE_ID). The join chain is HEADER_ID = GSMP.ORDER_ID, TRANSACTION_TYPE_ID = OEOHA.ORDER_TYPE_ID, and LINE_ID = GSMP.ORDER_LINE_ID. All order-related and site/organization joins are outer, while the customer party and account joins are inner, meaning a sample must resolve to a valid customer party and account to appear in the result set.

Key Columns

• SAMPLE_ID — The primary identifier from GMD_SAMPLES, uniquely identifying each customer sample record.
• CUSTOMER_NAME — The party name (HZ_PARTIES.PARTY_NAME) of the customer associated with the sample, resolved through HZ_CUST_ACCOUNTS_ALL.
• OPERATING_UNIT_NAME — The name of the operating unit from HR_OPERATING_UNITS, matching the sample's ORG_ID.
• SHIP_TO_SITE_NAME — The ship-to location (HZ_CUST_SITE_USES_ALL.LOCATION) tied to the sample's SHIP_TO_SITE_ID.
• ORDER_NUMBER — The sales order header number from OE_ORDER_HEADERS_ALL; null when the sample is not linked to an order.
• ORDER_TYPE — The transaction type name (OE_TRANSACTION_TYPES.NAME) identifying the order classification.
• ORDER_LINE_NUMBER — The line number (OE_ORDER_LINES_ALL.LINE_NUMBER) that places the sample at a specific line on the referenced sales order; this is the column most often targeted by "order_line_number" searches.

Common Use Cases and Queries

This view is typically used for sample-to-order traceability reporting, customer sample activity analysis, and integration extracts that must reconcile QC samples against sales order demand. A representative query retrieving samples with their order line context is shown below.

SELECT sample_id, customer_name, order_number, order_type, order_line_number FROM apps.gmd_qc_e_cust_sample_dtls_v WHERE order_line_number IS NOT NULL ORDER BY order_number, order_line_number;

To report samples that have not yet been assigned to an order line, the outer-joined columns are tested for null values: SELECT sample_id, customer_name FROM apps.gmd_qc_e_cust_sample_dtls_v WHERE order_number IS NULL; Filtering by operating unit or customer name is also common for drill-down reporting. Because all order-side joins are outer, consumers must account for null ORDER_NUMBER and ORDER_LINE_NUMBER values in their result handling.