Results for “cs_kb_set_links_u1”

AI-generated from documented ETRM metadata — verify critical details on the linked pages.

Overview

CS_KB_SET_LINKS is a Service (CS) module table in Oracle E-Business Suite 12.1.1 and 12.2.2 that stores the knowledge base set links. As described in the ETRM metadata, the table implements the one-to-many relationship between a knowledge base "set" and external entities. In practical terms, it acts as the association table that records which external objects (identified by an OBJECT_CODE) belong to a given knowledge set (identified by SET_ID), enabling knowledge content to be grouped and reused across the service organization.

From a data modeling perspective, the heuristic Data Vault classification mined from the foreign-key structure suggests that CS_KB_SET_LINKS behaves as a link entity. It sits between CS_KB_SETS_B (the set/parent) and JTF_OBJECTS_B (the referenced external object), resolving the many-to-many-style association into a concrete linkage with additional descriptive attributes. This classification aligns with its documented purpose of implementing one-to-many relationships.

Key Information Stored

The table contains 28 documented columns. The most significant are the keys and linkage identifiers:

• LINK_ID — the surrogate primary key defined by CS_KB_SET_LINKS_PK. It also appears in the unique index CS_KB_SET_LINKS_U1, confirming its uniqueness.
• SET_ID — foreign key to CS_KB_SETS_B, identifying the knowledge set to which the link belongs.
• OBJECT_CODE — foreign key to JTF_OBJECTS_B, identifying the external entity type being linked.
• OTHER_ID — the specific external entity instance being referenced; combined with OBJECT_CODE and SET_ID in unique index CS_KB_SET_LINKS_U2, this forms the business-key candidate guaranteeing that a given set links to a given object instance only once.
• OBJECT_NUMBER — a supplemental object reference attribute.
• LINK_TYPE — categorizes the nature of the link between the set and the external entity.
• SECURITY_GROUP_ID — supports multi-org/security-group data partitioning, referencing FND_SECURITY_GROUPS.
• CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN — standard WHO audit columns tracking record creation and maintenance.
• ATTRIBUTE_CATEGORY and ATTRIBUTE1 through ATTRIBUTE15 — the standard Oracle descriptive flexfield (DFF) columns for extensible, customer-defined attributes.

The distinction between the surrogate key (LINK_ID) and the composite business key (OTHER_ID, OBJECT_CODE, SET_ID) is important for reconciliation and integration work.

Common Use Cases and Queries

Typical reporting scenarios include determining which external entities are attached to a knowledge set, or conversely which sets reference a particular object. A representative join query is:

• SELECT l.LINK_ID, l.SET_ID, l.OBJECT_CODE, l.OTHER_ID FROM CS.CS_KB_SET_LINKS l WHERE l.SET_ID = :set_id; — list all links for a set, joined as needed to CS_KB_SETS_B.
• SELECT l.* FROM CS.CS_KB_SET_LINKS l, CS.CS_KB_SETS_B s WHERE l.SET_ID = s.SET_ID AND s.NAME = :name; — resolve links by set name.
• SELECT l.* FROM CS.CS_KB_SET_LINKS l WHERE l.OBJECT_CODE = :code AND l.OTHER_ID = :id; — find the sets that reference a specific external object.

These patterns support knowledge base configuration audits, content mapping reports, and data migration validation using unique index CS_KB_SET_LINKS_U2 to detect duplicates.

Related Objects

• CS_KB_SETS_B — parent set table; joined via SET_ID.
• JTF_OBJECTS_B — external object registry; joined via OBJECT_CODE.
• FND_SECURITY_GROUPS — referenced through SECURITY_GROUP_ID for security-group partitioning.
• CS_KB_SETS_TL — translation table typically used alongside CS_KB_SETS_B for descriptive set names.
• CS_KB_SET_LINKS_PK / U1 / U2 — the primary key and unique index definitions enforcing identity and business-key uniqueness.

Together these objects form the knowledge set linking model, with CS_KB_SET_LINKS serving as the central association table.