Search Results composite_text_index

Overview

CS_KB_ELEMENTS_VL is a multi-lingual (VL) view owned by the APPS schema in Oracle E-Business Suite, delivered as part of the CS (Service) product family. It presents knowledge base element definitions maintained by Oracle Knowledge Base functionality within Service. The view is defined over the base and translation tables CS_KB_ELEMENTS_B and CS_KB_ELEMENTS_TL, joining them so that each base row is returned with the translated, language-specific content appropriate to the current session.

In EBS 12.1.1 and 12.2.2 the object reports a status of VALID. Because it resolves the language at runtime through USERENV('LANG'), it serves as the standard reporting and integration access point for knowledge base element data, allowing concurrent users in different languages to query the same underlying records and receive translated NAME and DESCRIPTION values without writing explicit language joins. Report developers, BI Publisher data models, and interface programs use it in preference to the base tables.

Underlying Base Objects

The view is documented as being defined over two base objects, both exposed through synonyms: CS_KB_ELEMENTS_B, which stores the language-independent attributes of each knowledge element, and CS_KB_ELEMENTS_TL, which stores the translatable text. The join condition is B.ELEMENT_ID = T.ELEMENT_ID, with the additional filter T.LANGUAGE = USERENV('LANG'), which restricts the translation row to the language of the querying session.

This _B/_TL pairing is the standard EBS multi-lingual table pattern. The _B table holds one row per element; the _TL table holds one row per element per installed language. The view therefore behaves as a single logical entity, hiding both the physical partitioning of columns and the language resolution logic from the caller.

Key Columns

• ELEMENT_ID — Primary identifier of the knowledge base element, and the join key between the base and translation tables.
• ELEMENT_TYPE_ID — Reference to the element type classification that governs how the element is used.
• ELEMENT_NAME — Internal, language-independent name of the element, carried on the base table.
• GROUP_FLAG — Flag indicating whether the element is treated as a group (container) rather than an individual item; this is the column most directly implicated in the searched term "group_flag."
• NAME and DESCRIPTION — Language-specific translated text sourced from the _TL table.
• STATUS — Lifecycle state of the element, controlling whether it is active and available.
• ACCESS_LEVEL — Visibility or authorization level applied to the element.
• CONTENT_TYPE and ELEMENT_NUMBER — Content classification and the user-facing element number.
• COMPOSITE_TEXT_INDEX — Text index value from the translation table, used in knowledge base text search.
• ROW_ID — Row identifier derived from the base table ROWID.
• Audit columns — CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, LAST_UPDATED_BY, and LAST_UPDATE_LOGIN.
• ATTRIBUTE_CATEGORY and ATTRIBUTE1–ATTRIBUTE15 — The standard EBS descriptive flexfield columns.

Common Use Cases and Queries

Typical uses include listing active knowledge elements for a language, filtering group containers from individual items, and feeding the element number and translated name into downstream extracts. A representative query for group elements is:

SELECT element_id,
       element_number,
       element_name,
       name,
       status,
       access_level
FROM   apps.cs_kb_elements_vl
WHERE  group_flag = 'Y'
AND    status = 'A'
ORDER  BY element_name;

A query joining related knowledge base structures might select ELEMENT_TYPE_ID and CONTENT_TYPE alongside the translated NAME. Because the view already applies the USERENV('LANG') predicate, no additional language filter is required; the returned NAME and DESCRIPTION match the session language. Developers needing only base attributes should note that filtering on translated columns such as NAME may prevent index usage on the _TL table, so performance-sensitive queries should constrain ELEMENT_ID or ELEMENT_NUMBER where possible.