Search Results cs_kb_set_used_sums_pk

Overview

The CS_KB_SET_USED_SUMS table is a core data object within the Oracle E-Business Suite Service (CS) module, specifically supporting the Knowledge Base (KB) functionality. It serves as a summary repository for tracking the usage frequency of knowledge base sets over defined time periods. Its primary role is to aggregate and persist "used count" metrics, enabling performance analysis, popularity trending, and reporting on knowledge assets. This data is critical for administrators and analysts to identify high-value content, measure the effectiveness of the knowledge base, and make informed decisions about content maintenance and curation. The table operates in conjunction with a definition table that controls the summarization periods.

Key Information Stored

The table's structure is designed to store summarized usage counts keyed by two primary identifiers. The SET_ID column stores the unique identifier for a specific knowledge base set, linking to the CS_KB_SETS_B table. The DEF_ID column stores the identifier for the summarization definition period, linking to the CS_KB_USED_SUM_DEFS_B table. The combination of these two columns forms the table's primary key (CS_KB_SET_USED_SUMS_PK), ensuring a unique record for each set and period combination. While the provided metadata does not list all columns explicitly, the core data point stored is the aggregated "used count" for the specified set over the timeframe defined by DEF_ID. This count represents the total number of times the knowledge set was accessed or utilized during that period.

Common Use Cases and Queries

A primary use case is generating reports on knowledge base article or solution popularity over weekly, monthly, or quarterly periods. This helps support organizations prioritize updates for frequently used content and retire obsolete material. Another scenario involves data purging or archival processes, where old summary records beyond a certain age can be identified and managed. Common SQL queries typically join this summary table with the set and definition tables to produce readable reports.

For example, a query to retrieve usage summaries for a specific period might follow this pattern:

• SELECT s.SET_NUMBER, d.PERIOD_NAME, sum.USED_COUNT
• FROM CS_KB_SET_USED_SUMS sum,
• CS_KB_SETS_B s,
• CS_KB_USED_SUM_DEFS_VL d
• WHERE sum.SET_ID = s.SET_ID
• AND sum.DEF_ID = d.DEF_ID
• AND d.PERIOD_NAME = 'WEEK-2024-10';

Related Objects

The CS_KB_SET_USED_SUMS table has defined foreign key relationships with two central knowledge base tables, as documented in the ETRM metadata.

• CS_KB_SETS_B: This is the base table for knowledge base sets. The foreign key relationship is defined on the column CS_KB_SET_USED_SUMS.SET_ID, which references the primary key in CS_KB_SETS_B. This join provides access to the detailed metadata of the summarized knowledge set.
• CS_KB_USED_SUM_DEFS_B: This is the base table for usage summary definition periods. The foreign key relationship is defined on the column CS_KB_SET_USED_SUMS.DEF_ID, which references the primary key in CS_KB_USED_SUM_DEFS_B. This join provides context for the time period (e.g., week, month) over which the usage count was aggregated.

Additionally, the descriptive view CS_KB_USED_SUM_DEFS_VL, referenced in the table's description, is typically used in queries instead of the base definition table to retrieve user-friendly period names.