Results for “held_by”

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

Overview

OE_HOLD_SOURCES_V is a seeded Oracle E-Business Suite view owned by the APPS schema and delivered with the Order Management (ONT) product family. Its stated purpose is to support the Holds form, where it displays all hold sources applied to order management entities. In EBS 12.1.1 and 12.2.2 the view is a denormalized, presentation-oriented projection over OE_HOLD_SOURCES, enriched with descriptive names and lookup meanings so that end users and downstream reports do not need to resolve foreign keys manually. The view carries status VALID in the ETRM reference for 12.2.2.

Because it exposes release status, hold definitions, and both primary and secondary hold entity attributions, OE_HOLD_SOURCES_V is frequently used as a reporting and integration surface for order holds — for example, feeding operational dashboards or interfaces that must identify which hold is active on an order, line, or fulfillment entity.

Underlying Base Objects

The view text joins OE_HOLD_SOURCES (HS) to several supporting objects:

• OE_HOLD_SOURCES — the primary transactional table storing each hold instance, its entity attribution, release flags, and descriptive flexfield columns.
• OE_HOLD_DEFINITIONS — joined on HOLD_ID to supply the hold name (HD.NAME as HOLD_NA in the column list).
• FND_USER — joined on CREATED_BY to resolve the user who applied the hold; exposed as USER_NAME and surfaced as HELD_BY.
• FND_LOOKUP_VALUES — joined twice against lookup type HOLD_ENTITY_DESC with VIEW_APPLICATION_ID = 660, using FND_GLOBAL.LOOKUP_SECURITY_GROUP for language- and security-aware lookup resolution. FLV translates HOLD_ENTITY_CODE; FLV2 (outer-joined) translates HOLD_ENTITY_CODE2.
• OE_HOLDS_PVT — a PL/SQL package whose ENTITY_ID_VALUE function derives a displayable identifier for an entity code/ID pair; invoked for both the primary and secondary entity.
• FND_GLOBAL — used within the lookup security-group calls.

Note that the view restricts output with HS.HOLD_RELEASE_ID IS NULL, so released hold sources are excluded from the result set.

Key Columns

• HOLD_SOURCE_ID — primary key of the underlying hold source record.
• HOLD_ID / HOLD_NA — identifier and name of the hold definition being applied.
• HOLD_ENTITY_CODE — code of the primary entity the hold is placed against; FLV.MEANING provides its translated description.
• HOLD_ENTITY_ID / HOLD_ENTITY_ID_VALUE — raw entity identifier and its derived display value from OE_HOLDS_PVT.ENTITY_ID_VALUE.
• HOLD_ENTITY_CODE2 / HOLD_ENTITY_ID2 / HOLD_ENTITY_ID2_VALUE — the secondary entity attribution, resolved through the outer-joined FLV2 lookup. This is the column family users locate when searching for hold_entity_code2.
• HELD_BY — the user name of the person who created the hold.
• HOLD_UNTIL_DATE — the date through which the hold remains effective.
• RELEASED_FLAG — indicates release state; combined with the HOLD_RELEASE_ID filter this governs visibility.
• HOLD_COMMENT — free-text rationale entered when the hold was applied.
• ORG_ID — operating unit context.
• ATTRIBUTE1–ATTRIBUTE15, CONTEXT — descriptive flexfield columns carried through from the base table.
• Audit columns — CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN, PROGRAM_APPLICATION_ID, PROGRAM_ID, PROGRAM_UPDATE_DATE, REQUEST_ID.

Common Use Cases and Queries

Typical scenarios include identifying all active holds on a specific order or line, reporting on holds by definition name or entity, and exposing both the primary and secondary entity attributions for integration.

List active holds with resolved entity meanings:

SELECT hold_source_id, hold_na, held_by,
       hold_entity_code, hold_entity_id_value,
       hold_entity_code2, hold_entity_id2_value,
       hold_until_date, hold_comment
FROM   apps.oe_hold_sources_v
WHERE  org_id = :p_org_id;

Retrieve the secondary entity description for a given order:

SELECT hold_source_id, hold_na,
       hold_entity_code2, hold_entity_id2_value
FROM   apps.oe_hold_sources_v
WHERE  hold_entity_code  = 'ORDER'
AND    hold_entity_id    = :p_header_id;

Aggregate hold counts by definition:

SELECT hold_na, COUNT(*)
FROM   apps.oe_hold_sources_v
GROUP  BY hold_na
ORDER  BY 2 DESC;