Search Results cs_kb_set_type_attrs




Overview
Explore in AI Chat

Overview

The CS_KB_SET_TYPE_ATTRS table is a core data structure within the Oracle E-Business Suite Service (CS) module, specifically designed for the Knowledge Base (KB) functionality. Its primary role is to establish and manage a many-to-many relationship between knowledge base set types and attribute types. This relationship defines which attributes are applicable to which types of knowledge sets, enabling a flexible and structured content model. Critically, the official ETRM documentation states this table has been "Not used since before 11.5.8." This indicates that while the table exists in schemas for versions 12.1.1 and 12.2.2, it is a legacy artifact and is not actively referenced or maintained by the application's business logic in these releases.

Key Information Stored

The table's structure is minimal, serving solely as a junction table. The two key columns form a composite primary key and directly implement the relationship. The SET_TYPE_ID column stores the unique identifier for a knowledge set type, linking to the CS_KB_SET_TYPES_B table. The ATTRIBUTE_ID column stores the unique identifier for an attribute type, linking to the CS_KB_ATTRS_B table. The combination of these two IDs defines a single valid pairing, ensuring that a specific attribute can be associated with a specific set type. No other descriptive columns are present, as the table's sole purpose is to maintain this associative relationship.

Common Use Cases and Queries

Given its documented status as unused in current releases, there are no standard application use cases for this table in Oracle EBS 12.1.1 or 12.2.2. Its presence is historical. However, for diagnostic or data cleanup purposes, a developer or DBA might query it to understand legacy data relationships or confirm its emptiness. A sample query to list all existing associations would be:

  • SELECT set_type_id, attribute_id FROM cs.cs_kb_set_type_attrs;

To join with the related descriptive tables for a more comprehensive view, a query might be:

  • SELECT st.name set_type_name, a.name attribute_name FROM cs.cs_kb_set_type_attrs sta JOIN cs.cs_kb_set_types_b st ON sta.set_type_id = st.set_type_id JOIN cs.cs_kb_attrs_b a ON sta.attribute_id = a.attribute_id;

Any data found in this table is likely vestigial and not processed by the application.

Related Objects

The table's relationships are explicitly defined by its foreign key constraints, as documented in the ETRM metadata. It has two primary dependencies:

  • CS_KB_SET_TYPES_B: The foreign key on the SET_TYPE_ID column references this table, which contains the master definitions for knowledge base set types.
  • CS_KB_ATTRS_B: The foreign key on the ATTRIBUTE_ID column references this table, which holds the master definitions for attribute types.

These relationships enforce referential integrity, ensuring that any record in CS_KB_SET_TYPE_ATTRS points to valid, existing entities in the respective master tables. Despite these enforced relationships, the core application code paths no longer utilize this junction table for operational purposes.