Search Results hold_entity_id_value




Overview
Explore in AI Chat

Overview

APPS.OE_HOLD_SOURCES_V is a reporting and integration view in the Oracle Order Management module of Oracle E-Business Suite, available in releases 12.1.1 and 12.2.2. It exposes active hold source records — that is, holds that have been placed against order management entities but not yet released. The defining predicate hs.HOLD_RELEASE_ID IS NULL restricts the result set to currently effective holds, since released holds are recorded by the population of HOLD_RELEASE_ID. The view denormalizes several relationships so that consumers receive descriptive text alongside raw identifiers: the hold definition name, the holding user's name, and the translated meaning of the hold entity code. Because the search term "hold_entity_desc" corresponds directly to the lookup type used in the view's join to FND_LOOKUP_VALUES, this object is the standard source for resolving hold entity codes into user-facing descriptions.

Underlying Base Objects

The view is defined over the following documented base objects:

  • OE_HOLD_SOURCES (synonym) — the driving table, supplying hold source identifiers, hold entity codes and IDs, hold-until dates, release status, descriptive flexfield context and attributes, and organization context.
  • OE_HOLD_DEFINITIONS (synonym) — joined on HOLD_ID to supply the hold name, item type, and progress workflow flag.
  • FND_USER (synonym) — joined on CREATED_BY to supply USER_NAME of the creating user.
  • FND_LOOKUP_VALUES (synonym) — joined twice on lookup type 'HOLD_ENTITY_DESC' with VIEW_APPLICATION_ID 660 to decode HOLD_ENTITY_CODE and, optionally, HOLD_ENTITY_CODE2.
  • OE_HOLDS_PVT (package) — its entity_id_value function translates a hold entity code and ID pair into a displayable entity identifier value.
  • FND_GLOBAL (package) — supplies LANGUAGE and lookup security group context for the lookup joins.

The second lookup join and the HOLD_ENTITY_CODE2/HOLD_ENTITY_ID2/HOLD_ENTITY_ID2_VALUE columns are outer-joined, so records without a secondary entity still appear.

Key Columns

  • HOLD_SOURCE_ID — primary key of the hold source record.
  • HOLD_ID, NAME, ITEM_TYPE — the hold definition applied, its descriptive name, and its item type.
  • HOLD_ENTITY_CODE and MEANING — the coded entity type and its lookup meaning derived from lookup type HOLD_ENTITY_DESC.
  • HOLD_ENTITY_ID and HOLD_ENTITY_ID_VALUE — the entity identifier and its resolved display value, such as an order or line number.
  • HOLD_UNTIL_DATE, RELEASED_FLAG, HOLD_RELEASE_ID — scheduling and release state; RELEASED_FLAG and the null HOLD_RELEASE_ID filter define the active population.
  • HOLD_COMMENT, PROGRESS_WF_ON_RELEASE_FLAG — free-text rationale and whether workflow should proceed on release.
  • USER_NAME, CREATION_DATE, LAST_UPDATE_DATE — audit and ownership attributes.
  • ORG_ID — multi-org operating unit context; CONTEXT and ATTRIBUTE1–15 carry descriptive flexfield data.

Common Use Cases and Queries

Typical scenarios include hold exception reporting, order-to-cash blocking analysis, and integration feeds that must resolve entity codes to descriptive text. Because the view already joins the lookup table, consumers avoid re-implementing the HOLD_ENTITY_DESC resolution.

Listing active holds with readable entity descriptions:

SELECT hold_source_id, name, meaning hold_entity_desc,
       hold_entity_id_value, hold_until_date
FROM   apps.oe_hold_sources_v
WHERE  org_id = :p_org_id
ORDER  BY creation_date DESC;

Holds tied to a specific entity identifier value:

SELECT hold_source_id, name, meaning, hold_comment
FROM   apps.oe_hold_sources_v
WHERE  hold_entity_id_value = :p_order_number;

Grouping active holds by entity type for workload reporting:

SELECT meaning hold_entity_desc, COUNT(*) hold_count
FROM   apps.oe_hold_sources_v
GROUP  BY meaning;

In all cases the view returns only unreleased holds; historical or released holds must be queried from OE_HOLD_SOURCES directly.