Search Results cs_kb_set_chg_hists_pk

Overview

The CS_KB_SET_CHG_HISTS table is a technical entity within the Oracle E-Business Suite (EBS) Service (CS) module, specifically designed for the Knowledge Base (KB) functionality. Its primary role was to implement a many-to-many relationship between knowledge base sets (CS_KB_SETS_B) and change history records (CS_KB_HISTORIES_B). This structure would have allowed a single set to be associated with multiple history entries and vice versa, tracking changes over time. However, a critical piece of documented information is that this table has been deprecated for a significant period. As explicitly stated in the ETRM documentation, it has been "Not used since before 11.5.8." Consequently, in releases 12.1.1 and 12.2.2, this table is a legacy artifact with no active data or functional purpose within the application's operational logic.

Key Information Stored

The table's structure is minimal, consisting solely of two foreign key columns that form a composite primary key. The SET_ID column references the primary key of the CS_KB_SETS_B table, identifying a specific knowledge base set. The HISTORY_ID column references the primary key of the CS_KB_HISTORIES_B table, identifying a specific change history record. The combination of these two columns (enforced by the CS_KB_SET_CHG_HISTS_PK primary key constraint) would have uniquely defined a relationship instance. Given the table's deprecated status, these columns would not contain any application-generated data in a standard EBS 12.1.1 or 12.2.2 environment.

Common Use Cases and Queries

As an obsolete table, there are no standard application-driven use cases, reporting requirements, or data manipulation operations involving CS_KB_SET_CHG_HISTS in modern implementations. Any data found within it would be residual from a pre-11.5.8 installation. Therefore, standard queries for reporting or integration should not reference this object. If encountered during a data audit or migration analysis, the only relevant query would be to confirm its empty state. A sample validation check would be:

• SELECT COUNT(*) FROM apps.CS_KB_SET_CHG_HISTS;

Administrators and developers should treat this table as inactive and exclude it from any new customizations, data extracts, or upgrade considerations.

Related Objects

The table's relationships are defined entirely by its foreign key constraints, linking it to two other knowledge base tables. The first is CS_KB_SETS_B, which stores the definition of knowledge base sets. The second is CS_KB_HISTORIES_B, which was intended to store history records. Like CS_KB_SET_CHG_HISTS, the CS_KB_HISTORIES_B table is also documented as unused since before the 11.5.8 release, indicating a broader architectural change in how the Knowledge Base managed change tracking. The CS_KB_SETS_B table, however, remains a core object. The existence of these foreign keys is important for understanding the historical data model but does not imply active data relationships in current EBS versions.