Search Results oe_hold_sources_all




Overview
Explore in AI Chat

Overview

The OE_HOLD_SOURCES_ALL table is a core repository within Oracle E-Business Suite (EBS) Order Management (ONT) module, specifically for Release 12.1.1 and 12.2.2. It functions as the master definition table for the specific source criteria that trigger an order hold. A hold source defines the precise business entity, such as a customer, ship-to location, or internal organization, to which a particular hold definition is applied. This table is central to the hold management architecture, linking generic hold definitions to the concrete operational data that necessitates a hold. Its multi-org enabled structure, indicated by the "_ALL" suffix, allows it to store data for multiple operating units, making it a fundamental component for enforcing business controls across the enterprise.

Key Information Stored

The table's primary purpose is to map a hold definition to its applicable source entities. The most critical columns include HOLD_SOURCE_ID, which is the unique primary key identifier for each source record. The HOLD_ID column is a foreign key linking to OE_HOLD_DEFINITIONS, specifying which hold rule is being applied. The HOLD_ENTITY_ID column is a polymorphic foreign key that stores the identifier for the specific business entity that is the source of the hold; its meaning is contextual based on the entity type. This entity is linked to tables such as RA_CUSTOMERS (for a customer), RA_SITE_USES_ALL (for a ship-to or bill-to site), HR_ALL_ORGANIZATION_UNITS (for an internal organization), or OE_ORDER_HEADERS_ALL (for a specific order). Additional columns typically define the source type, active status, and creation/update metadata.

Common Use Cases and Queries

This table is essential for diagnosing hold-related issues, auditing hold configurations, and generating operational reports. A common scenario involves identifying all active holds applied to a specific customer. A sample query for this would join OE_HOLD_SOURCES_ALL to OE_HOLD_DEFINITIONS and filter by HOLD_ENTITY_ID corresponding to the customer in RA_CUSTOMERS. Another critical use case is analyzing the source criteria for a particular hold definition to understand its business scope. Developers and administrators also query this table when troubleshooting why an order entered a specific hold state, tracing from the order hold (OE_ORDER_HOLDS_ALL) back to its source definition. Reporting on hold coverage by entity type (e.g., customer vs. site) is another practical application.

Related Objects

OE_HOLD_SOURCES_ALL is a central hub within the hold subsystem, with key relationships to several other objects. Its primary foreign key relationship is with OE_HOLD_DEFINITIONS (via HOLD_ID), which stores the master hold rule. It is referenced as a parent table by OE_HOLD_RELEASES, which stores release criteria for holds, and by OE_ORDER_HOLDS_ALL, which records the specific instances of holds placed on orders. As indicated by the foreign key metadata, it links to numerous base tables to resolve the HOLD_ENTITY_ID, including RA_CUSTOMERS, RA_SITE_USES_ALL, HR_ALL_ORGANIZATION_UNITS, and OE_ORDER_HEADERS_ALL. This network of relationships underscores its role in connecting hold logic to transactional data.