Results for “so_hold_sources_all”

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

Overview

SO_HOLD_SOURCES_ALL is an Oracle Order Entry (OE) transaction table that records the individual hold instances applied to sales orders and their related entities. While its ETRM description is terse — "Applied holds" — the object functions as the operational join point between a hold definition (the template describing why an order is held) and the specific business document that has been placed on hold (the order, customer, or site). Each row represents one applied hold, capturing who or what triggered it, when it was placed, and whether it has since been released.

The table resides in the OE schema and is a key component of the Order Management hold resolution workflow. Order Management applies holds during order import, order entry, or scheduled concurrent processing; SO_HOLD_SOURCES_ALL is the persistent record of those applications, and it is directly referenced by both the hold release and order hold interface tables. Because Order Management uses the "_ALL" suffix convention, the table is structured to support multiple operating units, with ORG_ID present among its 34 documented columns.

From a dimensional modeling perspective, the metadata's foreign key structure suggests a satellite-leaning classification: the table carries descriptive and status attributes about a hold application event and is anchored to hub-like entities such as SO_HOLDS, SO_HEADERS_ALL, and RA_CUSTOMERS. This is a modeling suggestion derived from the FK topology rather than a documented Data Vault design.

Key Information Stored

The surrogate primary key is HOLD_SOURCE_ID, enforced by the unique index SO_HOLD_SOURCS_PK and reinforced by the unique index SO_HOLD_SOURCES_U1 on the same column. The most significant content columns are:

• HOLD_ID — identifies the hold definition applied; foreign key to SO_HOLDS.
• HOLD_ENTITY_CODE / HOLD_ENTITY_ID — a polymorphic discriminator and identifier pair pointing to the entity placed on hold (order header, customer, or site).
• HOLD_UNTIL_DATE — the date through which the hold is intended to remain in force.
• RELEASED_FLAG — indicates whether the hold has been released.
• HOLD_RELEASE_ID — identifies the release record associated with a released hold.
• HOLD_COMMENT — free-form text describing the reason or context for the hold.
• ORG_ID — the operating unit under which the hold application was recorded.
• LAST_UPDATE_DATE, CREATION_DATE, LAST_UPDATED_BY, CREATED_BY, LAST_UPDATE_LOGIN — standard audit columns.
• PROGRAM_ID, PROGRAM_APPLICATION_ID, PROGRAM_UPDATE_DATE, REQUEST_ID — concurrent program and request traceability.
• CONTEXT and ATTRIBUTE1–ATTRIBUTE15 — the standard Oracle descriptive flexfield container.

Common Use Cases and Queries

Typical scenarios include determining why a specific order is blocked, auditing hold aging, and identifying holds eligible for automated release. A common query joins the applied hold to its definition and to the order header via the polymorphic entity columns:

SELECT hsh.hold_source_id, hsh.hold_id, hsh.hold_entity_id,
  hsh.hold_until_date, hsh.released_flag, hsh.hold_comment
FROM oe.so_hold_sources_all hsh, oe.so_holds sh
WHERE hsh.hold_id = sh.hold_id
  AND hsh.hold_entity_code = 'ORDER'
  AND hsh.released_flag = 'N';

Reports frequently aggregate open holds by HOLD_ID to measure operational impact, or filter on HOLD_UNTIL_DATE to find holds past their intended expiry. Because HOLD_ENTITY_ID is polymorphic, join logic must branch on HOLD_ENTITY_CODE to reach SO_HEADERS_ALL, RA_CUSTOMERS, or RA_SITE_USES_ALL. Audit and reconciliation queries use REQUEST_ID and PROGRAM_ID to trace holds placed by order import.

Related Objects

• SO_HOLDS — joined on SO_HOLD_SOURCES_ALL.HOLD_ID = SO_HOLDS.HOLD_ID; supplies hold definition and description.
• SO_HEADERS_ALL — joined on HOLD_ENTITY_ID when the held entity is an order header.
• RA_CUSTOMERS — joined on HOLD_ENTITY_ID for customer-level holds.
• RA_SITE_USES_ALL — joined on HOLD_ENTITY_ID for customer site-level holds.
• SO_HOLD_RELEASES — references SO_HOLD_SOURCES_ALL.HOLD_SOURCE_ID; records release actions against an applied hold.
• SO_ORDER_HOLDS_ALL — references SO_HOLD_SOURCES_ALL.HOLD_SOURCE_ID; the interface/processing table carrying hold data into Order Management.