Skip to content
EBS Reference

OE_DROP_SHIP_SOURCES

Schema: ONTtransactionOU-striped (ORG_ID)

The drop-ship bridge — one row linking a sales order line to the purchase requisition and purchase order raised to fulfill it from the supplier; the only physical tie between the order-to-cash and procure-to-pay flows

Module: Order ManagementOperating-unit striped (ORG_ID)
Notes

No enforced primary key in the data dictionary — DROP_SHIP_SOURCE_ID is the working surrogate key. Pointer naming differs across tables: the PO shipment column here is LINE_LOCATION_ID, while the supply picture spells it PO_LINE_LOCATION_ID.

What the badges mean
master
Data class: what the table holds — master data, transaction documents, control/configuration, interface/staging, or an APPS-schema view.
In field listings, K marks a primary-key field.

Fields

11 fields · 1 key

Table fields: position, field name, description, data type, and flags. 11 fields.
#FieldDescriptionTypeFlags
1DROP_SHIP_SOURCE_IDWorking surrogate key — no enforced primary key in the data dictionaryNUMBER
Key
2ORG_IDOperating unit — drop-ship raises the requisition and PO in the order's OUNUMBER
3HEADER_IDThe sales order headerNUMBER
4LINE_IDThe sales order line being drop-shippedNUMBER
5DESTINATION_ORGANIZATION_IDThe receiving inventory org on the purchasing sideNUMBER
6REQUISITION_HEADER_IDThe requisition raised for the lineNUMBER
7REQUISITION_LINE_IDThe requisition lineNUMBER
8PO_HEADER_IDThe purchase order raised, once autocreatedNUMBER
9PO_LINE_IDThe purchase order lineNUMBER
10LINE_LOCATION_IDThe PO shipment schedule — this table's name for it (the supply picture spells it PO_LINE_LOCATION_ID)NUMBER
11PO_RELEASE_IDThe blanket release, when fulfilled off an agreementNUMBER

Field provenance: hand-curated. 1 key field.

Boilerplate SQL

Starting point for reading OE_DROP_SHIP_SOURCESon Databricks — real DATE columns need no conversion, and the org anchor and the LAST_UPDATE_DATE watermark are already in place. Set your Unity Catalog location, schema, and org values below; they’re substituted into the SQL and the copy button.

Query parameters
-- ============================================================
-- Table  : OE_DROP_SHIP_SOURCES — The drop-ship bridge — one row linking a sales order line to the purchase requisition and purchase order raised to fulfill it from the supplier; the only physical tie between the order-to-cash and procure-to-pay flows
-- Purpose: Column-selected read of OE_DROP_SHIP_SOURCES — auto-generated from field metadata
-- Grain  : One row per operating unit (ORG_ID) + DROP_SHIP_SOURCE_ID
-- Notes  : Auto-generated skeleton for Oracle EBS R12 data landed in your lakehouse. Dates are real DATE/TIMESTAMP columns — no conversion needed. WHO audit columns omitted (see the quirks guide); the optional LAST_UPDATE_DATE watermark filter supports incremental extracts.
-- ============================================================
SELECT
  t.DROP_SHIP_SOURCE_ID AS "Working surrogate key — no enforced primary key in the data dictionary",
  t.ORG_ID AS "Operating unit — drop-ship raises the requisition and PO in the order's OU",
  t.HEADER_ID AS "The sales order header",
  t.LINE_ID AS "The sales order line being drop-shipped",
  t.DESTINATION_ORGANIZATION_ID AS "The receiving inventory org on the purchasing side",
  t.REQUISITION_HEADER_ID AS "The requisition raised for the line",
  t.REQUISITION_LINE_ID AS "The requisition line",
  t.PO_HEADER_ID AS "The purchase order raised, once autocreated",
  t.PO_LINE_ID AS "The purchase order line",
  t.LINE_LOCATION_ID AS "The PO shipment schedule — this table's name for it (the supply picture spells it PO_LINE_LOCATION_ID)",
  t.PO_RELEASE_ID AS "The blanket release, when fulfilled off an agreement"
FROM <catalog>.<schema>.OE_DROP_SHIP_SOURCES t
WHERE
  t.ORG_ID = <operating_unit_id>  -- operating unit (MOAC does not filter extracts)
  -- AND t.DROP_SHIP_SOURCE_ID = <DROP_SHIP_SOURCE_ID>
  -- AND t.LAST_UPDATE_DATE >= TIMESTAMP '<watermark>'  -- WHO watermark, bulk-stamped by batch jobs; see quirks guide #who-columns
ORDER BY t.DROP_SHIP_SOURCE_ID;

5 parameters not filled: <catalog>, <schema>, <operating_unit_id>, <DROP_SHIP_SOURCE_ID>, <watermark>

Relationships

1-hop neighbors — click a table to navigate there. FND lookup decode and translation edges are highlighted; they’re the joins newcomers most often get wrong.

Join details

  • OE_DROP_SHIP_SOURCESOE_ORDER_HEADERS_ALLforeign key · N:1
    ON OE_DROP_SHIP_SOURCES.HEADER_ID = OE_ORDER_HEADERS_ALL.HEADER_ID AND OE_DROP_SHIP_SOURCES.ORG_ID = OE_ORDER_HEADERS_ALL.ORG_ID
  • OE_DROP_SHIP_SOURCESOE_ORDER_LINES_ALLforeign key · N:1
    ON OE_DROP_SHIP_SOURCES.LINE_ID = OE_ORDER_LINES_ALL.LINE_ID AND OE_DROP_SHIP_SOURCES.ORG_ID = OE_ORDER_LINES_ALL.ORG_ID
  • OE_DROP_SHIP_SOURCESPO_HEADERS_ALLforeign key · N:1
    ON OE_DROP_SHIP_SOURCES.PO_HEADER_ID = PO_HEADERS_ALL.PO_HEADER_ID AND OE_DROP_SHIP_SOURCES.ORG_ID = PO_HEADERS_ALL.ORG_ID
  • OE_DROP_SHIP_SOURCESPO_LINE_LOCATIONS_ALLforeign key · N:1
    ON OE_DROP_SHIP_SOURCES.LINE_LOCATION_ID = PO_LINE_LOCATIONS_ALL.LINE_LOCATION_ID AND OE_DROP_SHIP_SOURCES.ORG_ID = PO_LINE_LOCATIONS_ALL.ORG_ID
  • OE_DROP_SHIP_SOURCESPO_REQUISITION_HEADERS_ALLforeign key · N:1
    ON OE_DROP_SHIP_SOURCES.REQUISITION_HEADER_ID = PO_REQUISITION_HEADERS_ALL.REQUISITION_HEADER_ID AND OE_DROP_SHIP_SOURCES.ORG_ID = PO_REQUISITION_HEADERS_ALL.ORG_ID
  • OE_DROP_SHIP_SOURCESPO_REQUISITION_LINES_ALLforeign key · N:1
    ON OE_DROP_SHIP_SOURCES.REQUISITION_LINE_ID = PO_REQUISITION_LINES_ALL.REQUISITION_LINE_ID AND OE_DROP_SHIP_SOURCES.ORG_ID = PO_REQUISITION_LINES_ALL.ORG_ID

Browse more Order Managementtables →

Maintained by Summit Analytics, a supply chain analytics practice. The tools and references are free — the consulting is selective.

Part of the Summit Analytics reference library.

Work with the practice →

Not affiliated with or endorsed by Oracle. Oracle and Oracle E-Business Suite are registered trademarks of Oracle and/or its affiliates.