Results for “cs_kb_lib_properties_vl”

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

Overview

The APPS.CS_KB_LIB_PROPERTIES_VL view belongs to the Service (CS) product family within Oracle E-Business Suite 12.1.1 and 12.2.2. It is a language-specific (VL) view that exposes translated configuration properties governing the display behavior of the knowledge base library and its sections. In earlier releases of ETRM, this view supported the Knowledge Base (KB) authoring and browsing user interfaces by defining how many hierarchy levels to render and whether certain library or section elements should be suppressed from end users.

The documented ETRM metadata for this object carries an explicit status of VALID, yet the description states "View no longer used." This combination is common in EBS data model documentation: the object remains compiled and queryable in the APPS schema for backward compatibility, but Oracle no longer references it from active application code paths. As a result, it should not be considered part of the supported integration surface for new development. Its principal reporting value today is historical or diagnostic — confirming legacy configuration values during upgrades, audits, or data migration exercises where a customer is moving off deprecated Knowledge Base functionality.

Underlying Base Objects

The view is defined over two documented base objects, both resolved through public synonyms in the APPS schema:

• CS_KB_LIB_PROPERTIES_B — the base table holding the language-independent property definitions, including the category linkage and the display control flags.
• CS_KB_LIB_PROPERTIES_TL — the translation table holding language-dependent descriptive text for each property.

The join is performed on PROPERTY_ID, constrained by TL.LANGUAGE = USERENV('LANG'). This is the standard EBS "VL" pattern: the _B table supplies the operational attributes while the _TL table supplies the locale-appropriate text, producing a single row per property for the session's current language. Because the view resolves its language at runtime via USERENV, identical queries issued from different sessions may return different DETAILS values.

Key Columns

• CATEGORY_ID — identifier of the knowledge base category to which the property applies; the primary grouping key for the display rules.
• PROPERTY_ID — unique identifier of the property record; the join key between the _B and _TL tables.
• LEVELS_TO_DISPLAY — numeric control indicating how many levels of the library hierarchy are exposed to the user.
• HIDE_LIBRARY_FLAG — flag indicating whether the entire library node is hidden from display.
• HIDE_SECTION_FLAG — flag indicating whether individual sections within the library are suppressed.
• LANGUAGE — the language code of the returned translated row, always equal to the session's USERENV('LANG') value.
• SOURCE_LANG — the base language from which the translation was derived, useful for identifying untranslated or fallback content.
• DETAILS — the language-specific descriptive text associated with the property.

Common Use Cases and Queries

The view is principally queried for audit and troubleshooting rather than for ongoing integration. A typical use is enumerating the configured display rules for a given category:

SELECT category_id, property_id, levels_to_display,
       hide_library_flag, hide_section_flag, details
FROM   apps.cs_kb_lib_properties_vl
WHERE  category_id = :p_category_id;

To detect properties lacking a translation in the current session language, compare the retained source_lang against language:

SELECT property_id, language, source_lang, details
FROM   apps.cs_kb_lib_properties_vl
WHERE  source_lang <> language;

Because the object is documented as no longer used, any dependency discovered in custom reports, interfaces, or extensions should be treated as technical debt and reassessed against the current Knowledge Management data model before an upgrade to 12.2.2 or later. Where the view is still required for interim reporting, it should be accessed read-only and never used as a target for DML.