Search Results original_author

Overview

CS_KB_SETS_VL is a multi-lingual (ML) view owned by the APPS schema in Oracle E-Business Suite, belonging to the CS (Service) product family. It presents translated knowledge base set definitions by joining the base table CS_KB_SETS_B with the translation table CS_KB_SETS_TL, resolving translated attribute values based on the session language. The "_VL" suffix is the standard Oracle Applications convention denoting a view that overlays a "_B" (base) table and its "_TL" (translation) table, returning a single row per entity in the language of the current user environment. As an APPS-level database object, the view is a supported interface for reporting, data extraction, and integration, and it shields consumers from the physical partitioning of base and translated columns. In Oracle EBS 12.1.1 and 12.2.2 the definition and status (VALID) are consistent; the view is documented in the ETRM metadata repository with the same column set in both releases.

Underlying Base Objects

The view is defined over two objects, documented as synonyms in the APPS schema: CS_KB_SETS_B and CS_KB_SETS_TL. CS_KB_SETS_B stores the language-independent, non-translatable attributes of each knowledge base set. CS_KB_SETS_TL stores the language-dependent descriptive attributes, keyed by SET_ID and LANGUAGE. The view text joins the two on SET_ID and restricts the translation row with the predicate T.LANGUAGE = USERENV('LANG'), ensuring each set appears once, rendered in the language of the runtime session. Because the join is an inner join, a set is returned only when a translation row exists for the active language code. No other tables, views, or database links are referenced by the definition.

Key Columns

• ROW_ID — the ROWID of the base table row (B.ROWID), useful for identifying the underlying physical record.
• SET_ID — primary identifier of the knowledge base set; the join key between base and translation rows.
• SET_TYPE_ID, SET_NAME — the classification and internal name of the set, sourced from the base table.
• NAME, DESCRIPTION — translated display name and description, sourced from CS_KB_SETS_TL.
• GROUP_FLAG, STATUS, ACCESS_LEVEL, VISIBILITY_ID — control whether the set is a group, its lifecycle status, its access classification, and its visibility scope.
• COMPOSITE_ASSOC_INDEX, POSITIVE_ASSOC_INDEX, NEGATIVE_ASSOC_INDEX — translated indexing attributes associated with the set's composite, positive, and negative associations.
• LATEST_VERSION_FLAG, VIEWABLE_VERSION_FLAG — versioning indicators used to distinguish the latest version from versions that may be viewed.
• SET_NUMBER, FLOW_DETAILS_ID, ORIGINAL_AUTHOR, ORIGINAL_AUTHOR_DATE — set numbering, flow linkage, and authorship/creation provenance.
• LOCKED_BY — the user currently holding a lock on the set, where applicable.
• NORM_USAGE_SCORE — normalized usage score supporting ranking or relevance displays.
• Standard WHO columns — CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN.
• ATTRIBUTE_CATEGORY and ATTRIBUTE1 through ATTRIBUTE15 — the DFF (descriptive flexfield) context and segment columns.

Common Use Cases and Queries

The view is typically queried in reports and integrations that need translated set names rather than internal set names, or that must enumerate sets by status, type, or visibility. A representative query listing active sets reads:

SELECT set_id, name, set_name, status, access_level, last_update_date
FROM cs_kb_sets_vl
WHERE status = 'ACTIVE'
ORDER BY name;

A second pattern retrieves the latest viewable version and its descriptive translation for a given set type:

SELECT set_id, name, description, latest_version_flag, norm_usage_score
FROM cs_kb_sets_vl
WHERE set_type_id = :p_set_type_id
AND viewable_version_flag = 'Y';

Because the view filters on USERENV('LANG'), output language follows the session's language setting, making it suitable for multilingual reporting without additional joins. For data extraction and interfaces, the ROW_ID, SET_NUMBER, and DFF attribute columns support reconciliation back to the base table. Joins to related knowledge base association and translation tables are generally performed on SET_ID.