Search Results oe_hold_releases




Overview
Explore in AI Chat

Overview

The OE_HOLD_RELEASES table is a core data repository within the Oracle E-Business Suite (EBS) Order Management (ONT) module. It serves the critical function of maintaining a historical audit trail for all hold release actions performed on sales orders. When a hold condition on an order line is resolved and the restriction is lifted, a record is created in this table. This provides a permanent, auditable log of who released a hold, when, and why, which is essential for compliance, troubleshooting, and process analysis. Its role is complementary to the OE_ORDER_HOLDS_ALL table, which stores active hold information.

Key Information Stored

The table's primary purpose is to capture the details of a release event. While the full column list is not detailed in the provided metadata, its structure is defined by key relationships. The primary key, HOLD_RELEASE_ID, uniquely identifies each release transaction. A critical foreign key, HOLD_SOURCE_ID, links back to the OE_HOLD_SOURCES_ALL table, which defines the original hold type (e.g., credit, shipping, custom). Other columns typically found in this table include the RELEASED_BY user ID, the RELEASE_DATE, and a RELEASE_COMMENT or REASON field documenting why the hold was removed. The relationship defined with OE_ORDER_HOLDS_ALL indicates this table stores the definitive release identifier for a hold record.

Common Use Cases and Queries

This table is central to operational reporting and audit inquiries. Common use cases include generating hold release history reports for specific orders or customers, analyzing hold resolution cycle times, and auditing user actions. A typical query would join OE_HOLD_RELEASES to OE_ORDER_HOLDS_ALL and OE_HOLD_SOURCES_ALL to get a complete picture.

  • Sample Query Pattern: To find all released holds for an order, including who released them and the hold type:
    SELECT ohr.release_date, ohr.released_by, ohsa.name AS hold_name
    FROM oe_hold_releases ohr,
    oe_order_holds_all ooha,
    oe_hold_sources_all ohsa
    WHERE ooha.header_id = :p_header_id
    AND ooha.hold_release_id = ohr.hold_release_id
    AND ohr.hold_source_id = ohsa.hold_source_id
    ORDER BY ohr.release_date DESC;
  • Data from this table is often leveraged in custom workflows or notifications to inform stakeholders when critical order holds are cleared.

Related Objects

OE_HOLD_RELEASES is a central node in the Order Management hold data model. Its primary relationships, as documented, are:

  • OE_ORDER_HOLDS_ALL: This table stores active and historical hold applications. Its HOLD_RELEASE_ID column is a foreign key referencing OE_HOLD_RELEASES.HOLD_RELEASE_ID, creating the definitive link between a hold and its release record.
  • OE_HOLD_SOURCES_ALL: This table defines the valid hold types (sources) in the system. The foreign key OE_HOLD_RELEASES.HOLD_SOURCE_ID references OE_HOLD_SOURCES_ALL.HOLD_SOURCE_ID, classifying the nature of the released hold.
  • While not explicitly listed in the metadata, this table is also intrinsically related to core order entities (OE_ORDER_HEADERS_ALL, OE_ORDER_LINES_ALL) through the OE_ORDER_HOLDS_ALL table, enabling analysis at the header, line, and hold source level.