Skip to content
EBS Reference

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

Module: Order ManagementOperating-unit striped (ORG_ID)
Notes

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
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

8 fields · 1 key

Table fields: position, field name, description, data type, and flags. 8 fields.
#FieldDescriptionTypeFlags
1HOLD_SOURCE_IDSurrogate key of the hold sourceNUMBER
Key
2ORG_IDOperating unitNUMBER
3HOLD_IDThe hold definition being appliedNUMBER
4HOLD_ENTITY_CODEWhat kind of entity is held — customer, order, item, warehouse…VARCHAR2
5HOLD_ENTITY_IDThe held entity's id — stored as text whatever the entity; cast before numeric joinsVARCHAR2
6HOLD_UNTIL_DATEAutomatic expiry date of the hold, when setDATE
7RELEASED_FLAGN while the source still applies its holdVARCHAR2
8HOLD_RELEASE_IDThe release record for the whole source, once releasedNUMBER

Field provenance: hand-curated. 1 key field.

Boilerplate SQL

Starting point for reading OE_HOLD_SOURCES_ALLon 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_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;

5 parameters not filled: <catalog>, <schema>, <operating_unit_id>, <HOLD_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_ORDER_HOLDS_ALLOE_HOLD_SOURCES_ALLforeign key · N:1
    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_ID
  • OE_HOLD_SOURCES_ALLOE_HOLD_DEFINITIONSforeign key · N:1
    ON OE_HOLD_SOURCES_ALL.HOLD_ID = OE_HOLD_DEFINITIONS.HOLD_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.