Results for “so_hold_authorizations”

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

Overview

OE.SO_HOLD_AUTHORIZATIONS is a transactional configuration table in the Oracle Order Entry (OE) module of Oracle E-Business Suite, present in both 12.1.1 and 12.2.2. Its documented purpose is to store hold responsibility information — that is, the mapping of which Oracle EBS responsibilities are permitted to apply, release, or otherwise act upon a specific order hold. In effect, it answers the operational question: "Who is authorized to place or remove this hold?"

Order holds in EBS are defined in SO_HOLDS (and its language table SO_HOLDS_TL), but a hold definition alone does not determine who may manipulate it. The authorization grid is captured separately in SO_HOLD_AUTHORIZATIONS, which links a hold to one or more responsibilities. This separation allows the same hold to be governed by different responsibility profiles across organizations or business units.

The record set is small and highly stable; it is configuration-oriented rather than high-volume transaction data. From a Data Vault modeling perspective — a heuristic classification mined from the foreign-key structure — this table is best characterized as a link, since it resolves a many-to-many relationship between SO_HOLDS and FND_RESPONSIBILITY. It carries a composite primary key rather than a single surrogate, which reinforces the link interpretation.

Key Information Stored

The physical schema defines 27 columns in the OE schema, but the semantically significant ones are few. The composite primary key, SO_HOLD_AUTHORIZATIONS_PK, is formed by HOLD_ID and RESPONSIBILITY_ID — these two columns together constitute the business key and uniquely identify a row.

• HOLD_ID — Foreign key to SO_HOLDS. Identifies the hold definition being authorized.
• RESPONSIBILITY_ID — Foreign key to FND_RESPONSIBILITY. Identifies the responsibility granted authority over the hold.
• APPLICATION_ID — The application owning the responsibility; part of the FND_RESPONSIBILITY lookup context.
• AUTHORIZED_ACTION_CODE — Indicates the action the responsibility is permitted to perform (for example, apply versus release).
• START_DATE_ACTIVE / END_DATE_ACTIVE — Date-range columns controlling when the authorization is in force; a standard EBS pattern for time-bounded configuration.
• CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN — Standard EBS WHO columns recording audit history.
• CONTEXT and ATTRIBUTE1–ATTRIBUTE15 — The standard EBS descriptive flexfield (DFF) container, available for customer-specific extensions.

The key point: the surrogate is composite. Any query joining to this table must supply both HOLD_ID and RESPONSIBILITY_ID to resolve a unique row.

Common Use Cases and Queries

The most common operational need is security auditing: determining which responsibility can release a given hold. A representative query joining to the hold language table is:

SELECT sh.name, fr.responsibility_name, sha.authorized_action_code
FROM oe.so_hold_authorizations sha,
oe.so_holds_tl sh,
fnd_responsibility_vl fr
WHERE sha.hold_id = sh.hold_id
AND sha.responsibility_id = fr.responsibility_id
AND sh.language = USERENV('LANG');

Another frequent scenario is troubleshooting "why can't this user release the order?" — the answer typically lies in a missing row in this table for the user's responsibility. Reverse lookups (all holds a responsibility may act upon) follow the same join pattern with the predicates reversed.

Reporting use cases include documenting the hold authorization matrix for SOX compliance, validating that date-active ranges are current (rows with expired END_DATE_ACTIVE), and confirming no orphaned authorizations exist after a hold is deleted.

Related Objects

• SO_HOLDS — Parent hold definition; joined on SO_HOLD_AUTHORIZATIONS.HOLD_ID = SO_HOLDS.HOLD_ID.
• SO_HOLDS_TL — Translated hold names and descriptions.
• SO_HOLD_TYPES / SO_HOLD_RELEASES — Related hold configuration tables used together when interpreting authorization behavior.
• FND_RESPONSIBILITY — Responsibility master; joined on RESPONSIBILITY_ID.
• FND_RESPONSIBILITY_VL — The translatable view of FND_RESPONSIBILITY, preferred for reporting.
• FND_APPLICATION — Resolves APPLICATION_ID to an application name.
• OE_ORDER_HEADERS_ALL / OE_ORDER_LINES_ALL — Order transactions where hold authorization ultimately takes effect.

Order Management APIs — notably OE_HOLDS_PUB and the Order Management public APIs for applying and releasing holds — enforce these authorizations at runtime, making SO_HOLD_AUTHORIZATIONS the configuration source of truth for hold security across both 12.1.1 and 12.2.2.