Results for “original_author”

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

Overview

CS_KB_SETS_B is the base table that stores knowledge base sets within the Oracle E-Business Suite Service (CS) module. Knowledge base sets define the logical groupings of knowledge articles, solutions, and supporting content that are surfaced to service agents and customers through the interaction center and self-service channels. The _B suffix denotes the base (non-translated) table, indicating that this object holds the language-independent attributes of a knowledge set, while translated descriptive text is maintained separately in CS_KB_SETS_TL.

The table is owned by the CS schema and is documented as VALID across Oracle EBS 12.1.1 and 12.2.2, containing 45 columns in the 12.2.2 physical schema. Its primary key is CS_KB_SETS_B_PK on SET_ID, and a unique index CS_KB_SETS_B_U1 also covers SET_ID. From a Data Vault modeling perspective, the heuristic classification is hub-leaning: the table holds the durable identity of each knowledge set and is referenced by a large fan-out of dependent child tables, which is typical of a hub surrounded by satellites and links.

Key Information Stored

The surrogate primary key is SET_ID, which uniquely identifies each knowledge base set and is the column through which virtually every child table joins back to this base record. The business-facing identifier SET_NAME provides the human-readable label of the set, while SET_NUMBER supplies a durable numbering reference.

Several foreign key columns classify the set and drive its behavior. SET_TYPE_ID references CS_KB_SET_TYPES_B to determine the set type; VISIBILITY_ID references CS_KB_VISIBILITIES_B to control who may view the set; FLOW_DETAILS_ID references CS_KB_WF_FLOW_DETAILS to link the set to a workflow definition; SECURITY_GROUP_ID references FND_SECURITY_GROUPS for multi-org/security group isolation; and EMPLOYEE_ID references PSB_EMPLOYEES to attribute the set to an employee. The columns GROUP_FLAG, STATUS, ACCESS_LEVEL, and PRIORITY_CODE govern grouping, lifecycle state, access restrictions, and ranking.

Versioning and lifecycle columns include LATEST_VERSION_FLAG, VIEWABLE_VERSION_FLAG, ORIGINAL_AUTHOR, ORIGINAL_AUTHOR_DATE, START_ACTIVE_DATE, END_ACTIVE_DATE, LOCKED_BY, and LOCK_DATE. Usage metrics are captured in USAGE_SCORE and NORM_USAGE_SCORE, with REINDEX_FLAG supporting search reindexing. Standard audit columns (CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN) and the fifteen ATTRIBUTE (1–15, with ATTRIBUTE_CATEGORY) flex columns are also present.

Common Use Cases and Queries

Knowledge base sets are queried to resolve which sets are active and visible for a given agent, to report on set usage, and to support search and recommendation features. A typical join retrieves the set name together with its type and visibility:

• SELECT s.SET_ID, s.SET_NAME, s.SET_NUMBER, s.STATUS FROM CS.CS_KB_SETS_B s WHERE s.STATUS = 'ACTIVE';
• SELECT s.SET_ID, s.SET_NAME FROM CS.CS_KB_SETS_B s JOIN CS.CS_KB_SET_TYPES_B t ON s.SET_TYPE_ID = t.SET_TYPE_ID WHERE t.SET_TYPE_ID = :type;
• SELECT SET_ID, SET_NAME, USAGE_SCORE FROM CS.CS_KB_SETS_B WHERE GROUP_FLAG = 'Y' AND LATEST_VERSION_FLAG = 'Y' ORDER BY USAGE_SCORE DESC;
• SELECT SET_ID, SET_NAME FROM CS.CS_KB_SETS_B s WHERE s.VISIBILITY_ID IN (SELECT VISIBILITY_ID FROM CS.CS_KB_VISIBILITIES_B) AND s.START_ACTIVE_DATE <= SYSDATE AND (s.END_ACTIVE_DATE IS NULL OR s.END_ACTIVE_DATE >= SYSDATE);

Reporting scenarios include set usage analytics via CS_KB_SET_USED_SUMS, change auditing via CS_KB_SET_CHG_HISTS, and cross-reference reporting through CS_KB_SET_SETS for nested or related set hierarchies.

Related Objects

CS_KB_SETS_B sits at the center of the knowledge base schema, referenced by numerous dependent tables through the SET_ID column, and itself referencing several classification tables:

• CS_KB_SETS_TL — translated set names/descriptions, joined on SET_ID.
• CS_KB_SET_TYPES_B — referenced via SET_TYPE_ID to classify the set.
• CS_KB_VISIBILITIES_B — referenced via VISIBILITY_ID for visibility rules.
• CS_KB_WF_FLOW_DETAILS — referenced via FLOW_DETAILS_ID for workflow linkage.
• FND_SECURITY_GROUPS — referenced via SECURITY_GROUP_ID for security isolation.
• PSB_EMPLOYEES — referenced via EMPLOYEE_ID to attribute ownership.
• CS_KB_SET_ELES and CS_KB_SET_RECS — child tables holding set elements and recommendations.
• CS_KB_SET_PRODUCTS, CS_KB_SET_CATEGORIES, and CS_KB_SET_PLATFORMS — associate sets with products, categories, and platforms.
• CS_KB_SET_SETS — defines parent/child relationships using SET_ID_1 and SET_ID_2.
• CS_KB_SET_USED_SUMS and CS_KB_SET_USED_HISTS — aggregate and historical usage tracking on SET_ID.