Search Results cs_kb_category_groups_b




Overview
Explore in AI Chat

Overview

The CS_KB_CATEGORY_GROUPS_B table is a core data structure within the Oracle E-Business Suite (EBS) Service (CS) module, specifically for the Knowledge Base (KB) application. It functions as the base table for storing the fundamental definition of category groups. In the context of the Knowledge Base, a category group is a logical container used to organize and manage categories of solutions, articles, or other knowledge artifacts. This table holds the primary, language-independent transactional data, while its corresponding translation table, CS_KB_CATEGORY_GROUPS_TL, stores the language-specific names and descriptions. Its primary role is to serve as the master source for category group identifiers and structural metadata, enabling the hierarchical classification and efficient retrieval of knowledge content within the service and support domains of Oracle EBS 12.1.1 and 12.2.2.

Key Information Stored

While the provided ETRM metadata does not list specific columns, the structure of Oracle EBS base tables and the documented relationships allow for a reliable inference of its key attributes. The primary column is CATEGORY_GROUP_ID, which is the unique identifier (Primary Key) for each category group record. This surrogate key is referenced by all related tables. Other standard columns typical of an EBS base table include CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, LAST_UPDATED_BY, and LAST_UPDATE_LOGIN for auditing purposes. The table likely contains columns defining the group's operational context, such as START_DATE_ACTIVE and END_DATE_ACTIVE to control its active period, and potentially a SEEDED_FLAG to indicate if the record was delivered by Oracle. The actual descriptive name for the group is stored in the associated translation table.

Common Use Cases and Queries

This table is central to administration and reporting of the Knowledge Base's taxonomy. Common use cases include setting up and maintaining the category hierarchy for solution categorization, generating reports on category group utilization, and integrating knowledge taxonomy with other service processes like service request flows. A typical query would join the base table with its translation table to retrieve a list of active category groups in a specific language. For example:

SELECT b.CATEGORY_GROUP_ID, tl.NAME, tl.DESCRIPTION
FROM CS_KB_CATEGORY_GROUPS_B b,
CS_KB_CATEGORY_GROUPS_TL tl
WHERE b.CATEGORY_GROUP_ID = tl.CATEGORY_GROUP_ID
AND tl.LANGUAGE = USERENV('LANG')
AND SYSDATE BETWEEN NVL(b.START_DATE_ACTIVE, SYSDATE) AND NVL(b.END_DATE_ACTIVE, SYSDATE);

Another critical use case involves understanding category membership by joining with CS_KB_CAT_GROUP_MEMBERS, or analyzing approval workflows via CS_KB_CAT_GROUP_FLOWS.

Related Objects

The CS_KB_CATEGORY_GROUPS_B table is the central hub in a network of related objects that manage category group metadata, membership, and workflows. The documented foreign key relationships are as follows:

  • CS_KB_CATEGORY_GROUPS_TL: References CATEGORY_GROUP_ID to store translated names and descriptions for the group.
  • CS_KB_CAT_GROUP_MEMBERS: References CATEGORY_GROUP_ID to define which specific categories belong to a given group.
  • CS_KB_CAT_GROUP_FLOWS: References CATEGORY_GROUP_ID to associate approval workflows with a specific category group.
  • CS_KB_CAT_GROUP_DENORM: References CATEGORY_GROUP_ID; this is typically a denormalized summary or hierarchy table used for performance optimization in category navigation and queries.

All these relationships are established via the foreign key column CATEGORY_GROUP_ID in the child tables pointing to the primary key of the same name in CS_KB_CATEGORY_GROUPS_B.