Results for “cs_kb_category_groups_b”

50+ results




Overview
Explore in AI Chat

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

Overview

CS_KB_CATEGORY_GROUPS_B is the base table that stores Knowledge Base category group definitions within the Oracle E-Business Suite Service (CS) module. Category groups provide the top-level organizational structure for the Knowledge Base, allowing administrators to cluster related solution categories into logical groupings that drive authoring, browsing, and search behavior for knowledge users. The table resides in the CS schema and is classified as VALID in the ETRM 12.2.2 repository.

In Data Vault modeling terms, the FK structure mined from this object classifies it as hub-leaning. This is a modeling suggestion rather than a physical design statement: the table behaves as a hub because its primary key, CATEGORY_GROUP_ID, is referenced as a foreign key by multiple dependent tables, and it holds the descriptive attributes that satellites would typically carry in a pure Data Vault design.

Key Information Stored

The table documents 25 columns. The most significant are:

  • CATEGORY_GROUP_ID — the surrogate primary key, enforced through CS_KB_CATEGORY_GROUPS_B_PK. It is also the business-key candidate listed under the unique index CS_KB_CATEGORY_GROUPS_U1, which uniquely identifies the row together with ZD_EDITION_NAME.
  • ZD_EDITION_NAME — the edition identifier that supports editioned or versioned knowledge content. Its presence in CS_KB_CATEGORY_GROUPS_U1 confirms that the same category group can exist across multiple editions.
  • START_DATE_ACTIVE / END_DATE_ACTIVE — the date range that controls when a category group is active and available for use.
  • CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN — the standard Oracle EBS audit columns that track who created and last modified each record.
  • ATTRIBUTE_CATEGORY and ATTRIBUTE1 through ATTRIBUTE15 — the flexible descriptive flexfield (DFF) columns that allow customers to extend the table with installation-specific attributes without modifying the schema.

The translatable category group name and description are not stored on this base table; they reside in CS_KB_CATEGORY_GROUPS_TL, which is joined back through CATEGORY_GROUP_ID.

Common Use Cases and Queries

Typical uses include reporting on active category group hierarchies, validating configuration before Knowledge Base deployment, and extracting category group metadata for integration with external knowledge portals.

  • List currently active category groups: SELECT CATEGORY_GROUP_ID FROM CS.CS_KB_CATEGORY_GROUPS_B WHERE SYSDATE BETWEEN START_DATE_ACTIVE AND NVL(END_DATE_ACTIVE, SYSDATE) AND ZD_EDITION_NAME = :edition;
  • Retrieve multilingual names: join to CS_KB_CATEGORY_GROUPS_TL on CATEGORY_GROUP_ID to obtain LANGUAGE-specific values.
  • Audit changes: filter on LAST_UPDATE_DATE or CREATED_BY to track recent administrative activity.
  • Extend reporting: reference ATTRIBUTE_CATEGORY and ATTRIBUTE1–15 to surface customer-defined DFF values.
  • Data Vault staging: treat CATEGORY_GROUP_ID as a hub key when loading a warehouse, with the audit and DFF columns as satellite attributes.

Related Objects

The following objects depend on CS_KB_CATEGORY_GROUPS_B via the CATEGORY_GROUP_ID foreign key:

  • CS_KB_CATEGORY_GROUPS_TL — holds translated category group names and descriptions keyed by CATEGORY_GROUP_ID.
  • CS_KB_CAT_GROUP_DENORM — denormalized structure supporting faster category group lookups.
  • CS_KB_CAT_GROUP_FLOWS — defines workflow or flow relationships associated with a category group.
  • CS_KB_CAT_GROUP_MEMBERS — maps individual categories to their parent category group.

Together these tables, joined through CATEGORY_GROUP_ID, constitute the full Knowledge Base category group model. Queries should always restrict to a single ZD_EDITION_NAME to avoid duplicate rows across editions.