Search Results received_uom




Overview
Explore in AI Chat

Overview

APPS.SO_DROP_SHIP_LINKS_V is a supplementary view in the Oracle E-Business Suite Order Management schema (OE), registered under FND Design Data as OE.SO_DROP_SHIP_LINKS_V. It is classified as a "supplementary view used to simplify forms coding," meaning it exists primarily to support the Drop Ship Links form rather than to serve as a public integration interface. Oracle explicitly warns that this view should not be queried or altered directly for data manipulation, as its definition may change dramatically across minor or major releases. The view consolidates drop-shipment linkage data spanning Order Management sales order lines, Purchasing requisitions, purchase orders, releases, and receipt information, presenting a single denormalized row per drop-ship link. It is marked VALID in 12.1.1 and 12.2.2.

Underlying Base Objects

The view draws from a broad set of transactional and reference objects. Purchasing-side objects include PO_HEADERS, PO_LINES, PO_LINE_LOCATIONS, PO_RELEASES, PO_REQUISITION_HEADERS, PO_REQUISITION_LINES, and PO_VENDORS, supplying requisition numbers, purchase order references, supplier item, pricing, and receipt details. Order Management objects include SO_LINES, SO_DROP_SHIP_SOURCES, and SO_LOOKUPS, providing the sales order line context and lookup decoding. Supporting objects include FINANCIALS_SYSTEM_PARAMETERS and GL_SETS_OF_BOOKS for ledger context, and several HR views and packages — HR_LOCATIONS, HR_PERSON_NAME, PER_PEOPLE_F, HR_GENERAL, and HR_SECURITY — for buyer name resolution and security filtering. FND_GLOBAL supplies session context, and OE_DROP_SHIP_PVT provides the core drop-ship business logic. The view is not referenced by any database object, confirming its role as a terminal presentation layer.

Key Columns

Common Use Cases and Queries

The principal use case is the Drop Ship Links form, where it displays the relationship between sales order lines and their sourcing purchase documents, including receipt status. The RECEIVED_UOM and QUANTITY_RECEIVED columns support reconciliation of receipted quantities against ordered quantities, a frequent requirement in drop-shipment auditing. A sample query follows:

  • SELECT line_id, po_req_number, line_num, vendor_name, ordered_uom, quantity, received_uom, quantity_received FROM apps.so_drop_ship_links_v WHERE line_id = :p_line_id;
  • SELECT po_req_number, vendor_name, received_uom, quantity_received FROM apps.so_drop_ship_links_v WHERE quantity_received > 0;

Because the view performs HR security filtering and joins numerous high-volume tables, queries should always be constrained by LINE_ID or a specific requisition identifier to avoid full-table scans. Given Oracle's stated caution, custom development should prefer the underlying OE_DROP_SHIP_PVT APIs or a purpose-built extract rather than depending on this view's structure remaining stable across releases.