Results for “release_reason_code”

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

Overview

OE_HOLD_RELEASES is an Order Management (ONT) transactional table in the Oracle E-Business Suite 12.1.1 and 12.2.2 environments. It resides in the ONT schema and stores information about every hold that has been released against an order or order line. Because holds govern whether an order can progress to pick, ship, and invoice, this table provides the audit trail that answers when a hold was lifted, why it was released, by whom, and against which underlying hold source. The table is populated when a user manually releases a hold from the Order Management responsibility or when an automated concurrent program, workflow activity, or API call clears a hold. Under the heuristic Data Vault classification mined from its foreign-key structure, OE_HOLD_RELEASES is modeled as satellite-leaning. It is a descriptive, event-oriented record that extends the core hold and order entities rather than serving as an independent business hub. Each row captures one release event, so a single order hold may conceptually appear in more than one release record across its lifecycle. The table carries the standard 32-column EBS footprint, combining eleven WHO columns (including the multi-attribute flexfield pair CONTEXT and ATTRIBUTE1 through ATTRIBUTE15) with functional hold-release attributes.

Key Information Stored

The surrogate primary key is HOLD_RELEASE_ID, enforced by the OE_HOLD_RELEASES_PK constraint and the unique index OE_HOLD_RELEASES_U1. Functional columns of primary interest include:

• HOLD_SOURCE_ID — foreign key to OE_HOLD_SOURCES_ALL, identifying the hold source definition that was released.
• ORDER_HOLD_ID and RELEASED_ORDER_AMOUNT — the specific hold instance affected and the monetary amount released. RELEASED_ORDER_AMOUNT is meaningful for amount-based hold sources such as credit or past-due limits.
• RELEASED_CURR_CODE — the currency of RELEASED_ORDER_AMOUNT.
• RELEASE_REASON_CODE and RELEASE_COMMENT — the coded reason and free-text narrative for the release.
• CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN — the standard WHO audit columns identifying who released the hold and when.
• PROGRAM_APPLICATION_ID, PROGRAM_ID, PROGRAM_UPDATE_DATE, REQUEST_ID — the concurrent program context, indicating whether the release was manual or driven by a concurrent request.
• CONTEXT and ATTRIBUTE1 through ATTRIBUTE15 — the descriptive flexfield segments, available for customer-specific extensions.

ORDER_HOLD_ID and HOLD_SOURCE_ID act as the de facto business keys linking a release back to the hold definition and hold instance; HOLD_RELEASE_ID remains the technical surrogate.

Common Use Cases and Queries

Typical uses include hold-release audit reporting, credit-management analysis, and root-cause investigation of why an order shipped or was invoiced after a hold. A representative query joining to the hold instance and source is:

• SELECT r.HOLD_RELEASE_ID, h.ORDER_HOLD_ID, s.NAME, r.RELEASE_REASON_CODE, r.RELEASE_COMMENT, r.CREATION_DATE, r.CREATED_BY FROM OE_HOLD_RELEASES r, OE_ORDER_HOLDS_ALL h, OE_HOLD_SOURCES_ALL s WHERE r.ORDER_HOLD_ID = h.ORDER_HOLD_ID AND r.HOLD_SOURCE_ID = s.HOLD_SOURCE_ID.
• Releases summarized by reason code for a period: GROUP BY RELEASE_REASON_CODE, filtering on CREATION_DATE.
• Amount-based analysis of released credit holds using SUM(RELEASED_ORDER_AMOUNT) grouped by RELEASED_CURR_CODE.
• Automated-versus-manual release analysis by examining REQUEST_ID and PROGRAM_ID.

Related Objects

• OE_ORDER_HOLDS_ALL — holds the active hold instances; its HOLD_RELEASE_ID column references OE_HOLD_RELEASES, making this the principal child/association table.
• OE_HOLD_SOURCES_ALL — referenced via HOLD_SOURCE_ID, supplying the hold source definition metadata.
• OE_ORDER_HEADERS_ALL and OE_ORDER_LINES_ALL — order entities linked through the hold instance.
• OE_HOLDS / OE_HOLD_DEFINITIONS — hold setup and definition views.
• ONT Order Management APIs such as OE_HOLDS_PUB / OE_ORDER_PUB, which release holds programmatically and write these rows.
• Hold Release and Order Management concurrent programs that populate REQUEST_ID.