Search Results cs_kb_visibilities_vl




Overview
Explore in AI Chat

Overview

The CS_KB_VISIBILITIES_VL view is a multi-lingual (ML) dictionary view in the Oracle E-Business Suite Service (CS) module, owned by the APPS schema and bearing a VALID status. It presents Knowledge Base (KB) visibility definitions together with their translated name and description attributes. The "VL" suffix follows Oracle's standard convention for views that join a "_B" (base) table to its "_TL" (translation) table, restricting the translation language to the session's current language via USERENV('LANG'). In both Oracle EBS 12.1.1 and 12.2.2, the view is classified as a Knowledge Base Visibilities Multi Lingual View, making it the canonical source for retrieving visibility records in the language of the connected user.

Because the underlying tables reside in the APPS schema and are exposed as synonyms, this view is accessible to any database session granted the appropriate privileges through APPS. It supports reporting, integration, and personalization logic that must resolve a visibility's localized label and description rather than its raw numeric identifier. Its position in the KB security model means it is frequently consumed alongside KB setup queries and reference data extracts.

Underlying Base Objects

Per the ETRM metadata, the view is defined over two documented base objects, exposed to the APPS schema as synonyms:

  • CS_KB_VISIBILITIES_B — the base table holding language-independent attributes such as the visibility identifier, display position, effective date range, audit columns, and the fifteen descriptive flexfield (DFF) attribute columns.
  • CS_KB_VISIBILITIES_TL — the translation table holding the language-specific NAME and DESCRIPTION, keyed by VISIBILITY_ID and LANGUAGE.

The join condition is B.VISIBILITY_ID = T.VISIBILITY_ID combined with T.LANGUAGE = USERENV('LANG'). This inner equijoin returns one row per visibility, presenting base columns from the _B table and translated text from the _TL table for the active session language.

Key Columns

The view exposes the following documented columns:

  • ROW_ID — the ROWID from the _B table, useful for direct row addressing.
  • VISIBILITY_ID — the primary identifier of the visibility record; the join key between base and translation tables.
  • POSITION — ordering position used to sequence visibilities in list-of-values and setup displays.
  • START_DATE_ACTIVE / END_DATE_ACTIVE — effective dating that determines when a visibility is active.
  • NAME / DESCRIPTION — the translated label and descriptive text from CS_KB_VISIBILITIES_TL in the session language.
  • CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN — standard EBS audit columns.
  • ATTRIBUTE_CATEGORY and ATTRIBUTE1 through ATTRIBUTE15 — the descriptive flexfield segments for extensible, customer-defined data.

Common Use Cases and Queries

Typical scenarios include building Value Set queries for KB visibility selection, extracting visibility reference data for downstream systems, and reporting on active visibilities in the user's language.

List active visibilities in the current session language, ordered for display:

SELECT visibility_id, name, description, position
FROM cs_kb_visibilities_vl
WHERE TRUNC(SYSDATE) BETWEEN NVL(start_date_active, SYSDATE) AND NVL(end_date_active, SYSDATE)
ORDER BY position;

Retrieve a single visibility's localized text by identifier:

SELECT name, description
FROM cs_kb_visibilities_vl
WHERE visibility_id = :p_visibility_id;

Populate an LOV with localized names:

SELECT name, visibility_id
FROM cs_kb_visibilities_vl
ORDER BY position, name;

Because filtering depends on USERENV('LANG'), rows appear only for the connected session's language; deployments supporting multiple languages must ensure the required translation rows exist in CS_KB_VISIBILITIES_TL.