Results for “oebv_order_hold_authorizations”

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

Overview

OEBV_ORDER_HOLD_AUTHORIZATIONS is a reporting and integration view within the Oracle E-Business Suite Order Entry (OE) module. It exposes hold authorization data that controls which responsibilities are permitted to apply, release, or otherwise act upon order holds. The view is classified as "Retrofitted," indicating that it was introduced or reconstituted to preserve backward compatibility with earlier EBS releases while operating against the current underlying schema. This makes it a candidate object for custom reports, extensions, and interfaces that were originally authored against legacy hold authorization structures.

The view is defined with a WITH READ ONLY clause, so it is strictly a query surface. It cannot be used as a DML target for inserts, updates, or deletes; any modification to hold authorization data must be performed against the base table directly. Its principal role is to provide a stable, denormalized read interface over the SO_HOLD_AUTHORIZATIONS table, translating internal lookup codes into display-friendly meanings for downstream reporting.

Underlying Base Objects

The view is defined entirely over a single base table, SO_HOLD_AUTHORIZATIONS. No other base objects are documented in the ETRM metadata. The projection includes literal substitution strings that Oracle Forms and the localization framework interpret at runtime:

• '_LA:AUTHORIZED_ACTION_CODE:SO_LOOKUPS:AUTHORIZED_ACTION:MEANING' — a localization directive that resolves the authorized action code to its descriptive meaning from the SO_LOOKUPS lookup type AUTHORIZED_ACTION.
• '_DF:OE:SO_HOLD_AUTHORIZATIONS:SO_HOLD_AUTHORIZATIONS' — a descriptive flexfield reference pointing to the SO_HOLD_AUTHORIZATIONS flexfield definition.

These literals appear as column values in the view text and are normally interpreted by the Oracle Applications presentation layer rather than by SQL*Plus or generic JDBC clients.

Key Columns

The view projects the following columns, several of which carry aliased or directive names:

• "_LA:AUTHORIZED_ACTION" — the localized meaning of the authorized action, derived through the SO_LOOKUPS lookup. In practice this carries the AUTHORIZED_ACTION_CODE.
• HOLD_ID — the identifier of the order hold to which the authorization applies. This is the column most frequently used as a filter, and it is the term the user searched for.
• RESPONSIBILITY_ID — the responsibility granted authority over the hold.
• APPLICATION_ID — the application context owning the responsibility.
• START_DATE and END_DATE — the active window during which the authorization is valid. Records outside this range should be treated as inactive.
• "_DF" — the descriptive flexfield reference for the row.
• Audit columns: LAST_UPDATE_DATE, LAST_UPDATED_BY, CREATION_DATE, and CREATED_BY.

Common Use Cases and Queries

The most common scenario is determining which responsibilities may act on a given hold. A typical query filters by HOLD_ID:

• SELECT hold_id, responsibility_id, start_date, end_date FROM oebv_order_hold_authorizations WHERE hold_id = :hold_id;
• SELECT hold_id, responsibility_id FROM oebv_order_hold_authorizations WHERE SYSDATE BETWEEN start_date AND NVL(end_date, SYSDATE); — returns only currently effective authorizations.
• Joining to FND_RESPONSIBILITY to resolve responsibility names for a report of holds and their authorized owners.

Because the object is read only, any administrative correction must target SO_HOLD_AUTHORIZATIONS. The ETRM metadata notes "Not implemented in this database" for the implementation/DBA data section, meaning availability may vary by instance or patch level; developers should verify the view exists before relying on it in a concurrent program or interface.