Search Results set_id_2

Overview

The CS_KB_SET_SETS table is a legacy data object within the Oracle E-Business Suite (EBS) Service (CS) module. Its primary purpose was to model a many-to-many relationship between knowledge base sets, a feature of the application's knowledge management functionality. This structure would have allowed a single set of knowledge content to be associated with multiple parent sets, or for sets to be nested in complex hierarchies. However, as explicitly stated in the official ETRM documentation, this table has been deprecated and is not in use. The metadata indicates it has been inactive since a version prior to Oracle EBS 11.5.8. In the context of releases 12.1.1 and 12.2.2, this table exists as a historical artifact within the CS schema and holds no functional role in the active application.

Key Information Stored

The table's structure is minimal, serving solely to link two sets together. The two key columns are both foreign keys referencing the primary knowledge base sets table. The primary key is a composite of these two columns, enforcing uniqueness in the relationship. No additional descriptive columns are present, as the table's sole purpose was to establish the relationship link itself.

• SET_ID_1: A foreign key column referencing the CS_KB_SETS_B table. Represents one side of the set-to-set relationship.
• SET_ID_2: A foreign key column also referencing the CS_KB_SETS_B table. Represents the other side of the set-to-set relationship.

Common Use Cases and Queries

Given its deprecated status, there are no active business or reporting use cases for this table in Oracle EBS 12.1.1 or 12.2.2. Any data present is legacy and not maintained by the application. Consequently, no standard application queries, reports, or APIs interact with this table. Investigation of this object would typically occur only during data migration audits, deep historical analysis of very old data, or while reviewing schema dependencies. A sample query to examine any residual data would be a simple select statement, such as: SELECT set_id_1, set_id_2 FROM cs.cs_kb_set_sets;. For any functional requirements involving knowledge base sets in current implementations, one must consult the active core tables, primarily CS_KB_SETS_B and its related entities.

Related Objects

The relationships for CS_KB_SET_SETS are clearly defined by its foreign key constraints, both pointing to the core sets table. There are no other documented tables with foreign keys referencing CS_KB_SET_SETS, consistent with its inactive status.

• CS_KB_SETS_B: The primary knowledge base sets table. CS_KB_SET_SETS.SET_ID_1 references CS_KB_SETS_B via a foreign key constraint.
• CS_KB_SETS_B: The same core table is referenced again. CS_KB_SET_SETS.SET_ID_2 references CS_KB_SETS_B via a separate foreign key constraint, completing the many-to-many link.