Search Results po_req_number




Overview
Explore in AI Chat

Overview

APPS.OE_DROP_SHIP_LINKS_V is an Oracle E-Business Suite view that exposes the linkage between Order Management drop-ship demand lines and their corresponding procurement documents. It is a UNION-based view: the first branch returns purchase order drop-ship links, and the second branch returns requisition-based drop-ship links. For each sales order line sourced by an external supplier, the view presents the sourcing document header, line, schedule, buyer, supplier, and quantity information in a single denormalized structure. Because it spans both Order Management and Purchasing, it is used for reporting, integration, and validation of the drop-ship supply chain — confirming that ordered quantities, receipt quantities, and supplier details align with the originating sales order demand.

The view is defined in the APPS schema and is therefore queried with the standard APPS credentials. It is read-only and reflects committed transactional data in real time; it does not store data of its own.

Underlying Base Objects

The documented base objects include PO_HEADERS_ALL, PO_LINES_ALL, PO_LINE_LOCATIONS_ALL, PO_RELEASES_ALL, PO_REQUISITION_HEADERS_ALL, and PO_REQUISITION_LINES_ALL for the procurement side; OE_ORDER_LINES_ALL and OE_DROP_SHIP_SOURCES for the order side; OE_LOOKUPS for the document type meaning; PER_PEOPLE_F for the buyer name; PO_VENDORS for supplier information; HR_LOCATIONS for ship-to location data; and FINANCIALS_SYSTEM_PARAMS_ALL, GL_SETS_OF_BOOKS, HR_GENERAL, HR_PERSON_NAME, and HR_SECURITY for organizational and security context.

OE_DROP_SHIP_SOURCES is the pivotal table. It stores one row per drop-ship association, holding LINE_ID (the sales order line), PO_HEADER_ID, PO_LINE_ID, and LINE_LOCATION_ID. The view joins this to OE_ORDER_LINES_ALL on LINE_ID, and to the PO/requisition tables on the header, line, and location keys. Rows with PO_RELEASE_ID are excluded from the purchase order branch. The PER_PEOPLE_F join is date-effective as of TRUNC(SYSDATE), and outer joins are applied to HR_LOCATIONS and PO_VENDORS.

Key Columns

Common Use Cases and Queries

Typical uses include order-to-supplier traceability reports, drop-ship receipt reconciliation, UOM discrepancy analysis between ordered and received quantities, and supplier performance metrics. The following query lists drop-ship lines and their ordered UOM for a given sales order line:

  • SELECT LINE_ID, PO_REQ_NUMBER, LINE_NUM, SUPPLIER_ITEM, ORDERED_UOM, QUANTITY, RECEIVED_UOM, QUANTITY_RECEIVED FROM APPS.OE_DROP_SHIP_LINKS_V WHERE LINE_ID = :p_line_id;
  • SELECT DOCUMENT_TYPE, ORDERED_UOM, SUM(QUANTITY) FROM APPS.OE_DROP_SHIP_LINKS_V WHERE ORG_ID = :p_org_id GROUP BY DOCUMENT_TYPE, ORDERED_UOM;
  • Detecting UOM mismatches: SELECT LINE_ID, ORDERED_UOM, RECEIVED_UOM FROM APPS.OE_DROP_SHIP_LINKS_V WHERE ORDERED_UOM <> RECEIVED_UOM;

Because the view contains a UNION with a hard-coded document type filter and a SYSDATE-driven people join, queries should restrict by LINE_ID or ORG_ID where possible to limit full-scan cost.