OE_ORDER_HOLDS_ALL
Schema: ONTtransactionOU-striped (ORG_ID)Hold 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
LINE_ID is NULL for order-level holds — a line-only filter silently drops them. Active holds are RELEASED_FLAG = 'N'; release timing lives on the hold-release record (not yet cataloged).
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
8 fields · 1 key
8 fields.
| # | Field | Description | Type | Flags |
|---|---|---|---|---|
| 1 | ORDER_HOLD_ID | Surrogate key of the hold instance | NUMBER | Primary-key field |
| 2 | ORG_ID | Operating unit | NUMBER | |
| 3 | HEADER_ID | The held order | NUMBER | |
| 4 | LINE_ID | The held line — NULL for order-level holds, so a line-only filter drops them | NUMBER | |
| 5 | HOLD_SOURCE_ID | The hold source (criteria) that applied this hold | NUMBER | |
| 6 | HOLD_RELEASE_ID | The release record once lifted — NULL while the hold is active | NUMBER | |
| 7 | RELEASED_FLAG | N while the hold is active — the open-holds filter | VARCHAR2 | |
| 8 | CREDIT_PROFILE_LEVEL | Credit-check profile level for credit holds | VARCHAR2 |
Field provenance: hand-curated. 1 key field.
Boilerplate SQL
Starting point for reading OE_ORDER_HOLDS_ALL 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>, <ORDER_HOLD_ID>, <watermark>
-- ============================================================
-- Table : OE_ORDER_HOLDS_ALL — Hold 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
-- Purpose: Column-selected read of OE_ORDER_HOLDS_ALL — auto-generated from field metadata
-- Grain : One row per operating unit (ORG_ID) + ORDER_HOLD_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.ORDER_HOLD_ID AS "Surrogate key of the hold instance",
t.ORG_ID AS "Operating unit",
t.HEADER_ID AS "The held order",
t.LINE_ID AS "The held line — NULL for order-level holds, so a line-only filter drops them",
t.HOLD_SOURCE_ID AS "The hold source (criteria) that applied this hold",
t.HOLD_RELEASE_ID AS "The release record once lifted — NULL while the hold is active",
t.RELEASED_FLAG AS "N while the hold is active — the open-holds filter",
t.CREDIT_PROFILE_LEVEL AS "Credit-check profile level for credit holds"
FROM <catalog>.<schema>.OE_ORDER_HOLDS_ALL t
WHERE
t.ORG_ID = <operating_unit_id> -- operating unit (MOAC does not filter extracts)
-- AND t.ORDER_HOLD_ID = <ORDER_HOLD_ID>
-- AND t.LAST_UPDATE_DATE >= TIMESTAMP '<watermark>' -- WHO watermark, bulk-stamped by batch jobs; see quirks guide #who-columns
ORDER BY t.ORDER_HOLD_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_ORDER_HOLDS_ALL.HEADER_ID = OE_ORDER_HEADERS_ALL.HEADER_ID AND OE_ORDER_HOLDS_ALL.ORG_ID = OE_ORDER_HEADERS_ALL.ORG_IDON OE_ORDER_HOLDS_ALL.LINE_ID = OE_ORDER_LINES_ALL.LINE_ID AND OE_ORDER_HOLDS_ALL.ORG_ID = OE_ORDER_LINES_ALL.ORG_IDON OE_ORDER_HOLDS_ALL.HOLD_SOURCE_ID = OE_HOLD_SOURCES_ALL.HOLD_SOURCE_ID AND OE_ORDER_HOLDS_ALL.ORG_ID = OE_HOLD_SOURCES_ALL.ORG_ID
More Order Management tables
- 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
- OE_PRICE_ADJUSTMENTSPricing modifier applications — discounts, surcharges, and freight/special charges applied to an order or a line, with the modifier list that produced them and the monetary effect; the gap between list and selling price
- OE_TRANSACTION_TYPES_ALLOrder and line transaction types in one pool — each row defines a document type (distinguished order vs line by the type code) with its workflow binding, defaults, and accounting hooks; the decode for both ORDER_TYPE_ID and LINE_TYPE_ID
- OE_TRANSACTION_TYPES_TLTranslation companion for order/line transaction types — the display name and description per installed language; the only place the type name exists
- OE_DROP_SHIP_SOURCESThe 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