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
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
- Schema: INV
- Schema: the Oracle product schema that owns the table (INV, ONT, WSH, PO, BOM, WIP, MRP, MSC, AR, AP, GL, HR, APPLSYS) — tells you which product family the object belongs to, not who can query it.
- master
- Data class: what the table holds — master data, transaction documents, control/configuration, interface/staging, or an APPS-schema view.
- OU-striped (ORG_ID)
- Rows are scoped to an operating unit. A landed extract carries every operating unit’s rows — filter or join on
ORG_ID, and don’t confuse it withORGANIZATION_ID(see the quirks guide). - Per inventory org
- Rows are scoped to an inventory organization (plant or warehouse) via
ORGANIZATION_ID— a different partition from OU-striped tables (see the quirks guide). - Language-striped
- The table carries a
LANGUAGEcolumn (a _TL translation table or FND_LOOKUP_VALUES) — one row per language. Filter to oneLANGUAGEor a join multiplies rows (see the quirks guide). - View
- This is an APPS-schema convenience view, not a physical table. Extract the base tables it joins instead — views can be slow at scale and aren't guaranteed stable across patches.
Structural facts — how the table is partitioned, not a trap by itself
Join & extract hazards — verify before you rely on this
Fields
11 fields · 1 key
11 fields.
| # | Field | Description | Type | Flags |
|---|---|---|---|---|
| 1 | DROP_SHIP_SOURCE_ID | Working surrogate key — no enforced primary key in the data dictionary | NUMBER | Primary-key field |
| 2 | ORG_ID | Operating unit — drop-ship raises the requisition and PO in the order's OU | NUMBER | |
| 3 | HEADER_ID | The sales order header | NUMBER | |
| 4 | LINE_ID | The sales order line being drop-shipped | NUMBER | |
| 5 | DESTINATION_ORGANIZATION_ID | The receiving inventory org on the purchasing side | NUMBER | |
| 6 | REQUISITION_HEADER_ID | The requisition raised for the line | NUMBER | |
| 7 | REQUISITION_LINE_ID | The requisition line | NUMBER | |
| 8 | PO_HEADER_ID | The purchase order raised, once autocreated | NUMBER | |
| 9 | PO_LINE_ID | The purchase order line | NUMBER | |
| 10 | LINE_LOCATION_ID | The PO shipment schedule — this table's name for it (the supply picture spells it PO_LINE_LOCATION_ID) | NUMBER | |
| 11 | PO_RELEASE_ID | The blanket release, when fulfilled off an agreement | NUMBER |
Field provenance: hand-curated. 1 key field.
Boilerplate SQL
Starting point for reading OE_DROP_SHIP_SOURCES on Databricks — real DATE columns need no conversion, and the org anchor is already in place. The optional LAST_UPDATE_DATE watermark is included. Set your Unity Catalog location, schema, and org values below; they’re substituted into the SQL and the copy button.
5 parameters not filled: <catalog>, <schema>, <operating_unit_id>, <DROP_SHIP_SOURCE_ID>, <watermark>
-- ============================================================
-- 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;Verified September 2026
Relationships
Diagram of 1-hop neighbors — join details below. FND lookup decode and translation edges are highlighted; they’re the joins newcomers most often get wrong.
Join details
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_IDON OE_DROP_SHIP_SOURCES.LINE_ID = OE_ORDER_LINES_ALL.LINE_ID AND OE_DROP_SHIP_SOURCES.ORG_ID = OE_ORDER_LINES_ALL.ORG_IDON OE_DROP_SHIP_SOURCES.PO_HEADER_ID = PO_HEADERS_ALL.PO_HEADER_ID AND OE_DROP_SHIP_SOURCES.ORG_ID = PO_HEADERS_ALL.ORG_IDON 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_IDON 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_IDON 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
More Order Management tables
- OE_HOLD_DEFINITIONSHold definitions — the named hold types (credit check, administrative…) with their workflow scope and effectivity; global seed data every hold instance resolves to
- OE_HOLD_SOURCES_ALLHold source criteria — the entity a hold was applied against (a customer, an order, an item, a warehouse), stored as a generic entity code plus a polymorphic id, with the hold-until date
- OE_ORDER_HEADERS_ALLThe sales order header — one row per order or quote, carrying the order number, type, customer references, currency, and the workflow status the whole order-to-cash cycle hangs off; operating-unit striped
- OE_ORDER_HOLDS_ALLHold instances on orders and lines — one row per applied hold, pointing at the hold source that applied it and the release record once lifted; the "why isn't this line shipping" table
- OE_ORDER_LINES_ALLSales order lines at their most granular workflow unit — shipment splits, model options, included items, and configuration items each get their own row, individually statused and quantity-tracked through booking, shipping, and invoicing
- OE_ORDER_SOURCESThe order source master — the feeder systems order import brings sales documents in from (EDI, web, copies, internal orders), a small global decode for ORDER_SOURCE_ID