Search Results hold_entity_code

Overview

SO_HOLD_SOURCES is an Oracle E-Business Suite (EBS) view owned by the APPS schema and classified under the OE – Order Entry product family. It presents hold-related records that govern order holds and their releases, effectively exposing the hold source rows that drive the Order Management hold engine. In EBS 12.1.1 and 12.2.2 the view serves as the multi-org–secured reporting and integration surface over the underlying hold source table, allowing concurrent programs, forms, and custom code to query hold information filtered by the current operating unit context.

The view is frequently referenced by users searching for RELEASED_FLAG, because that column is the primary mechanism by which a hold is identified as either currently active or already released. Its presence in the view makes SO_HOLD_SOURCES a natural candidate for queries that distinguish open holds from released ones.

Underlying Base Objects

The documented referenced base object is SO_HOLD_SOURCES_ALL (accessed through a synonym). The view is defined with a SELECT statement that lists all significant columns from SO_HOLD_SOURCES_ALL and applies a WHERE clause using USERENV('CLIENT_INFO') to enforce org-level security, exactly mirroring the pattern used by other _ALL/_V multi-org views in the EBS data model.

The ORG_ID predicate compares the stored ORG_ID against the operating unit value parsed from the CLIENT_INFO session setting, defaulting to -99 when no value is present. This ensures that queries run under an initialized Order Management responsibility return only the hold source records belonging to the active operating unit, while still permitting access to org-independent rows where appropriate.

Key Columns

• HOLD_SOURCE_ID – Surrogate primary key identifying each hold source record.
• HOLD_ID – Foreign reference to the hold definition (from the hold codes setup) applied to the entity.
• HOLD_ENTITY_CODE / HOLD_ENTITY_ID – Identify the object the hold is placed against (for example, an order header or line) and its specific identifier.
• RELEASED_FLAG – Indicates whether the hold has been released. This is the column most commonly queried by users and is central to determining current hold status.
• HOLD_UNTIL_DATE – The date through which the hold remains in effect, where applicable.
• HOLD_RELEASE_ID – Reference to the release action associated with the hold source record.
• HOLD_COMMENT – Free-text comment describing the reason or notes for the hold.
• WHO columns – CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN for audit tracking.
• Concurrent program columns – PROGRAM_APPLICATION_ID, PROGRAM_ID, PROGRAM_UPDATE_DATE, REQUEST_ID for tracing batch processes.
• ORG_ID – Operating unit identifier used by the multi-org security predicate.
• CONTEXT and ATTRIBUTE1–ATTRIBUTE15 – Descriptive flexfield segments for extensibility.

Common Use Cases and Queries

The view is typically used to report on outstanding holds, to reconcile released versus active holds, and to feed integrations requiring hold status. A typical query filters on RELEASED_FLAG to isolate open holds:

• SELECT hold_source_id, hold_id, hold_entity_code, hold_entity_id, released_flag, hold_until_date FROM so_hold_sources WHERE NVL(released_flag,'N') = 'N';
• SELECT hold_entity_id, COUNT(*) FROM so_hold_sources WHERE released_flag = 'Y' GROUP BY hold_entity_id;

Because the view enforces org security through CLIENT_INFO, consumers should initialize the operating unit context (for example, via FND_GLOBAL.APPS_INITIALIZE) before querying, otherwise only rows matching the default -99 predicate are returned. This behavior is consistent across 12.1.1 and 12.2.2.