Search Results so_drop_ship_sources




Overview
Explore in AI Chat

Overview

The SO_DROP_SHIP_SOURCES table is a core transactional table within the Oracle E-Business Suite (EBS) Order Entry (OE) module, specifically for releases 12.1.1 and 12.2.2. It functions as a cross-reference repository that establishes and maintains the critical relationships between sales order lines and their corresponding procurement documents. Its primary role is to support the drop shipment fulfillment model, a business process where an item ordered by a customer is shipped directly from a supplier, bypassing the selling organization's inventory. This table is essential for tracking the entire lifecycle of a drop-ship order, from the initial creation of an internal requisition to the final generation of a purchase order sent to the supplier.

Key Information Stored

The table's structure is defined by its foreign key columns, which link it to the primary transactional entities in both the Order Management and Purchasing modules. While the specific internal technical columns (like creation dates and who columns) are not detailed in the provided metadata, the documented foreign keys reveal the core data relationships it stores. Each record acts as a junction point, connecting a specific sales order line (LINE_ID) to one or more procurement document identifiers. These identifiers include the purchase order header (PO_HEADER_ID) and line (PO_LINE_ID), the purchase order shipment or line location (LINE_LOCATION_ID), and the internal requisition header (REQUISITION_HEADER_ID) and line (REQUISITION_LINE_ID) from which the purchase order may have been sourced.

Common Use Cases and Queries

The primary use case is tracking and reporting on drop-ship order fulfillment status. Common operational queries involve joining this table to sales order and purchase order tables to answer critical business questions. For instance, to identify all sales orders awaiting supplier shipment, one might query the link between SO_DROP_SHIP_SOURCES and PO_LINE_LOCATIONS_ALL to check receipt status. Another frequent pattern is tracing the procurement path for a given sales order line to troubleshoot fulfillment delays. A basic reporting query to list all drop-ship relationships would follow this structure:

  • SELECT sl.line_number, sl.ordered_item, ph.segment1 po_number, pl.line_num po_line
  • FROM oe.so_drop_ship_sources dss,
  • oe.so_lines_all sl,
  • po.po_headers_all ph,
  • po.po_lines_all pl
  • WHERE dss.line_id = sl.line_id
  • AND dss.po_header_id = ph.po_header_id
  • AND dss.po_line_id = pl.po_line_id;

Related Objects

As documented in the provided foreign key metadata, SO_DROP_SHIP_SOURCES is a central hub with defined relationships to key tables in the Order Management and Purchasing schemas. These relationships are critical for data integrity and process flow.

  • SO_LINES_ALL: Links via SO_DROP_SHIP_SOURCES.LINE_ID. This is the foundational relationship to the sales order line being fulfilled.
  • PO_HEADERS_ALL: Links via SO_DROP_SHIP_SOURCES.PO_HEADER_ID. Connects to the purchase order issued to the supplier.
  • PO_LINES_ALL: Links via SO_DROP_SHIP_SOURCES.PO_LINE_ID. Connects to the specific line on the purchase order.
  • PO_LINE_LOCATIONS_ALL: Links via SO_DROP_SHIP_SOURCES.LINE_LOCATION_ID. Connects to the shipment/schedule details of the purchase order line.
  • PO_REQUISITION_HEADERS_ALL: Links via SO_DROP_SHIP_SOURCES.REQUISITION_HEADER_ID. Connects to the internal requisition that initiated procurement.
  • PO_REQUISITION_LINES_ALL: Links via SO_DROP_SHIP_SOURCES.REQUISITION_LINE_ID. Connects to the specific line on the internal requisition.