Search Results cs_kb_histories_b




Overview
Explore in AI Chat

Overview

The CS_KB_HISTORIES_B table is a core data object within the Oracle E-Business Suite Service (CS) module, specifically supporting its knowledge management functionality. As a base table, it serves as the primary repository for audit trail records related to activities within the knowledge base. Its fundamental role is to capture a chronological log of events, providing a historical record that is essential for tracking changes, usage, and modifications to knowledge articles and their associated elements. This audit capability is critical for maintaining data integrity, supporting compliance, and enabling analysis of knowledge base evolution and user interaction over time.

Key Information Stored

While the provided metadata does not list all columns, the structure and foreign keys indicate the core data stored. The primary key column, HISTORY_ID, uniquely identifies each historical event record. A critical foreign key, USER_ID, references FND_USER, linking each history entry to the application user who performed the action. The table's purpose as a base table suggests it holds fundamental attributes common to all history types, such as timestamps, action types, and references to the object being acted upon. More specific details of the change or usage are stored in related transactional tables (like CS_KB_SET_CHG_HISTS or CS_KB_ELE_CHG_HISTS), which link back to this base record via the HISTORY_ID.

Common Use Cases and Queries

This table is central to audit and reporting functions within the knowledge base. Common use cases include generating reports on knowledge article modification frequency, identifying top contributors or editors, and tracing the complete change history of a specific solution or article set. A typical query might join CS_KB_HISTORIES_B with FND_USER to display a user-friendly audit log, or with a transactional table like CS_KB_SET_CHG_HISTS to analyze specific changes to solution sets. For example, a query to find recent modifications might follow this pattern:

  • SELECT h.HISTORY_ID, u.USER_NAME, h.CREATION_DATE
  • FROM CS_KB_HISTORIES_B h, FND_USER u
  • WHERE h.USER_ID = u.USER_ID
  • AND h.CREATION_DATE > SYSDATE - 30
  • ORDER BY h.CREATION_DATE DESC;

Related Objects

As indicated by the foreign key relationships, CS_KB_HISTORIES_B is a central hub for several specialized history tables. The base history record is extended by CS_KB_SET_CHG_HISTS for solution set changes, CS_KB_ELE_CHG_HISTS for element changes, and CS_KB_SET_USED_HISTS for tracking solution usage. The CS_KB_HISTORIES_TL table provides translated descriptions for the history records. Furthermore, the table has a mandatory dependency on the FND_USER table to resolve the user identifier. This structure allows the application to maintain a normalized audit model where common data is stored once in the base table, with specific details segmented into related entities.