Results for “oke_chg_statuses_vl”
38 results
AI-generated from documented ETRM metadata — verify critical details on the linked pages.
Overview
OKE_CHG_STATUSES_VL is a multi-lingual (VL) view owned by the APPS schema in Oracle E-Business Suite. It is delivered as part of the OKE – Project Contracts product family and serves as the descriptive, language-aware presentation layer for contract change request statuses. The view exposes the codes, names, descriptions, and workflow associations that define each valid status a contract change request can occupy during its lifecycle.
Because Oracle EBS stores translatable descriptive text separately from its base transactional and setup data, the "_VL" suffix indicates that this view joins a base table (holding language-independent columns, including the primary key and WHO audit columns) with a translation table (holding the language-specific name and description). This design allows the same status code to be rendered in the session's language without duplicating the underlying setup rows. The view is therefore the standard source that forms, concurrent programs, and reports query when they need to display a change request status to an end user in their native language rather than as a raw code.
The view was documented as VALID in ETRM, confirming it is compiled and available in the supported 12.1.1 and 12.2.2 environments. Its role is primarily read-only: it presents reference data used by Oracle Forms, OAF pages, and custom reporting or integration extracts rather than storing data itself.
Underlying Base Objects
The view text joins five documented objects:
- OKE_CHG_STATUSES_B – the base table holding language-independent status attributes (status code, type, default flag, workflow item type and process, active date range, and the DFF attribute columns). It supplies the primary key CHG_STATUS_CODE.
- OKE_CHG_STATUSES_TL – the translation table supplying CHG_STATUS_NAME and DESCRIPTION, joined on CHG_STATUS_CODE and the session language.
- WF_ITEM_TYPES_TL – the Oracle Workflow item type translation table, outer-joined to provide the workflow item type display name.
- WF_RUNNABLE_PROCESSES_V – the Workflow runnable processes view, outer-joined to resolve the process display name.
- FND_LOOKUP_VALUES_VL – the multilingual lookup values view, joined on LOOKUP_TYPE = 'CHG_STATUS_TYPE' and the status type code, with VIEW_APPLICATION_ID = 777, to translate the status type into its meaning.
The language joins are driven by USERENV('LANG'), so the effective row returned depends on the runtime language setting of the querying session.
Key Columns
- CHG_STATUS_CODE – the unique identifier of the status; primary join key across all base objects.
- CHG_STATUS_NAME / DESCRIPTION – the translated, user-facing name and description from OKE_CHG_STATUSES_TL.
- CHG_STATUS_TYPE_CODE / CHG_STATUS_TYPE_NAME – the status type code and its FND lookup meaning.
- DEFAULT_STATUS – flag indicating whether the status is the default assigned to new change requests.
- WF_ITEM_TYPE / WF_ITEM_TYPE_NAME – the Oracle Workflow item type associated with the status, with its display name.
- WF_PROCESS / WF_PROCESS_NAME – the runnable workflow process name and display name.
- START_DATE_ACTIVE / END_DATE_ACTIVE – the effective date range during which the status is active.
- ATTRIBUTE_CATEGORY and ATTRIBUTE1–15 – descriptive flexfield columns carried through from the base table.
- ROW_ID and WHO columns (CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN) – standard audit and row identifier columns.
Common Use Cases and Queries
Typical uses include populating status list-of-values on change request forms, joining change request records to their current status description in reports, and extracting reference data for downstream integrations. A basic query returning all active statuses is:
SELECT chg_status_code, chg_status_name, chg_status_type_name, default_status FROM oke_chg_statuses_vl WHERE NVL(end_date_active, SYSDATE + 1) > SYSDATE ORDER BY chg_status_name;SELECT chg_status_code, chg_status_name, wf_item_type, wf_process FROM oke_chg_statuses_vl WHERE default_status = 'Y';SELECT chg_status_type_name, COUNT(*) FROM oke_chg_statuses_vl GROUP BY chg_status_type_name;
Because results depend on USERENV('LANG'), these queries return names and descriptions in the language of the executing session, making the view suitable for multilingual reporting and user-facing integrations without additional translation logic.
-
View: OKE_CHG_STATUSES_VL 12.2.2
Contract change request status multi-lingual view
APPS.OKE_CHG_STATUSES_VL·↳ FND_LOOKUP_VALUES_VL·↳ OKE_CHG_STATUSES_B·↳ OKE_CHG_STATUSES_TL·Explore OKE module →
-
View: OKE_CHG_STATUSES_VL 12.1.1
Contract change request status multi-lingual view
APPS.OKE_CHG_STATUSES_VL·↳ FND_LOOKUP_VALUES_VL·↳ OKE_CHG_STATUSES_B·↳ OKE_CHG_STATUSES_TL·Explore OKE module →
-
12.2.2 FND Design Data 12.2.2
-
12.1.1 FND Design Data 12.1.1
-
12.1.1 DBA Data 12.1.1
-
12.2.2 DBA Data 12.2.2
-
eTRM - OKE Tables and Views 12.1.1
This table stores the version comparison results.
-
eTRM - OKE Tables and Views 12.2.2
This table stores the version comparison results.
-
12.2.2 DBA Data 12.2.2
-
12.1.1 DBA Data 12.1.1
-
eTRM - FND Tables and Views 12.2.2
No longer used
-
eTRM - FND Tables and Views 12.1.1
No longer used
-
eTRM - OKE Tables and Views 12.1.1
This table stores the version comparison results.
-
eTRM - OKE Tables and Views 12.2.2
This table stores the version comparison results.
-
eTRM - FND Tables and Views 12.2.2
No longer used
-
eTRM - FND Tables and Views 12.1.1
No longer used