Search Results oe_hold_authorizations




Overview
Explore in AI Chat

Overview

The OE_HOLD_AUTHORIZATIONS table is a core data structure within the Oracle E-Business Suite (EBS) Order Management module (ONT). Its primary function is to define and enforce the security model for order holds by storing the authorization rules that determine which users or responsibilities possess the authority to apply and release specific holds on sales orders. This table is essential for maintaining controlled business processes, ensuring that holds—which can stop order fulfillment for reasons like credit verification or fraud checks—are managed only by authorized personnel. It acts as the junction between hold definitions and the EBS security framework, enabling granular control over hold management within the application.

Key Information Stored

The table's structure links hold definitions to EBS security entities. While the full column list is not detailed in the provided metadata, the foreign key relationships reveal its critical components. The central column is HOLD_ID, which references OE_HOLD_DEFINITIONS to identify the specific hold type. Authorization is primarily granted based on EBS responsibilities, linked via the composite foreign key columns APPLICATION_ID and RESPONSIBILITY_ID to the FND_RESPONSIBILITY table. This design means that any user operating under a responsibility listed in this table for a given HOLD_ID is authorized to manage that hold. The table may also include columns for user-specific authorizations or other security attributes, but the documented model emphasizes responsibility-based control.

Common Use Cases and Queries

A primary use case is auditing security for hold management. Administrators can query which responsibilities can manage critical holds, such as credit holds. A typical query joins OE_HOLD_AUTHORIZATIONS with OE_HOLD_DEFINITIONS and FND_RESPONSIBILITY to produce a readable report. For example:

  • Identifying all authorizations for a specific hold: SELECT resp.responsibility_name, hld.name FROM oe_hold_authorizations auth, oe_hold_definitions hld, fnd_responsibility_vl resp WHERE auth.hold_id = hld.hold_id AND auth.application_id = resp.application_id AND auth.responsibility_id = resp.responsibility_id AND hld.name = 'Credit Hold';
  • During order processing, the application queries this table to validate if the current user's responsibility permits the release of an applied hold, a process integral to the "Release Holds" form and underlying APIs.

Related Objects

OE_HOLD_AUTHORIZATIONS has direct dependencies on several key EBS objects, as per the provided metadata. Its primary foreign key relationship is with OE_HOLD_DEFINITIONS (via HOLD_ID), the master table defining all available hold types. Its security model is tied to the core application foundation table FND_RESPONSIBILITY. In practice, it is also closely related to OE_ORDER_HOLDS, which stores the instances of holds applied to specific orders; the authorizations table governs who can create or remove those records. Key Order Management APIs and forms for hold management, such as the Order Organizer and the Release Holds interface, internally query this table to enforce business rules.