Results for “cs_kb_set_types_vl”

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

Overview

CS_KB_SET_TYPES_VL is a multi-lingual (VL) view owned by the APPS schema in Oracle E-Business Suite Release 12.1.1 and 12.2.2. It belongs to the CS — Service product family and exposes knowledge base set type definitions maintained by the Service (TeleService / Knowledge Management) module. The view presents a language-stripped, user-facing representation of set type metadata by joining the base table CS_KB_SET_TYPES_B with its translation table CS_KB_SET_TYPES_TL, returning the translated NAME and DESCRIPTION values relevant to the session language.

Set types in the knowledge base context define groupings or classifications used to organize and control knowledge articles and related Service entities. The VL view is the standard reporting and integration interface for this data: it hides the underlying table structure and the language join, presenting a single curated row per set type with the appropriate translation for the current user's language environment. Its status is documented as VALID, indicating it is a supported, compiled object within the APPS schema.

Underlying Base Objects

The view is defined over two documented base objects:

• CS_KB_SET_TYPES_B (SYNONYM) — the base table holding language-independent attributes, including keys, flexfield segments, and effective dating columns.
• CS_KB_SET_TYPES_TL (SYNONYM) — the translation table holding the language-dependent NAME and DESCRIPTION values, joined by SET_TYPE_ID filtered on LANGUAGE = USERENV('LANG').

The view text joins the two tables on SET_TYPE_ID and restricts the translation row to the language returned by USERENV('LANG'). Because translations are language-specific, the view returns exactly one translation row per set type for the active session language. All 15 descriptive flexfield (DFF) attribute columns are sourced from the _B table, preserving the configured flexfield structure. The _B and _TL tables are documented as referenced through synonyms in the APPS schema, the standard pattern for EBS multi-lingual views.

Key Columns

• ROW_ID — ROWID sourced from the base table; useful for row identification and certain update patterns.
• SET_TYPE_ID — Primary key and join key between the base and translation tables; the identity of the set type.
• SET_TYPE_NAME — Language-independent internal name from the _B table, used by code and integrations for stable references.
• NAME — Translated, user-facing display name from the _TL table for the current language.
• DESCRIPTION — Translated descriptive text for the set type.
• START_DATE_ACTIVE / END_DATE_ACTIVE — Effective dating range controlling whether the set type is currently active.
• CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN — Standard EBS audit columns maintained on the base record.
• ATTRIBUTE_CATEGORY and ATTRIBUTE1 – ATTRIBUTE15 — Descriptive flexfield segments carried from the base table.

Common Use Cases and Queries

The view is typically used to list and validate knowledge base set types in reports, LOVs, and integrations, ensuring the correct language-specific labels appear without requiring the consuming query to manage the translation join. A typical listing query is:

• SELECT set_type_id, set_type_name, name, description, start_date_active, end_date_active FROM apps.cs_kb_set_types_vl ORDER BY name;
• Filtering active set types: ... WHERE (end_date_active IS NULL OR end_date_active >= SYSDATE) AND start_date_active <= SYSDATE;
• Joining to child knowledge objects by SET_TYPE_ID to resolve display names in a localized report.

Because it resolves the session language automatically, the view is preferred over directly querying the base and translation tables in reporting and integration code.