Results for “oke_priority_codes_vl”

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

Overview

OKE_PRIORITY_CODES_VL is a multi-lingual (ML) view in the Oracle E-Business Suite APPS schema, owned by the OKE – Project Contracts product family. It presents priority ratings used within Project Contracts, merging the language-independent definition of each priority code with its translated name and description, and further resolving the priority type lookup into a user-facing meaning. The "_VL" suffix denotes a "view language" construct that Oracle EBS generates for translatable entities; such views return translated columns for the session's current language, determined at runtime through the USERENV('LANG') function, while exposing the base-table surrogate and audit columns unchanged.

In reporting and integration scenarios, this view serves as the recommended access path for any consumer that requires priority code semantics in the reporting user's language. Because it performs the translation join, the lookup meaning join, and language filtering internally, external reports, BI Publisher data models, interfaces, and custom concurrent programs can query a single object rather than replicating the three-way join. The view is documented as VALID in both EBS 12.1.1 and 12.2.2, and its column list and view text are consistent across those releases.

Underlying Base Objects

The view text is defined over three documented base objects, joined as follows:

• OKE_PRIORITY_CODES_B (synonym to the base table) — supplies the language-independent priority definition, including PRIORITY_CODE, PRIORITY_TYPE_CODE, the active date range, WHO/audit columns, and the fifteen descriptive flexfield ATTRIBUTE columns. It is aliased as B in the view definition.
• OKE_PRIORITY_CODES_TL (synonym to the translation table) — supplies PRIORITY_NAME and DESCRIPTION for the current session language. The join is B.PRIORITY_CODE = T.PRIORITY_CODE, with T.LANGUAGE = USERENV('LANG').
• FND_LOOKUP_VALUES_VL (view) — supplies the MEANING for the PRIORITY_TYPE_CODE. The join restricts LOOKUP_TYPE to 'PRIORITY_TYPE' and VIEW_APPLICATION_ID to 777 (the OKE application identifier), aliased as PT.

The _VL naming convention and the "_B"/"_TL" table pair confirm that priority codes follow the standard Oracle multi-lingual schema pattern: one base row per code, with one translation row per installed language.

Key Columns

• PRIORITY_CODE — the primary business key, unique per priority rating.
• PRIORITY_NAME — translated name from OKE_PRIORITY_CODES_TL for the session language.
• DESCRIPTION — translated long description for the session language.
• PRIORITY_TYPE_CODE — the lookup code classifying the priority type; this is the column most closely associated with the user's search term "priority_type_code".
• PRIORITY_TYPE_NAME — the translated MEANING of the priority type lookup, joined from FND_LOOKUP_VALUES_VL where LOOKUP_TYPE = 'PRIORITY_TYPE' and VIEW_APPLICATION_ID = 777. Note the column list names this column PRIORITY_TYPE_NAME even though the underlying selected expression is PT.MEANING.
• START_DATE_ACTIVE / END_DATE_ACTIVE — effective dating that determines whether a priority code is currently usable.
• CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN — standard WHO audit columns.
• ATTRIBUTE_CATEGORY and ATTRIBUTE1–ATTRIBUTE15 — descriptive flexfield context and segment values, surfaced directly from the base table.
• ROW_ID — the base-table ROWID, selected as B.ROWID; it is not the physical ROWID of the view and should be treated cautiously in DML contexts.

Common Use Cases and Queries

Typical usage includes validating priority codes entered on contract lines, populating LOVs and reports that must show the localized priority name, and extracting priority classifications for analytics. Because the view already resolves the lookup, list-of-values queries should generally filter to active codes. A representative query is:

SELECT priority_code, priority_name, priority_type_code, priority_type_name, start_date_active, end_date_active
FROM apps.oke_priority_codes_vl
WHERE (end_date_active IS NULL OR end_date_active >= SYSDATE)
ORDER BY priority_type_code, priority_name;

To restrict to one classification, filter on the lookup code, for example WHERE priority_type_code = :type_code. For integration extracts, select the desflex attributes alongside the business columns. Reports requiring all languages regardless of session language cannot use this view; they must query OKE_PRIORITY_CODES_TL directly.