Search Results so_order_holds_all




Overview
Explore in AI Chat

Overview

The SO_ORDER_HOLDS_ALL table is a core transactional table within the Oracle E-Business Suite (EBS) Order Entry (OE) module, specifically for releases 12.1.1 and 12.2.2. Its primary function is to record and manage all active holds placed on sales orders and individual order lines. A hold is a business control mechanism that prevents further processing of an order, such as shipping or invoicing, until a specific condition is resolved. This table acts as the central repository for tracking the existence, source, and status of these holds, ensuring order fulfillment adheres to defined business rules and validations.

Key Information Stored

The table's structure is designed to link a hold instance to the specific order entity and its source. The primary key, ORDER_HOLD_ID, uniquely identifies each hold record. The most critical foreign key columns are HEADER_ID and LINE_ID, which link the hold to a specific order in SO_HEADERS_ALL or a specific line in SO_LINES_ALL, respectively. A hold applied at the header level typically cascades to all lines. The HOLD_SOURCE_ID column references SO_HOLD_SOURCES_ALL, identifying the specific business rule or condition that triggered the hold (e.g., credit check failure, missing documentation). When a hold is released, the HOLD_RELEASE_ID column is populated with a reference to the SO_HOLD_RELEASES table, documenting the release action.

Common Use Cases and Queries

A primary use case is operational reporting to identify blocked orders. A common query involves joining to order headers and hold source descriptions to list all active holds. For example:

  • SELECT oha.order_number, hs.name AS hold_source, soha.creation_date FROM so_order_holds_all soha JOIN oe_order_headers_all oha ON soha.header_id = oha.header_id JOIN so_hold_sources_all hs ON soha.hold_source_id = hs.hold_source_id WHERE soha.hold_release_id IS NULL;

This identifies orders still on hold. Another critical use is during order management workflows, where applications check this table to determine if an order is eligible for progression to the next stage. Data from this table is also essential for auditing hold and release histories over time.

Related Objects

The SO_ORDER_HOLDS_ALL table maintains integral relationships with several key OE tables, as documented by its foreign keys:

  • SO_HEADERS_ALL: Joined via SO_ORDER_HOLDS_ALL.HEADER_ID. This links the hold to the sales order header.
  • SO_LINES_ALL: Joined via SO_ORDER_HOLDS_ALL.LINE_ID. This links the hold to a specific sales order line.
  • SO_HOLD_SOURCES_ALL: Joined via SO_ORDER_HOLDS_ALL.HOLD_SOURCE_ID. This provides the descriptive name and type of the applied hold.
  • SO_HOLD_RELEASES: Joined via SO_ORDER_HOLDS_ALL.HOLD_RELEASE_ID. This provides details on when and why a hold was removed.

The primary key constraint SO_ORDERS_HOLDS_PK on ORDER_HOLD_ID ensures the uniqueness of each hold record.