Results for “hold_until_date”

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

Overview

SO_ORDER_HOLDS_VIEW_HOLD_V is a denormalized reporting view owned by the APPS schema in Oracle E-Business Suite Release 12.1.1 and 12.2.2. It belongs to the Order Entry (OE) product family and consolidates order hold data drawn from the order holds, hold definitions, hold sources, hold releases, and user reference tables into a single queryable structure. Its principal role is to present a complete, human-readable picture of every hold applied to an order or order line, including the hold's name, the entity level at which it was applied, the associated entity identifier, the scheduled hold-until date, and the release history with the name of the releasing user. Because the view joins transactional hold records to their definitions and to FND_USER, it is well suited for operational reporting, order management dashboards, and integration extracts where a flattened hold record is preferable to navigating the normalized base tables. The view has a documented status of VALID and is registered in ETRM for both 12.1.1 and 12.2.2.

Underlying Base Objects

The view is defined over seven referenced objects. Six are synonyms within the APPS schema: FND_USER, SO_ACTIONS, SO_ENTITIES, SO_HOLDS, SO_HOLD_RELEASES, and SO_ORDER_HOLDS. The seventh, SO_HOLD_SOURCES, is itself a view rather than a base table. All joins except the one to SO_ORDER_HOLDS are outer joins (denoted by the (+) operator), so an order hold row is preserved even when its hold definition, source, entity, action, release, or user record is absent or has been purged. The relationship chain is anchored on SO_ORDER_HOLDS, which supplies the transaction-level hold instance. SO_HOLD_SOURCES connects the hold instance to its source through HOLD_SOURCE_ID, and SO_HOLDS supplies the hold name and action through the HOLD_ID carried on the source. SO_ENTITIES is joined twice — once aliased SE to resolve the hold level and once aliased SOENT to resolve the hold criteria. SO_HOLD_RELEASES and FND_USER provide release date and releaser identity, with the release join keyed on NVL(SOH.HOLD_RELEASE_ID, -1) to guarantee that unreleased holds still return a row.

Key Columns

• ORDER_HOLD_ID — Primary identifier of the hold instance, sourced from SO_ORDER_HOLDS.ORDER_HOLD_ID.
• NAME — The hold name from SO_HOLDS.
• CRITERIA — The hold criteria entity name, resolved from SO_ENTITIES via SOENT.
• HOLD_LEVEL — The entity level at which the hold applies (for example, order header or line), resolved from SO_ENTITIES via SE.
• ACTION — The hold action description from SO_ACTIONS.
• HOLD_UNTIL_DATE — The date through which the hold remains effective, from SO_HOLD_SOURCES.
• RELEASE_DATE — The creation date of the corresponding SO_HOLD_RELEASES record.
• RELEASER — The FND_USER.USER_NAME of the user who released the hold.
• LINE_ID and HEADER_ID — The order line and order header to which the hold instance belongs.
• HOLD_SOURCE_ID — Foreign key linking the hold instance to its hold source definition.
• HOLD_ENTITY_CODE and HOLD_ENTITY_ID — The entity type code and the identifier of the specific entity instance against which the hold was placed. HOLD_ENTITY_ID is the column most frequently used to trace a hold back to a particular header, line, or other business object.
• CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN — Standard audit columns from SO_ORDER_HOLDS.
• ROW_ID — The ROWID of the underlying SO_ORDER_HOLDS row, exposed for debugging and row-level identification.

Common Use Cases and Queries

The view is commonly used to report active and historical holds on orders, to identify holds requiring release, and to audit who released a hold and when. A typical query retrieving all holds for an order header is:

SELECT order_hold_id, name, hold_level, hold_entity_code, hold_entity_id, hold_until_date, release_date, releaser FROM so_order_holds_view_hold_v WHERE header_id = :p_header_id;

To find holds that remain unreleased, filter on a null release date:

SELECT order_hold_id, name, hold_entity_id, hold_until_date FROM so_order_holds_view_hold_v WHERE release_date IS NULL ORDER BY hold_until_date;

Because HOLD_ENTITY_ID is exposed directly alongside HOLD_ENTITY_CODE, the view supports joins back to order headers, lines, or other entities without additional lookups, making it a convenient source for hold-tracking extracts and exception reports.