Search Results so_hold_authorizations




Overview
Explore in AI Chat

Overview

The SO_HOLD_AUTHORIZATIONS table is a core data object within the Oracle E-Business Suite (EBS) Order Entry (OE) module. It functions as a security and authorization control table, defining which EBS responsibilities are permitted to release specific order holds. This table establishes a many-to-many relationship between holds defined in the system and the responsibilities authorized to manage them. Its role is critical for enforcing business rules and segregation of duties, ensuring that only users operating under the appropriate responsibility can authorize the release of holds placed on sales orders, thereby maintaining order integrity and control.

Key Information Stored

The table's structure is straightforward, consisting primarily of two foreign key columns that form its composite primary key. The HOLD_ID column links to the SO_HOLDS table, identifying the specific hold type or instance. The RESPONSIBILITY_ID column links to the FND_RESPONSIBILITY table, identifying the EBS responsibility granted the authority to release the linked hold. A third column, APPLICATION_ID, is also referenced in the foreign key relationship with FND_RESPONSIBILITY, ensuring the responsibility context is correctly scoped to its parent application. This minimal design efficiently maps authorization rights without redundant data.

Common Use Cases and Queries

The primary use case is to validate a user's privilege to release an order hold. When a user attempts to release a hold, the application checks this table for a record matching the hold and the user's current responsibility. Common queries involve auditing security setups and troubleshooting authorization issues. For example, to list all holds a specific responsibility can release:

  • SELECT h.HOLD_NAME FROM SO_HOLDS h, SO_HOLD_AUTHORIZATIONS a WHERE a.HOLD_ID = h.HOLD_ID AND a.RESPONSIBILITY_ID = 12345;

Conversely, to find all responsibilities authorized for a particular hold:

  • SELECT r.RESPONSIBILITY_NAME FROM FND_RESPONSIBILITY r, SO_HOLD_AUTHORIZATIONS a WHERE a.RESPONSIBILITY_ID = r.RESPONSIBILITY_ID AND a.HOLD_ID = 100;

Reporting often focuses on ensuring critical holds have appropriate authorization coverage.

Related Objects

SO_HOLD_AUTHORIZATIONS is centrally connected to two key tables via foreign key constraints. Its primary relationship is with SO_HOLDS (OE.SO_HOLDS), which stores the master definition of all order holds, such as credit or pricing holds. The second critical relationship is with FND_RESPONSIBILITY (APPLSYS.FND_RESPONSIBILITY), the core EBS table defining responsibilities and their associated menus and security contexts. Changes to holds or responsibilities are enforced through these relationships. This table is also integral to the underlying logic of the standard Order Management forms and APIs used for hold management.