Results for “oe_hold_authorizations”

48 results




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

Overview

OE_HOLD_AUTHORIZATIONS is a transactional configuration table owned by the ONT schema within the Oracle Order Management module. In Oracle EBS 12.1.1 and 12.2.2, this table defines the security and authorization matrix that governs which responsibilities are permitted to apply holds to, or release holds from, sales orders and order lines. Each row represents a grant of authority: it binds a specific hold definition to a specific responsibility within an application, and constrains the action that responsibility is allowed to perform against that hold.

Functionally, the table acts as the bridge between hold definitions and the responsibilities authorized to act upon them. When a user attempts to apply or release a hold through the Order Management hold workflow, the application consults this table to confirm that the user's responsibility is authorized for the requested action. Absence of a matching row effectively denies the operation. Because it resolves a many-to-many relationship between holds and responsibilities, an entity-relationship analysis classifies OE_HOLD_AUTHORIZATIONS as a link (junction) table within a Data Vault modeling approach; this classification is a heuristic suggestion derived from its foreign key structure rather than a declarative attribute of the object.

The table carries 27 columns in the documented 12.2.2 physical schema, combining the business keys of the two related entities with an action qualifier and standard Oracle EBS audit and descriptive flexfield columns.

Key Information Stored

The most significant columns define the authorization grant and its lifecycle:

The documented metadata does not expose an explicit surrogate primary key column; the effective business key is the combination of HOLD_ID, RESPONSIBILITY_ID, APPLICATION_ID, and AUTHORIZED_ACTION_CODE, which together enforce uniqueness while the date-active columns control temporal validity.

Common Use Cases and Queries

Administrators and security analysts use this table to audit and troubleshoot hold authority configuration. A common diagnostic query determines which responsibilities may release a given hold:

  • Joining OE_HOLD_AUTHORIZATIONS to OE_HOLD_DEFINITIONS on HOLD_ID to report the hold name alongside each authorized responsibility.
  • Joining to FND_RESPONSIBILITY on APPLICATION_ID and RESPONSIBILITY_ID to resolve the responsibility name for user-facing reports.
  • Filtering on SYSDATE between START_DATE_ACTIVE and END_DATE_ACTIVE to list only currently effective authorizations.
  • Filtering on AUTHORIZED_ACTION_CODE to isolate apply versus release privileges for segregation-of-duties reviews.

Reporting scenarios include access-certification extracts, hold-authority matrix reports, and reconciliation of holds that failed to apply or release because no authorization row existed for the acting responsibility.

Related Objects

The following objects are most significant to OE_HOLD_AUTHORIZATIONS:

  • OE_HOLD_DEFINITIONS — referenced via HOLD_ID; defines the holds being authorized.
  • FND_RESPONSIBILITY — referenced via APPLICATION_ID and RESPONSIBILITY_ID; defines the responsibilities granted authority.
  • OE_ORDER_HOLDS — the transactional table holding actual hold instances whose apply/release actions are governed by these authorizations.
  • OE_HOLD_RELEASES — records hold release activity subject to release authority.
  • FND_APPLICATION — resolves the owning application of a responsibility.
  • OE_HOLDS — the operational hold view interface consumed by the Order Management hold workflow.