Results for “oebv_hold_authorizations”
14 results
AI-generated from documented ETRM metadata — verify critical details on the linked pages.
Overview
OEBV_HOLD_AUTHORIZATIONS is a Business Intelligence System (BIS) business view owned by the APPS schema within Oracle E-Business Suite. It is delivered by the Order Management (ONT) product module and is documented as the Base BIS Business View for Order Hold Authorization. As a reporting-oriented view, it presents hold authorization data in a denormalized, business-friendly form intended for use by Oracle Business Intelligence, Discoverer, and other reporting or integration consumers that need to determine which responsibilities are authorized to apply or release specific order holds. The view is defined with a READ ONLY clause, confirming it is strictly a query object and cannot be used for DML. In both 12.1.1 and 12.2.2, the view is reported with a status of VALID in the ETRM repository, and it exposes a stable set of columns derived from the underlying authorization table.
Underlying Base Objects
The view is defined over a single base object documented as OE_HOLD_AUTHORIZATIONS, which is exposed through a SYNONYM. The view text selects directly from OE_HOLD_AUTHORIZATIONS and adds two synthetic descriptor columns that support BIS semantic layer integration: a lookup-based column for AUTHORIZED_ACTION resolved through the OE_LOOKUPS lookup type, and a descriptive flexfield reference for OE_HOLD_AUTHORIZATIONS. Because the view is a thin projection over one table, it inherits that table's row-level content without joins, aggregation, or filtering. This means the view reflects exactly the authorization records defined for each hold-to-responsibility combination, and any maintenance performed through the Order Management setup forms is immediately visible through the view.
Key Columns
The columns exposed by the view map to the following business meanings:
- HOLD_ID — Identifier of the order hold to which the authorization applies. This is the primary link between an authorization record and the hold definition itself; searching on hold_id is the most common access path.
- RESPONSIBILITY_ID — The responsibility that is authorized to apply or release the hold identified by HOLD_ID.
- APPLICATION_ID — The application context owning the responsibility, used together with RESPONSIBILITY_ID to uniquely identify the authorized responsibility.
- START_DATE and END_DATE — The active date range (mapped from START_DATE_ACTIVE and END_DATE_ACTIVE) during which the authorization is effective.
- "_LA:AUTHORIZED_ACTION" — A BIS-generated lookup column resolving the AUTHORIZED_ACTION_CODE against the OE_LOOKUPS lookup type AUTHORIZED_ACTION, exposing its MEANING for reporting.
- "_DF" — A BIS-generated descriptive flexfield column for OE_HOLD_AUTHORIZATIONS, enabling reporting of flexfield attributes.
- LAST_UPDATE_DATE, LAST_UPDATED_BY, CREATION_DATE, CREATED_BY — Standard audit columns recording who created and last modified each authorization record and when.
Common Use Cases and Queries
Typical usage includes auditing which responsibilities may place or release a given hold, validating hold setups after a patch or upgrade, and building BI reports that reconcile hold authorizations against security or setup expectations. The following query retrieves all authorizations for a specific hold, including the resolved authorized action and active dates:
SELECT hold_id, responsibility_id, application_id, authorized_action, start_date, end_date FROM apps.oebv_hold_authorizations WHERE hold_id = :hold_id;
To list only currently effective authorizations for a hold, an analyst can constrain on the date range:
SELECT hold_id, responsibility_id FROM apps.oebv_hold_authorizations WHERE hold_id = :hold_id AND TRUNC(SYSDATE) BETWEEN NVL(start_date, SYSDATE) AND NVL(end_date, SYSDATE);
Because the view is READ ONLY and joins directly to OE_HOLD_AUTHORIZATIONS, it should be used only for reporting; all transactional or setup changes must be performed against the underlying table through the supported Order Management functionality.
-
Base BIS Business View for Order Hold Authorization.
APPS.OEBV_HOLD_AUTHORIZATIONS·↳ OE_HOLD_AUTHORIZATIONS·Explore ONT module →
-
Base BIS Business View for Order Hold Authorization.
APPS.OEBV_HOLD_AUTHORIZATIONS·↳ OE_HOLD_AUTHORIZATIONS·Explore ONT module →
-
12.2.2 FND Design Data 12.2.2
-
12.1.1 FND Design Data 12.1.1
-
eTRM - ONT Tables and Views 12.2.2
OM WorkFlow Activity Skip Log.
-
12.2.2 DBA Data 12.2.2
-
eTRM - ONT Tables and Views 12.1.1
OM WorkFlow Activity Skip Log.
-
12.1.1 DBA Data 12.1.1
-
eTRM - ONT Tables and Views 12.1.1
OM WorkFlow Activity Skip Log.
-
eTRM - ONT Tables and Views 12.2.2
OM WorkFlow Activity Skip Log.