OE_HOLD_SOURCES_ALL
Schema: ONTtransactionOU-striped (ORG_ID)Hold 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
HOLD_ENTITY_ID is a VARCHAR2(250) holding whatever id HOLD_ENTITY_CODE names — cast before joining it to numeric keys.
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 | HOLD_SOURCE_ID | Surrogate key of the hold source | NUMBER | Primary-key field |
| 2 | ORG_ID | Operating unit | NUMBER | |
| 3 | HOLD_ID | The hold definition being applied | NUMBER | |
| 4 | HOLD_ENTITY_CODE | What kind of entity is held — customer, order, item, warehouse… | VARCHAR2 | |
| 5 | HOLD_ENTITY_ID | The held entity's id — stored as text whatever the entity; cast before numeric joins | VARCHAR2 | |
| 6 | HOLD_UNTIL_DATE | Automatic expiry date of the hold, when set | DATE | |
| 7 | RELEASED_FLAG | N while the source still applies its hold | VARCHAR2 | |
| 8 | HOLD_RELEASE_ID | The release record for the whole source, once released | NUMBER |
Field provenance: hand-curated. 1 key field.
Boilerplate SQL
Starting point for reading OE_HOLD_SOURCES_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>, <HOLD_SOURCE_ID>, <watermark>
-- ============================================================
-- Table : OE_HOLD_SOURCES_ALL — Hold 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
-- Purpose: Column-selected read of OE_HOLD_SOURCES_ALL — auto-generated from field metadata
-- Grain : One row per operating unit (ORG_ID) + HOLD_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.HOLD_SOURCE_ID AS "Surrogate key of the hold source",
t.ORG_ID AS "Operating unit",
t.HOLD_ID AS "The hold definition being applied",
t.HOLD_ENTITY_CODE AS "What kind of entity is held — customer, order, item, warehouse…",
t.HOLD_ENTITY_ID AS "The held entity's id — stored as text whatever the entity; cast before numeric joins",
t.HOLD_UNTIL_DATE AS "Automatic expiry date of the hold, when set",
t.RELEASED_FLAG AS "N while the source still applies its hold",
t.HOLD_RELEASE_ID AS "The release record for the whole source, once released"
FROM <catalog>.<schema>.OE_HOLD_SOURCES_ALL t
WHERE
t.ORG_ID = <operating_unit_id> -- operating unit (MOAC does not filter extracts)
-- AND t.HOLD_SOURCE_ID = <HOLD_SOURCE_ID>
-- AND t.LAST_UPDATE_DATE >= TIMESTAMP '<watermark>' -- WHO watermark, bulk-stamped by batch jobs; see quirks guide #who-columns
ORDER BY t.HOLD_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_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_IDON OE_HOLD_SOURCES_ALL.HOLD_ID = OE_HOLD_DEFINITIONS.HOLD_ID
More Order Management tables
- 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
- 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