Results for “hold_until_date”

AI-generated from documented ETRM metadata — verify critical details on the linked pages.

Overview

The OE_HOLD_SOURCES_ALL table, owned by the ONT (Order Management) schema, stores the criteria that define order hold sources in Oracle E-Business Suite Release 12.1.1 and 12.2.2. A hold source represents a specific combination of hold definition, entity, and scope that, when matched against an order, places the order or its lines on hold automatically. Each row describes a targeting rule that Oracle Order Management evaluates against eligible orders, so this table sits at the center of the automated order-holding and release framework.

From a Data Vault modeling perspective, the heuristic classification for this table is satellite-leaning. It extends the core hold definition with descriptive context (entity code, entity identifier, effective dates, release state), which is characteristic of a satellite attached to a hub-and-link structure. Analysts constructing a warehouse model should treat OE_HOLD_SOURCES_ALL as an attribute-bearing satellite rather than as a pure transactional hub or a relationship link.

Key Information Stored

The table contains 36 columns. The surrogate primary key is HOLD_SOURCE_ID, defined by the unique index OE_HOLD_SOURCES_ALL_PK. The single-column unique index OE_HOLD_SOURCES_U1 also enforces uniqueness on HOLD_SOURCE_ID, confirming it as the sole business-key candidate. The most significant columns include:

• HOLD_SOURCE_ID – Surrogate primary key uniquely identifying each hold source record.
• HOLD_ID – Foreign key to OE_HOLD_DEFINITIONS, linking the source to the hold type it applies.
• HOLD_ENTITY_CODE / HOLD_ENTITY_CODE2 – Codes indicating the entity type targeted by the source (for example, customer, site, organization, or order).
• HOLD_ENTITY_ID / HOLD_ENTITY_ID2 – Identifiers of the targeted entity; the FK metadata indicates these resolve to RA_CUSTOMERS, RA_SITE_USES_ALL, HR_ALL_ORGANIZATION_UNITS, or OE_ORDER_HEADERS_ALL depending on the entity code.
• HOLD_UNTIL_DATE – Effective end date for the hold source, supporting time-bounded holds.
• RELEASED_FLAG – Indicates whether the hold source has been released.
• HOLD_COMMENT – Free-text note describing the purpose of the source.
• HOLD_RELEASE_ID – References the release associated with this source.
• ORG_ID – Operating unit that owns the hold source, enabling multi-org security.
• Who-columns and audit fields – CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN, PROGRAM_ID, REQUEST_ID, and PROGRAM_UPDATE_DATE.
• CONTEXT and ATTRIBUTE1–ATTRIBUTE15 – Descriptive flexfield columns for customer-defined extensions.

Common Use Cases and Queries

Order management teams use this table to audit which hold sources exist, to identify sources targeting a particular customer or operating unit, and to trace why an order was placed on hold. A common query joins hold sources to hold definitions:

SELECT hs.HOLD_SOURCE_ID, hd.NAME, hs.HOLD_ENTITY_CODE, hs.HOLD_ENTITY_ID, hs.HOLD_UNTIL_DATE, hs.RELEASED_FLAG FROM ONT.OE_HOLD_SOURCES_ALL hs, ONT.OE_HOLD_DEFINITIONS hd WHERE hs.HOLD_ID = hd.HOLD_ID AND hs.ORG_ID = :p_org_id;

Analysts correlate active sources against OE_ORDER_HOLDS_ALL to measure how often each source has triggered. Reports commonly filter on RELEASED_FLAG and HOLD_UNTIL_DATE to distinguish open sources from expired or released ones, and the ATTRIBUTE columns support custom reporting when the flexfield context is populated.

Related Objects

The following objects are most tightly coupled to OE_HOLD_SOURCES_ALL through documented primary-key/foreign-key relationships:

• OE_HOLD_DEFINITIONS – Referenced by OE_HOLD_SOURCES_ALL.HOLD_ID; defines the hold type each source applies.
• OE_ORDER_HOLDS_ALL – References this table via HOLD_SOURCE_ID; contains the actual holds placed on orders and lines.
• OE_HOLD_RELEASES – References this table via HOLD_SOURCE_ID; records releases associated with the source.
• RA_CUSTOMERS – Resolved through HOLD_ENTITY_ID when the entity code targets a customer.
• RA_SITE_USES_ALL – Resolved through HOLD_ENTITY_ID when the entity code targets a customer site.
• HR_ALL_ORGANIZATION_UNITS – Resolved through HOLD_ENTITY_ID when the entity code targets an organization.
• OE_ORDER_HEADERS_ALL – Resolved through HOLD_ENTITY_ID when the entity code targets a specific order.