OE_HOLD_DEFINITIONS
Schema: ONTcontrolHold definitions — the named hold types (credit check, administrative…) with their workflow scope and effectivity; global seed data every hold instance resolves to
Not operating-unit striped — definitions are global; the striping lives on the hold instances and sources. The NAME is stored directly here (no translation companion).
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
7 fields · 1 key
7 fields.
| # | Field | Description | Type | Flags |
|---|---|---|---|---|
| 1 | HOLD_ID | Surrogate key of the hold definition | NUMBER | Primary-key field |
| 2 | NAME | The hold's name — stored directly here, no translation companion | VARCHAR2 | |
| 3 | TYPE_CODE | Hold type classification code | VARCHAR2 | |
| 4 | ITEM_TYPE | Workflow item type the hold applies to, when workflow-scoped | VARCHAR2 | |
| 5 | ACTIVITY_NAME | Workflow activity the hold stops at, when workflow-scoped | VARCHAR2 | |
| 6 | START_DATE_ACTIVE | Effectivity start date | DATE | |
| 7 | END_DATE_ACTIVE | Effectivity end date — NULL while active | DATE |
Field provenance: hand-curated. 1 key field.
Boilerplate SQL
Starting point for reading OE_HOLD_DEFINITIONS 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.
4 parameters not filled: <catalog>, <schema>, <HOLD_ID>, <watermark>
-- ============================================================
-- Table : OE_HOLD_DEFINITIONS — Hold definitions — the named hold types (credit check, administrative…) with their workflow scope and effectivity; global seed data every hold instance resolves to
-- Purpose: Column-selected read of OE_HOLD_DEFINITIONS — auto-generated from field metadata
-- Grain : One row per 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.HOLD_ID AS "Surrogate key of the hold definition",
t.NAME AS "The hold's name — stored directly here, no translation companion",
t.TYPE_CODE AS "Hold type classification code",
t.ITEM_TYPE AS "Workflow item type the hold applies to, when workflow-scoped",
t.ACTIVITY_NAME AS "Workflow activity the hold stops at, when workflow-scoped",
t.START_DATE_ACTIVE AS "Effectivity start date",
t.END_DATE_ACTIVE AS "Effectivity end date — NULL while active"
FROM <catalog>.<schema>.OE_HOLD_DEFINITIONS t
WHERE
1 = 1 -- no partition column on this table; the filters below are optional
-- AND t.HOLD_ID = <HOLD_ID>
-- AND t.LAST_UPDATE_DATE >= TIMESTAMP '<watermark>' -- WHO watermark, bulk-stamped by batch jobs; see quirks guide #who-columns
ORDER BY t.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_HOLD_SOURCES_ALL.HOLD_ID = OE_HOLD_DEFINITIONS.HOLD_ID
More Order Management tables
- 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
- 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