Results for “release_reason_code”

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

Overview

OE.SO_HOLD_RELEASES is an Order Entry module table that stores the release records associated with order holds in Oracle E-Business Suite Release 12.1.1 and 12.2.2. Where SO_ORDER_HOLDS_ALL captures the application of a hold against an order, line, or customer entity, SO_HOLD_RELEASES records the corresponding release action: the reason the hold was lifted, the source of the hold, the entity against which the release applies, and the free-text comment supplied by the user performing the release. Each row therefore represents a discrete hold-release event in the order lifecycle.

The table is owned by the OE schema and is documented with 31 columns. Its primary key, SO_HOLD_RELEASES_PK, is defined on the single surrogate column HOLD_RELEASE_ID, which is also enforced by the unique index SO_HOLD_RELEASES_U1. Mined from its foreign-key structure, the heuristic Data Vault classification for this object is satellite-leaning: the table behaves as a descriptive, keyed attribute store attached to hold and order entities rather than as an independent hub or a pure link. This classification should be treated as a modeling suggestion, not a documented physical property.

Key Information Stored

The most significant columns fall into three groups. The first group contains the surrogate and business-key identifiers. HOLD_RELEASE_ID is the surrogate primary key and the unique business-key candidate exposed through SO_HOLD_RELEASES_U1. HOLD_SOURCE_ID identifies which hold source generated the underlying hold, while HOLD_ENTITY_ID identifies the specific business entity (order header, customer, or site use) affected. HOLD_ENTITY_CODE qualifies that entity type.

The second group captures the release semantics. RELEASE_REASON_CODE holds the coded reason the hold was released, and RELEASE_COMMENT provides the accompanying free-text explanation entered by the releasing user. Together these columns are the primary analytical payload of the table.

The third group is the standard Oracle EBS "Who" audit and concurrent-program footprint: CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN, PROGRAM_APPLICATION_ID, PROGRAM_ID, PROGRAM_UPDATE_DATE, and REQUEST_ID. The fifteen ATTRIBUTE1 through ATTRIBUTE15 columns plus CONTEXT provide the standard extensible descriptive flexfield segment storage.

Common Use Cases and Queries

Typical scenarios include auditing which holds were released on a given order, analyzing release reasons by source or customer, and reconciling release history against the original hold records. A representative query joins releases back to the hold table through the shared HOLD_RELEASE_ID:

• SELECT r.HOLD_RELEASE_ID, r.RELEASE_REASON_CODE, r.RELEASE_COMMENT, r.CREATION_DATE FROM OE.SO_HOLD_RELEASES r WHERE r.HOLD_SOURCE_ID = :source_id;
• SELECT r.* FROM OE.SO_HOLD_RELEASES r, OE.SO_ORDER_HOLDS_ALL h WHERE r.HOLD_RELEASE_ID = h.HOLD_RELEASE_ID AND h.HEADER_ID = :order_id;
• Reporting on release volume by reason code and date using RELEASE_REASON_CODE and CREATION_DATE.
• Attributing releases to the concurrent program that processed them via PROGRAM_ID and REQUEST_ID.

Related Objects

The documented relationships center on the hold and entity model:

• SO_ORDER_HOLDS_ALL — references this table via HOLD_RELEASE_ID; the primary dependent child table.
• SO_HOLD_SOURCES_ALL — referenced by SO_HOLD_RELEASES.HOLD_SOURCE_ID; defines hold and release sources.
• SO_HEADERS_ALL — referenced by SO_HOLD_RELEASES.HOLD_ENTITY_ID when the hold entity is an order header.
• RA_CUSTOMERS — referenced by SO_HOLD_RELEASES.HOLD_ENTITY_ID for customer-level holds.
• RA_SITE_USES_ALL — referenced by SO_HOLD_RELEASES.HOLD_ENTITY_ID for site-use-level holds.

Because HOLD_ENTITY_ID is polymorphic across three foreign tables, joins must be conditioned on HOLD_ENTITY_CODE to resolve the correct parent.