Results for “cs_kb_set_used_hists”

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

Overview

CS_KB_SET_USED_HISTS is a Service (CS) module table that stores the usage history of knowledge base sets. A knowledge base set groups related solution articles and is typically presented to support agents as a curated collection of knowledge. This table records when a given set was used in the context of a knowledge base session, providing an audit and analytical trail that links a set to a specific history record. In Oracle EBS 12.1.1 and 12.2.2 the table resides in the CS schema and is documented in the ETRM repository with 26 columns and status VALID.

The heuristic Data Vault classification mined from the foreign key structure is link. This suggests the table functions as an associative entity that resolves a many-to-many style relationship between knowledge base sets and history records, with a session as additional context. Treating it as a link is a modeling suggestion rather than a formal designation; in EBS terms it is best understood as a transactional usage/association table.

Key Information Stored

Each row represents one instance of a knowledge base set being used within a session history. The most significant columns are:

• SET_ID — Identifier of the knowledge base set used; foreign key to CS_KB_SETS_B. Part of the composite primary key.
• HISTORY_ID — Identifier of the history record associated with the usage; foreign key to CS_KB_HISTORIES_B. Part of the composite primary key.
• SESSION_ID — The knowledge base session in which the set was used; foreign key to CS_KB_SESSIONS.
• USED_TYPE — Classifies the manner or type of usage recorded for the set.
• CREATION_DATE, CREATED_BY — Standard WHO columns capturing when and by whom the usage row was created.
• LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN — Standard WHO audit columns for the most recent modification.
• SECURITY_GROUP_ID — Foreign key to FND_SECURITY_GROUPS, supporting multi-org/security group partitioning.
• ATTRIBUTE_CATEGORY and ATTRIBUTE1–ATTRIBUTE15 — The DFF (descriptive flexfield) columns, providing extensibility for customer-specific information.

The surrogate primary key is CS_KB_SET_USED_HISTS_PK over (SET_ID, HISTORY_ID). A unique index, CS_KB_SET_USED_HISTS_U1, is documented over the same columns (SET_ID, HISTORY_ID), making that pair the business-key candidate that prevents duplicate usage rows for the same set/history combination.

Common Use Cases and Queries

Typical uses include measuring knowledge base set effectiveness, auditing which sets were surfaced during a session, and reporting set reuse across agents. A basic query joining to the session and set tables:

• SELECT u.SET_ID, u.HISTORY_ID, u.SESSION_ID, u.USED_TYPE, u.CREATION_DATE FROM CS_KB_SET_USED_HISTS u WHERE u.SESSION_ID = :session_id;
• Usage counts per set: SELECT u.SET_ID, COUNT(*) FROM CS_KB_SET_USED_HISTS u GROUP BY u.SET_ID ORDER BY 2 DESC;
• Join to set base table for names: SELECT s.SET_NAME, COUNT(*) FROM CS_KB_SET_USED_HISTS u, CS_KB_SETS_B s WHERE u.SET_ID = s.SET_ID GROUP BY s.SET_NAME;

These patterns support adoption reporting and troubleshooting of knowledge base set behavior within Service.

Related Objects

• CS_KB_SETS_B — Base table for knowledge base sets; joined via SET_ID.
• CS_KB_HISTORIES_B — Base table for history records; joined via HISTORY_ID.
• CS_KB_SESSIONS — Knowledge base sessions; joined via SESSION_ID.
• FND_SECURITY_GROUPS — Security group definition; joined via SECURITY_GROUP_ID.
• Standard WHO/DFF supporting objects (FND_USER, FND_FLEX_VALUES) for audit and attribute lookups.