Search Results cs_kb_ele_attr_vals_pk

Overview

The CS_KB_ELE_ATTR_VALS table is a foundational data structure within the Oracle E-Business Suite (EBS) Service (CS) module, specifically designed for the Knowledge Base functionality. Its primary role was to implement a many-to-many relationship between knowledge base elements (CS_KB_ELEMENTS_B) and their associated attribute values (CS_KB_ATTR_VALS_B). This relationship allowed a single element to be linked to multiple attribute values and a single attribute value to be associated with multiple elements, providing a flexible data model for categorizing and describing knowledge artifacts. Crucially, the provided ETRM metadata explicitly states this table has been "Not used since before 11.5.8." This indicates that for both EBS 12.1.1 and 12.2.2, the table is a legacy artifact, likely superseded by a different data model in later releases of the knowledge base features. Its presence in the database schema is primarily for backward compatibility and data reference, but it is not actively populated or maintained by the application code in these versions.

Key Information Stored

The table's structure is minimal, consisting essentially of two foreign key columns that form its composite primary key. The ELEMENT_ID column stores a reference to a unique record in the CS_KB_ELEMENTS_B table, identifying a specific knowledge base element. The ATTRIBUTE_VAL_ID column stores a reference to a unique record in the CS_KB_ATTR_VALS_B table, identifying a specific predefined attribute value. The combination of these two IDs forms the unique key (CS_KB_ELE_ATTR_VALS_PK) for each row, representing one specific linkage between an element and an attribute value. No other descriptive columns are present, as the table serves purely as a relationship junction.

Common Use Cases and Queries

Given its deprecated status, there are no active application use cases for this table in EBS 12.1.1 or 12.2.2. Its primary relevance is for technical consultants or DBAs performing historical data analysis, data migration, or schema cleanup projects. Sample queries would be investigative in nature. For instance, to check for any residual data, one might execute: SELECT COUNT(*) FROM cs.cs_kb_ele_attr_vals;. To understand the historical relationships, a join query retrieving element and attribute details would be used:

SELECT e.element_id, e.name element_name, av.attribute_val_id, av.name attribute_value_name FROM cs.cs_kb_ele_attr_vals eav JOIN cs.cs_kb_elements_b e ON eav.element_id = e.element_id JOIN cs.cs_kb_attr_vals_b av ON eav.attribute_val_id = av.attribute_val_id;

Reporting against this table is not a standard practice in current implementations.

Related Objects

The table has defined foreign key relationships with two core knowledge base tables, as documented in the ETRM metadata:

• CS_KB_ELEMENTS_B: The table is linked via the ELEMENT_ID column. This table stores the master definitions of knowledge base elements.
• CS_KB_ATTR_VALS_B: The table is linked via the ATTRIBUTE_VAL_ID column. This table stores the valid values for attributes that could be assigned to elements.

These relationships enforce referential integrity for any historical data that remains. The table itself is not referenced by other application objects like views or APIs in the active 12.x codebase, consistent with its deprecated nature.