Results for “hold_source_id”

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

Overview

OEBV_HOLD_RELEASES is a Business Intelligence System (BIS) base business view owned by the APPS schema in Oracle E-Business Suite, classified under the ONT – Order Management product family. It is documented with a status of VALID in both 12.1.1 and 12.2.2 and is explicitly described as the "Base BIS Business View for Order Hold Releases." Its purpose is to expose hold release activity recorded against order holds so that it can be consumed by Oracle Business Intelligence, Discoverer workbooks, custom reports, and integration extracts without requiring direct access to the underlying transactional table.

Consistent with the BIS view architecture, OEBV_HOLD_RELEASES is a thin, read-only projection over a single transactional entity. The view text concludes with the WITH READ ONLY clause, and Oracle's ETRM documentation lists OE_HOLD_RELEASES (accessed through a SYNONYM) as the only referenced base object. No joins, aggregations, or analytic functions are present; the view simply publishes the columns of the base table, supplemented by two metadata-driven derived columns that carry descriptive-flexfield and lookup semantics.

Underlying Base Objects

The view is defined directly over OE_HOLD_RELEASES, a synonym that resolves to the base hold release table in the Order Management schema. This is the table that stores a row each time a hold placed on an order, line, or fulfillment entity is released. Because the view is one-to-one with its base table, no row multiplication or loss occurs, and all standard audit and transactional columns pass through unchanged. The two derived columns in the projection are not physical columns at all but descriptive-flexfield placeholders: the literal _LA:RELEASE_REASON_CODE:OE_LOOKUPS:RELEASE_REASON:MEANING instructs the reporting layer to resolve the release reason code through the OE_LOOKUPS lookup type RELEASE_REASON and display the MEANING value, while the literal _DF:ONT:OE_HOLD_RELEASES:OE_HOLD_RELEASES marks the row as sourced from the OE_HOLD_RELEASES descriptive flexfield definition. Reporting tools that understand the BIS convention interpret these tokens at runtime.

Key Columns

• HOLD_RELEASE_ID – Primary identifier for each hold release record. It uniquely identifies a release event and serves as the safest join key to related Order Management tables.
• HOLD_SOURCE_ID – Identifier linking the release back to the originating hold source definition or hold instance, establishing the lineage between the hold that was applied and the release being recorded. This is the column most often used to trace which hold source generated a given release.
• RELEASE_COMMENTS – Free-text comments entered by the user at the time the hold was released. Note that the view text aliases this as RELEASE_COMMENT, while the documented column list shows RELEASE_COMMENTS; consumers should confirm the exposed alias in their environment.
• _LA:RELEASE_REASON – Derived lookup column resolving the release reason code to its meaning via the OE_LOOKUPS RELEASE_REASON lookup type.
• _DF – Descriptive flexfield reference column identifying the source context ONT:OE_HOLD_RELEASES.
• LAST_UPDATE_DATE, LAST_UPDATED_BY, CREATION_DATE, CREATED_BY – Standard EBS audit columns recording who created and last modified each release record and when, enabling incremental extraction and audit reporting.

Common Use Cases and Queries

The view is most commonly used to report hold release history, audit who released holds and why, and feed downstream reconciliation or SLA monitoring. A basic listing follows:

• Releases for a specific hold source: SELECT hold_release_id, hold_source_id, release_comments, creation_date FROM apps.oebv_hold_releases WHERE hold_source_id = :p_hold_source_id;
• Recent release activity within a date window: SELECT hold_release_id, hold_source_id, last_updated_by, last_update_date FROM apps.oebv_hold_releases WHERE last_update_date >= :p_from_date;
• Volume analysis by source: SELECT hold_source_id, COUNT(*) releases FROM apps.oebv_hold_releases GROUP BY hold_source_id ORDER BY releases DESC;

Because the view is read-only and unfiltered, apply all WHERE predicates in the calling query and use bind variables for the ID and date columns to preserve index usage on the base table. For descriptive-flexfield or lookup-meaning values, rely on the _DF and _LA columns rather than joining OE_LOOKUPS manually.