Search Results css_def_priorities_vl

Overview

CSS_DEF_PRIORITIES_VL is a translated (VL) view within the Oracle E-Business Suite CSS — Support module, which is documented as obsolete in Release 12.1.1 and 12.2.2. The view exposes priority definitions used historically by the Support (CSS) application, presenting a denormalized, language-aware recordset that combines base attribute columns with translated name and description text. As a "_VL" view, it follows the standard Oracle EBS multilingual pattern: the "_B" suffix identifies the base table holding language-independent columns, while the "_TL" suffix identifies the translation table holding language-dependent columns such as NAME and DESCRIPTION.

The view's principal role in reporting and integration was to provide a single, consistent source of priority data that automatically filtered translations to the session language via USERENV('LANG'). This allowed concurrent programs, Discoverer reports, and interface extracts to retrieve priority values without performing manual joins to the translation table. Because the object is flagged as not implemented in the database documented by the ETRM metadata, it exists as documented view text rather than as a deployed, queryable entity in that environment. On this basis, any integration referencing CSS_DEF_PRIORITIES_VL should be treated as legacy and subject to verification against the target instance.

Underlying Base Objects

The documented view text defines CSS_DEF_PRIORITIES_VL as a join over two base objects:

• CSS_DEF_PRIORITIES_B — the base table storing the language-independent definition of each priority, including its identifier, version, sort order, effective dates, audit columns, and descriptive flexfield attributes.
• CSS_DEF_PRIORITIES_TL — the translation table storing the language-dependent NAME and DESCRIPTION for each priority, keyed by PRIORITY_ID and LANGUAGE.

The two objects are joined on PRIORITY_ID, with the translation table additionally constrained by T.LANGUAGE = USERENV('LANG') so that only rows matching the current session language are returned. The SELECT list draws B.ROWID and the base-table columns from CSS_DEF_PRIORITIES_B and the NAME and DESCRIPTION columns from CSS_DEF_PRIORITIES_TL. The ETRM metadata documents no other referenced base objects, and the owner of the view is not recorded.

Key Columns

• ROW_ID — the ROWID of the base-table row, exposed as ROW_ID in the view projection; useful for direct row addressing.
• PRIORITY_ID — the primary surrogate key of the priority definition and the join key between the base and translation tables.
• OBJECT_VERSION_NUMBER — the optimistic locking version counter maintained by the EBS framework on the base row.
• SORT_ORDER — the display or processing sequence assigned to the priority, used to order values in lists and reports.
• START_DATE_ACTIVE / END_DATE_ACTIVE — the effective date range governing when the priority is valid for use.
• CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN — standard "WHO" audit columns populated by the EBS application framework.
• ATTRIBUTE1 through ATTRIBUTE15, CONTEXT — descriptive flexfield columns, with CONTEXT identifying the flexfield structure in effect for the row.
• NAME — the translated priority name from CSS_DEF_PRIORITIES_TL for the session language.
• DESCRIPTION — the translated priority description from the same translation table.

Common Use Cases and Queries

Typical usage centered on presenting priorities in the user's own language and on exporting priority reference data for interfaces. A basic listing ordered by SORT_ORDER might be written as:

• SELECT priority_id, name, description, sort_order FROM css_def_priorities_vl ORDER BY sort_order;

Because the translation join is embedded in the view, no explicit language predicate is required in the calling query; USERENV('LANG') resolves it automatically. Filtering by active period is likewise straightforward: SELECT priority_id, name FROM css_def_priorities_vl WHERE TRUNC(SYSDATE) BETWEEN NVL(start_date_active, TRUNC(SYSDATE)) AND NVL(end_date_active, TRUNC(SYSDATE));. Flexfield-aware extracts can include the CONTEXT and ATTRIBUTE columns where the priority definition carries additional site-specific data. Given the obsolete status of the CSS Support module and the ETRM note that the view is not implemented in the documented database, these patterns should be validated against the specific instance before being relied upon in production reporting, and any dependent code should be scheduled for review or replacement.