EBS Reference

OE_HOLD_DEFINITIONS

Schema: ONTcontrol

Hold definitions — the named hold types (credit check, administrative…) with their workflow scope and effectivity; global seed data every hold instance resolves to

Module: Order ManagementNot org-partitioned

Notes

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

master: Data class: what the table holds — master data, transaction documents, control/configuration, interface/staging, or an APPS-schema view.

Fields

7 fields · 1 key

Table fields: position, field name, description, data type, and flags. 7 fields.
#	Field	Description	Type	Flags
1	HOLD_ID	Surrogate key of the hold definition	NUMBER	Key
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_DEFINITIONSon 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

CatalogSchemaHold definition IDwatermark

Include optional filters (2)

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

4 parameters not filled: <catalog>, <schema>, <HOLD_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_HOLD_SOURCES_ALLOE_HOLD_DEFINITIONSforeign key · N:1
ON OE_HOLD_SOURCES_ALL.HOLD_ID = OE_HOLD_DEFINITIONS.HOLD_ID

Browse more Order Managementtables →