Search Results supplier_operating_unit

Overview

APPS.GMD_QC_E_SUPP_SAMPLE_DTLS_V is an Oracle E-Business Suite internal view owned by the APPS schema and registered under FND Design Data as GMD.GMD_QC_E_SUPP_SAMPLE_DTLS_V. It presents supplier-facing quality control sample details, joining quality sample records to the originating purchasing and receiving documents, and enriching them with supplier, site, and inventory organization context. The view exposes eleven columns covering the sample identifier, supplier identification, purchase order and receipt references, the supplier operating unit, and the inventory organization.

The object is documented as View Type "Internal" and carries the standard Oracle restriction that it is intended for use by standard Oracle Applications programs rather than as a supported public interface. In Oracle EBS 12.1.1 and 12.2.2 it therefore functions primarily as a reporting and integration aid for supplier quality sample data surfaced within the Quality module, not as a supported API.

Underlying Base Objects

The documented dependency list shows the view is defined over the following objects: FND_GLOBAL (PACKAGE), GMD_SAMPLES (SYNONYM), HR_OPERATING_UNITS (VIEW), MTL_PARAMETERS (SYNONYM), PO_HEADERS_ALL (SYNONYM), PO_LINES_ALL (SYNONYM), PO_VENDORS (VIEW), PO_VENDOR_SITES_ALL (VIEW), RCV_SHIPMENT_HEADERS (SYNONYM), and RCV_SHIPMENT_LINES (SYNONYM).

• GMD_SAMPLES supplies the core sample record, including SAMPLE_ID.
• PO_HEADERS_ALL and PO_LINES_ALL provide the purchase order number and line number associated with the sample.
• RCV_SHIPMENT_HEADERS and RCV_SHIPMENT_LINES provide receipt number and receipt line number details.
• PO_VENDORS and PO_VENDOR_SITES_ALL supply supplier code, supplier name, and supplier site.
• HR_OPERATING_UNITS supplies the SUPPLIER_OPERATING_UNIT value.
• MTL_PARAMETERS supplies the inventory organization identifier and code.
• FND_GLOBAL is referenced for session-level context such as the current operating unit.

The view is not referenced by any other database object, confirming it sits at the reporting edge of the schema rather than within a dependency chain.

Key Columns

• SAMPLE_ID (NUMBER) — unique sample identifier, database-sequenced.
• SUPPLIER_CODE (VARCHAR2 30), SUPPLIER_NAME (VARCHAR2 240), SUPPLIER_SITE (VARCHAR2 15) — supplier identification derived from the vendor and vendor site views.
• PO_NUMBER (VARCHAR2 20) and PO_LINE_NUMBER (NUMBER) — the sourcing purchase order and line.
• RECEIPT_NUMBER (VARCHAR2 30) and RECEIPT_LINE_NUMBER (NUMBER) — the receiving document and line linked to the sample.
• SUPPLIER_OPERATING_UNIT (VARCHAR2 240) — the operating unit associated with the supplier relationship, resolved through HR_OPERATING_UNITS. This is the column most commonly searched when filtering samples by the operating unit that owns the supplier.
• ORGANIZATION_ID (NUMBER) and ORGANIZATION_CODE — the inventory organization from MTL_PARAMETERS, identifying where the sampled material resides.

Common Use Cases and Queries

Typical scenarios include tracing a quality sample back to its purchase order and receipt, reporting sample volumes by supplier or supplier site, and filtering samples by the supplier's operating unit in multi-org deployments. Because the object is internal and subject to change, consumers should treat it as read-only and validate results against supported Quality and Purchasing reports.

To retrieve all supplier sample details, run:

• SELECT SAMPLE_ID, SUPPLIER_CODE, SUPPLIER_NAME, SUPPLIER_SITE, PO_NUMBER, PO_LINE_NUMBER, RECEIPT_NUMBER, RECEIPT_LINE_NUMBER, SUPPLIER_OPERATING_UNIT, ORGANIZATION_ID, ORGANIZATION_CODE FROM APPS.GMD_QC_E_SUPP_SAMPLE_DTLS_V;

To narrow results to a specific operating unit, add a predicate such as WHERE SUPPLIER_OPERATING_UNIT = :p_operating_unit. To isolate samples tied to a given receipt, filter on RECEIPT_NUMBER, and to group activity by supplier, aggregate on SUPPLIER_CODE or SUPPLIER_SITE. In 12.1.1 and 12.2.2 the column set is identical, so the same query text applies to both releases.