Search Results so_hold_sources_all




Overview
Explore in AI Chat

Overview

The SO_HOLD_SOURCES_ALL table is a core transactional table within the Oracle E-Business Suite Order Entry (OE) module. It serves as the central repository for recording the application of holds on sales orders and related entities. A hold is a business control mechanism that prevents further processing of an order, such as shipment or invoicing, until a specific condition is resolved. This table acts as the junction point, linking the definition of a hold (from SO_HOLDS) to the specific order, customer, or site where it has been applied. Its role is critical for maintaining order integrity, enforcing business rules, and providing an audit trail of all active and released holds within the system.

Key Information Stored

The table's primary function is to store the relationship between a hold and the entity it constrains. The most critical columns include HOLD_SOURCE_ID (the primary key uniquely identifying each hold application), HOLD_ID (a foreign key to SO_HOLDS defining the hold type and reason), and HOLD_ENTITY_ID (a foreign key identifying the specific record upon which the hold is placed). The HOLD_ENTITY_ID can reference different tables, most commonly SO_HEADERS_ALL for an entire sales order, RA_CUSTOMERS for a customer account, or RA_SITE_USES_ALL for a specific customer site. Additional columns typically track creation dates, the user who applied the hold, and context information for the hold's release criteria.

Common Use Cases and Queries

This table is essential for operational reporting and troubleshooting order fulfillment blocks. Common use cases include generating a list of all orders currently on hold, identifying which specific hold types are most frequently applied, and auditing hold release history. A fundamental query retrieves active holds for a given order by joining to the order headers and holds definition tables:

  • SELECT oh.hold_id, h.name, h.description FROM so_hold_sources_all oh, so_holds h WHERE oh.hold_id = h.hold_id AND oh.hold_entity_id = <header_id>;

Another critical pattern is analyzing holds by customer, joining to RA_CUSTOMERS via the HOLD_ENTITY_ID. Data from this table is also pivotal in custom workflows or alerts designed to notify personnel when key orders are placed on hold.

Related Objects

SO_HOLD_SOURCES_ALL maintains documented foreign key relationships with several key tables, as per the provided metadata. It is a central hub in the hold management schema:

  • SO_HOLDS: Joined via HOLD_ID. This is the master definition table for all possible hold types.
  • SO_HEADERS_ALL, RA_CUSTOMERS, RA_SITE_USES_ALL: Joined via HOLD_ENTITY_ID. These represent the entities (order, customer, site) to which a hold can be applied.
  • SO_HOLD_RELEASES: References SO_HOLD_SOURCES_ALL.HOLD_SOURCE_ID. This table logs the history of when and why holds were released.
  • SO_ORDER_HOLDS_ALL: References SO_HOLD_SOURCES_ALL.HOLD_SOURCE_ID. This table provides additional context and attributes for holds specifically placed on orders.