Results for “oke_hold_statuses_vl”

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

Overview

OKE_HOLD_STATUSES_VL is a multi-lingual (ML) view owned by the APPS schema within the OKE – Project Contracts product family. It presents contract hold status definitions in the run-time session language, combining descriptive and translatable attributes from a base table and its translation table, and enriching them with Oracle Workflow item type and process display names. In Oracle EBS 12.1.1 and 12.2.2 the view serves as the primary reporting and integration surface for hold statuses used to suspend or release contract activity in Project Contracts. Because hold status records participate directly in workflow-driven approval and routing logic, the view exposes the Workflow item type and process linkage alongside the user-facing name and description.

The view is registered as VALID in ETRM and is documented as a "Contract hold statuses multi-lingual view." Its naming follows the standard EBS convention in which a _VL view exposes the "_TL" translation columns resolved against USERENV('LANG'), while the underlying _B table stores language-independent attributes.

Underlying Base Objects

The documented base objects referenced by the view are:

• OKE_HOLD_STATUSES_B (SYNONYM) – language-independent base table holding the hold status code, audit columns, Workflow item type and process, active date range, and the 15 descriptive flexfield attribute columns.
• OKE_HOLD_STATUSES_TL (SYNONYM) – translation table supplying HOLD_STATUS_NAME and DESCRIPTION per language.
• WF_ITEM_TYPES_TL (SYNONYM) – Workflow item type translations, outer-joined to the base table on WF_ITEM_TYPE to derive the item type display name.
• WF_RUNNABLE_PROCESSES_V (VIEW) – Workflow runnable processes view, outer-joined on WF_ITEM_TYPE and WF_PROCESS to resolve the process display name.

The view joins the base and translation tables on HOLD_STATUS_CODE, restricting the translation row to T.LANGUAGE = USERENV('LANG'). The Workflow joins are outer joins ((+)), meaning hold statuses without a corresponding Workflow item type or process record are still returned with null display names.

Key Columns

• HOLD_STATUS_CODE – Primary business key shared across the _B and _TL tables; the value referenced by other OKE entities.
• HOLD_STATUS_NAME, DESCRIPTION – Language-resolved display text from OKE_HOLD_STATUSES_TL.
• WF_ITEM_TYPE, WF_ITEM_TYPE_NAME – Workflow item type identifier and its translated display name.
• WF_PROCESS, WF_PROCESS_NAME – Workflow process identifier and its display name.
• START_DATE_ACTIVE, END_DATE_ACTIVE – Effective date range controlling when the status is usable.
• ROW_ID, CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN – Audit columns from the base table.
• ATTRIBUTE_CATEGORY and ATTRIBUTE1–ATTRIBUTE15 – Descriptive flexfield columns for customer-specific extensions.

Common Use Cases and Queries

Typical uses include validating hold statuses during contract creation, populating value lists in extensions, and reporting on Workflow bindings for hold processing. Because the view resolves translations automatically, it is preferred over the base table for user-facing queries.

List all active hold statuses with their Workflow context:

• SELECT hold_status_code, hold_status_name, wf_item_type_name, wf_process_name FROM oke_hold_statuses_vl WHERE TRUNC(SYSDATE) BETWEEN NVL(start_date_active, SYSDATE) AND NVL(end_date_active, SYSDATE) ORDER BY hold_status_name;

Locate the Workflow item type associated with a specific status:

• SELECT hold_status_code, wf_item_type, wf_process FROM oke_hold_statuses_vl WHERE hold_status_code = :p_status;

Report on flexfield usage across hold statuses:

• SELECT hold_status_code, attribute_category, attribute1, attribute2 FROM oke_hold_statuses_vl WHERE attribute_category IS NOT NULL;

Note: the user search term wf_item_types_tl corresponds to one of the underlying base objects of this view; the Workflow item type translation table is consumed here through an outer join to supply WF_ITEM_TYPE_NAME.