Results for “cs_kb_set_categories”

50+ results




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

Overview

CS_KB_SET_CATEGORIES is a Service (CS) module table that functions as a linking table between Knowledge Base solution sets and solution categories. In Oracle E-Business Suite 12.1.1 and 12.2.2, the table enables a many-to-many relationship: a single knowledge base set (CS_KB_SETS_B) can be associated with multiple solution categories (CS_KB_SOLN_CATEGORIES_B), and a category can participate in multiple sets. This association drives the categorization and retrieval behavior of knowledge base content within the Service module, supporting search, browsing, and content classification used by agents and self-service users.

Based on the foreign-key structure documented in the ETRM metadata, this object is classified heuristically as a link table in Data Vault modeling terms. It resolves the relationship between two hub-like entities (sets and categories) and carries no descriptive business attributes beyond the association itself and auditing/attribute columns.

Key Information Stored

The table contains 23 documented columns in the 12.2.2 schema, owned by the CS schema. The most significant columns are:

  • SET_ID — Identifier of the knowledge base solution set; foreign key to CS_KB_SETS_B. Part of the composite primary key.
  • CATEGORY_ID — Identifier of the solution category; foreign key to CS_KB_SOLN_CATEGORIES_B. Part of the composite primary key.
  • CREATION_DATE — Timestamp when the association row was created.
  • CREATED_BY — User identifier who created the row.
  • LAST_UPDATE_DATE — Timestamp of the most recent update.
  • LAST_UPDATED_BY — User identifier who last updated the row.
  • LAST_UPDATE_LOGIN — Login session that performed the last update.
  • ATTRIBUTE_CATEGORY — Descriptive flexfield context value.
  • ATTRIBUTE1 through ATTRIBUTE15 — Flexfield attribute columns available for client-specific extension.

The primary key is CS_KB_SET_CATEGORIES_PK on (SET_ID, CATEGORY_ID), which is also represented by unique index CS_KB_SET_CATEGORIES_U1 on the same column pair. This composite key enforces that any given set-to-category association exists at most once, effectively making the two foreign keys together the business-key candidate.

Common Use Cases and Queries

Reporting and integration scenarios typically resolve the set/category association to their descriptive parents. A representative query listing the categories assigned to each knowledge base set is:

  • SELECT s.set_id, s.name, c.category_id, c.name FROM cs_kb_set_categories sc, cs_kb_sets_b s, cs_kb_soln_categories_b c WHERE sc.set_id = s.set_id AND sc.category_id = c.category_id;

Other common use cases include:

  • Determining which categories are available for a given published set, used to drive agent knowledge search and self-service browsing.
  • Auditing when category-to-set mappings were created or changed, using CREATION_DATE and LAST_UPDATE_DATE.
  • Diagnosing missing or duplicate category assignments by examining the composite primary key.
  • Extracting mapping data into downstream reporting or data warehouse layers, treating the table as a link between the set and category dimensions.
  • Validating content migration or setup data loads by reconciling row counts against the driving sets and categories.

Related Objects

The following objects are most significant to this table based on documented foreign-key relationships:

  • CS_KB_SETS_B — Parent table of knowledge base solution sets; joined via CS_KB_SET_CATEGORIES.SET_ID = CS_KB_SETS_B.SET_ID.
  • CS_KB_SOLN_CATEGORIES_B — Parent table of solution categories; joined via CS_KB_SET_CATEGORIES.CATEGORY_ID = CS_KB_SOLN_CATEGORIES_B.CATEGORY_ID.
  • CS_KB_SETS_TL — Translation table supplying set names and descriptions for language-specific reporting.
  • CS_KB_SOLN_CATEGORIES_TL — Translation table supplying category names and descriptions.
  • Knowledge Base solution and article tables in the CS schema that depend on category membership for indexing and retrieval.

Because the table is a pure link, it is typically accessed through the parent set and category entities rather than manipulated directly; the Service Knowledge Base setup and maintenance flows maintain the associations on the user's behalf.