Skip to content
Fusion Reference

DOO_HOLD_INSTANCES

Product: DOOtransaction

Hold instances — one row per hold applied to an orchestration order, order line, or fulfillment line, with who applied and released it and when; the "why isn't this line shipping" table

Notes

The parent pointers are prefixed DOO_ here — DOO_HEADER_ID and DOO_LINE_ID, unlike every sibling table — plus FULFILL_LINE_ID; which one is populated depends on the level the hold targets. Active holds are ACTIVE_FLAG = 'Y' with RELEASE_DATE null; released holds remain as history. Hold definitions live in DOO_HOLD_CODES_B (not yet cataloged).

What the badges mean
master
Data class: what the table holds — master data, transaction documents, control/configuration, interface/staging, or a documented view.
In field listings, K marks a primary-key field.

Extract access

The delivered surfaces that reach this table — the BICC extract data store (PVO) for bulk extraction and the OTBI subject areas for real-time queries. There is no SQL path to the SaaS database.

  • FscmTopModelAM.ScmExtractAM.DooBiccExtractAM.HoldInstanceExtractPVO
    OTBI: Order Management - Order Holds Real Time

    Hold Instances data store — keyed on HoldInstanceHoldInstanceId, mirroring HOLD_INSTANCE_ID. Hold-code definitions ride the companion HoldCodeExtractPVO / HoldCodeTLExtractPVO stores.

    Oracle data-store documentation →

Fields

13 fields · 1 key

Table fields: position, field name, description, data type, and flags. 13 fields.
#FieldDescriptionTypeFlags
1HOLD_INSTANCE_IDSurrogate key of the hold instanceNUMBER
Key
2HOLD_CODE_IDThe hold-code definition this instance appliesNUMBER
3DOO_HEADER_IDOrder header the hold targets — note the DOO_ prefix, unlike sibling tablesNUMBER
4DOO_LINE_IDOrder line the hold targetsNUMBER
5FULFILL_LINE_IDFulfillment line the hold targetsNUMBER
6ACTIVE_FLAGWhether the hold is currently active — released holds remain as historyVARCHAR2
7APPLY_DATEWhen the hold was placedDATE
Filter date
8RELEASE_DATEWhen the hold was released — NULL while activeDATE
9APPLY_USER_IDUser who requested the holdVARCHAR2
10RELEASE_USER_IDUser who released the holdVARCHAR2
11APPLY_SYSTEMSystem that requested the holdVARCHAR2
12HOLD_RELEASE_REASON_CODEReason code recorded at releaseVARCHAR2
13HOLD_COMMENTSComments entered when applying the holdVARCHAR2

Field provenance: hand-curated. 1 key field.

Boilerplate SQL

Starting point for reading the BICC-landed copy of DOO_HOLD_INSTANCESon Databricks — real DATE columns need no conversion, and the org anchor and the LAST_UPDATE_DATE watermark (the column incremental BICC extracts key on) 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  : DOO_HOLD_INSTANCES — Hold instances — one row per hold applied to an orchestration order, order line, or fulfillment line, with who applied and released it and when; the "why isn't this line shipping" table
-- Purpose: Column-selected read of DOO_HOLD_INSTANCES — auto-generated from field metadata
-- Grain  : One row per HOLD_INSTANCE_ID
-- Notes  : Auto-generated skeleton for Oracle Fusion Cloud data landed in your lakehouse by a BICC extract — there is no SQL path to the SaaS database. Column names follow Oracle's table documentation — if your landed data still carries PVO attribute headers, map names first; see quirks #pvo-drift. 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_INSTANCE_ID AS "Surrogate key of the hold instance",
  t.HOLD_CODE_ID AS "The hold-code definition this instance applies",
  t.DOO_HEADER_ID AS "Order header the hold targets — note the DOO_ prefix, unlike sibling tables",
  t.DOO_LINE_ID AS "Order line the hold targets",
  t.FULFILL_LINE_ID AS "Fulfillment line the hold targets",
  t.ACTIVE_FLAG AS "Whether the hold is currently active — released holds remain as history",
  t.APPLY_DATE AS "When the hold was placed",
  t.RELEASE_DATE AS "When the hold was released — NULL while active",
  t.APPLY_USER_ID AS "User who requested the hold",
  t.RELEASE_USER_ID AS "User who released the hold",
  t.APPLY_SYSTEM AS "System that requested the hold",
  t.HOLD_RELEASE_REASON_CODE AS "Reason code recorded at release",
  t.HOLD_COMMENTS AS "Comments entered when applying the hold"
FROM <catalog>.<schema>.DOO_HOLD_INSTANCES t
WHERE
  1 = 1  -- no partition column on this table; the filters below are optional
  -- AND t.HOLD_INSTANCE_ID = <HOLD_INSTANCE_ID>
  -- AND t.APPLY_DATE >= DATE '<DATE_FROM>'
  -- AND t.APPLY_DATE <= DATE '<DATE_TO>'
  -- AND t.LAST_UPDATE_DATE >= TIMESTAMP '<watermark>'  -- the column incremental BICC extracts key on
ORDER BY t.HOLD_INSTANCE_ID;

6 parameters not filled: <catalog>, <schema>, <HOLD_INSTANCE_ID>, <DATE_FROM>, <DATE_TO>, <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

  • DOO_HOLD_INSTANCESDOO_HEADERS_ALLforeign key · N:1
    ON DOO_HOLD_INSTANCES.DOO_HEADER_ID = DOO_HEADERS_ALL.HEADER_ID
  • DOO_HOLD_INSTANCESDOO_LINES_ALLforeign key · N:1
    ON DOO_HOLD_INSTANCES.DOO_LINE_ID = DOO_LINES_ALL.LINE_ID
  • DOO_HOLD_INSTANCESDOO_FULFILL_LINES_ALLforeign key · N:1
    ON DOO_HOLD_INSTANCES.FULFILL_LINE_ID = DOO_FULFILL_LINES_ALL.FULFILL_LINE_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 Fusion Cloud Applications are registered trademarks of Oracle and/or its affiliates.