Results for “so_holds”

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

Overview

SO_HOLDS is the Order Entry (OE) reference table in Oracle E-Business Suite that defines the holds applied to sales orders, order lines, and related fulfillment entities. Owned by the OE schema, it stores the master definition of each hold — its name, type, effective dates, and the action to be triggered — rather than the individual hold instances placed against specific orders, which reside in the transactional hold application tables. In Oracle EBS 12.1.1 and 12.2.2 the table is documented as VALID with 28 columns and is classified by heuristic Data Vault analysis as hub-leaning: it functions as a business-concept hub keyed on a stable identifier, with its satellite-style attributes (descriptive and audit fields) attached directly rather than separated. This classification is a modeling suggestion for analytical or warehouse designs, not a physical EBS constraint.

Key Information Stored

The table's surrogate primary key is HOLD_ID, enforced by the SO_HOLDS_PK constraint. Two unique indexes act as business-key candidates: SO_HOLDS_U1 on HOLD_ID and SO_HOLDS_U2 on NAME, making NAME the meaningful, user-facing identifier referenced by setup and personalization. The most significant attributes are:

• NAME — the unique hold name presented in the Order Management hold setup and order screens.
• TYPE_CODE — classifies the hold, driving how the application applies and releases it.
• DESCRIPTION — free-text explanation of the hold's purpose.
• ACTION_ID — foreign key to SO_ACTIONS, defining the action executed when the hold is applied or released.
• START_DATE_ACTIVE and END_DATE_ACTIVE — the active date range controlling whether the hold can be placed.
• CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN — standard audit columns maintained by the EBS framework.
• CONTEXT and ATTRIBUTE1 through ATTRIBUTE15 — the Oracle Flexfield descriptive columns used for extensions and custom reporting.

Common Use Cases and Queries

Functional and technical users typically query SO_HOLDS to list active holds, resolve a hold name to its HOLD_ID, or report which action each hold triggers. A common pattern returns active holds with their action:

• SELECT h.hold_id, h.name, h.type_code, a.action_name FROM oe.so_holds h, oe.so_actions a WHERE h.action_id = a.action_id AND SYSDATE BETWEEN h.start_date_active AND NVL(h.end_date_active, SYSDATE + 1);
• Joining SO_HOLDS to SO_HOLD_AUTHORIZATIONS to report which users or roles may release a given hold.
• Joining to SO_HOLD_SOURCES_ALL to determine which hold sources (manual, credit check, pick confirmation, etc.) can apply each hold.
• Resolving a hold by business key: SELECT hold_id FROM oe.so_holds WHERE name = :hold_name;

These queries support hold setup validation, seeded-versus-custom hold auditing, and operational reporting on order flow blockages.

Related Objects

SO_HOLDS participates in a small but central relationship set within Order Management:

• SO_ACTIONS — referenced via SO_HOLDS.ACTION_ID; defines the action linked to each hold.
• SO_HOLD_AUTHORIZATIONS — references SO_HOLDS.HOLD_ID; controls who may release the hold.
• SO_HOLD_SOURCES_ALL — references SO_HOLDS.HOLD_ID; maps hold sources that may apply the hold.
• Transactional hold application tables in OE that reference holds by HOLD_ID when holds are placed against orders and lines.
• Order Management setup and hold release concurrent programs and forms that consume this definition table.