Results for “cs_kb_set_types_tl”

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

Overview

CS_KB_SET_TYPES_TL is the translation (language) table for knowledge base set types within the Oracle E-Business Suite CS – Service module, owned by the CS schema. It stores the language-dependent display attributes — most notably the name and description — for the set types defined in its base counterpart, CS_KB_SET_TYPES_B. Set types are the classification groupings that organize knowledge base content (articles, solutions, and related knowledge objects) so that agents and self-service users can filter and retrieve information within the appropriate context.

The object is documented as VALID in ETRM releases 12.1.1 and 12.2.2, with a physical schema of 12 columns. The heuristic Data Vault classification mined from the foreign-key structure is link. In modeling terms, this suggests the table functions as an associative structure connecting a base entity (CS_KB_SET_TYPES_B via SET_TYPE_ID) to a language dimension (FND_LANGUAGES via LANGUAGE), rather than as a standalone hub or a pure descriptive satellite. Practitioners designing analytic or staging layers may therefore treat it as a translation resolution link that supplies the human-readable labels required to present set-type data.

Key Information Stored

Although 12 columns are documented, the operationally significant fields are the identifiers, translation attributes, and audit columns.

• SET_TYPE_ID — the surrogate/business identifier of the parent set type; part of the primary key and the FK to CS_KB_SET_TYPES_B.
• LANGUAGE — the language of the row; part of the primary key and an FK to FND_LANGUAGES.
• SOURCE_LANG — the source language from which the translation originated; also an FK to FND_LANGUAGES, used to track translation provenance.
• NAME — the translated display name of the set type, the primary user-facing label.
• DESCRIPTION — the translated descriptive text for the set type.
• CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN — standard EBS audit columns recording who created and last modified each translation row and when.
• SECURITY_GROUP_ID — the multi-org/security grouping reference (FK to FND_SECURITY_GROUPS) controlling row-level access.
• ZD_EDITION_NAME — the edition identifier supporting the online patching (Edition-Based Redefinition) model in 12.2.x.

The primary key is CS_KB_SET_TYPES_TL_PK (SET_TYPE_ID, LANGUAGE). A unique index, CS_KB_SET_TYPES_TL_U1 (SET_TYPE_ID, LANGUAGE, ZD_EDITION_NAME), extends the key with the edition column, reflecting the business-key candidate under EBR. The surrogate key proper is SET_TYPE_ID combined with LANGUAGE; SET_TYPE_ID alone is the business key carried from the base table.

Common Use Cases and Queries

Typical usage resolves a language-specific set-type label. A single-language lookup joins the translation table to the base table and filters by language and edition:

• Retrieving set-type names for a given session language by joining CS_KB_SET_TYPES_TL to CS_KB_SET_TYPES_B on SET_TYPE_ID and constraining LANGUAGE = :p_lang.
• Reporting on translation completeness by comparing SOURCE_LANG to LANGUAGE and checking for missing rows across the set of installed languages in FND_LANGUAGES.
• Seed data and migration validation, verifying that every base set type has one translation row per required language.
• BI extracts that join NAME and DESCRIPTION to knowledge base activity facts to present readable set-type labels.

A representative pattern:

SELECT b.set_type_id, t.name, t.description
FROM cs_kb_set_types_b b, cs_kb_set_types_tl t
WHERE b.set_type_id = t.set_type_id
AND t.language = USERENV('LANG')
AND t.zd_edition_name = 'SET1';

Related Objects

• CS_KB_SET_TYPES_B — the base table holding language-independent set-type definitions; joined on SET_TYPE_ID.
• FND_LANGUAGES — the language reference table; referenced twice, via LANGUAGE and SOURCE_LANG, to validate languages installed in the instance.
• FND_SECURITY_GROUPS — the security group reference controlling row-level visibility, joined on SECURITY_GROUP_ID.
• Knowledge base content tables — the set-type identifiers ultimately classify knowledge objects whose translated labels are resolved through this table for display in the Service module UI.
• FND_TERRITORIES / FND_LANGUAGE views and multilingual reporting utilities that consume translation tables for localized output.

Because it is a translation table, direct DML is uncommon; maintenance normally occurs through the owning application components and concurrent translation programs. Read access is the predominant operational pattern.