Results for “platform_id”

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

Overview

CS_KB_SET_PLATFORMS is a Service (CS) module table that implements the linking relationship between knowledge base sets and the platforms on which those sets are published or made available. In Oracle EBS 12.1.1 and 12.2.2, the knowledge base is the repository of solutions, notes, and articles used by call center and field service agents. A "set" (defined in CS_KB_SETS_B) groups knowledge content for authoring, translation, and publishing purposes, while platform records describe the deployment targets, such as environments, channels, or service organizations. CS_KB_SET_PLATFORMS resolves the many-to-many association between these two entities.

From a Data Vault modeling perspective, the mined foreign key structure classifies this table as satellite-leaning. It carries descriptive and contextual attributes around a composite association rather than acting as a pure hub of business keys. Modelers treating the knowledge base domain analytically may therefore treat CS_KB_SET_PLATFORMS as a link table with satellite characteristics, where the (SET_ID, PLATFORM_ID, PLATFORM_ORG_ID) tuple forms the link's unique grain and the audit columns provide change-tracking value.

Key Information Stored

The table is defined in the CS schema and contains nine documented columns. Its distinguishing structural feature is a composite primary key, CS_KB_S_PL_PK, defined over three columns rather than a single surrogate identifier:

• SET_ID — Identifies the knowledge base set being linked. This is a foreign key to CS_KB_SETS_B and forms the first component of the primary key.
• PLATFORM_ID — Identifies the platform to which the set is associated. It forms the second component of the primary key.
• PLATFORM_ORG_ID — Carries the operating unit or organization context for the platform association. It forms the third component of the primary key and allows the same platform to be related to a set within multiple organizational contexts.
• SECURITY_GROUP_ID — Supports Oracle EBS multi-tenant and security-group partitioning. It references FND_SECURITY_GROUPS and is used by row-level security and data access filtering.
• CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN — Standard Oracle EBS audit columns recording who created and last modified each association and when. These columns support auditing and are useful as extraction high-water marks in incremental ETL.

The composite primary key CS_KB_S_PL_PK functions as the effective unique identifier; there is no single surrogate sequence column. Business-key uniqueness is enforced by the combination of SET_ID, PLATFORM_ID, and PLATFORM_ORG_ID.

Common Use Cases and Queries

Typical usage centers on determining which platforms publish a given knowledge set, or which sets are available on a given platform. A frequently used query joins the linking table to the set definition:

• Listing all platforms for a knowledge set: SELECT p.PLATFORM_ID, p.PLATFORM_ORG_ID FROM CS_KB_SET_PLATFORMS p WHERE p.SET_ID = :set_id;
• Identifying knowledge sets published to a specific platform within an operating unit: SELECT p.SET_ID FROM CS_KB_SET_PLATFORMS p WHERE p.PLATFORM_ID = :platform_id AND p.PLATFORM_ORG_ID = :org_id;
• Reporting recently added platform associations using the audit columns: SELECT SET_ID, PLATFORM_ID FROM CS_KB_SET_PLATFORMS WHERE CREATION_DATE >= :start_date;
• Joining to CS_KB_SETS_B to retrieve set names and descriptions for a platform inventory report.
• Incremental extraction for a data warehouse, filtering on LAST_UPDATE_DATE and SECURITY_GROUP_ID to respect access controls.

Because PLATFORM_ORG_ID participates in the primary key, multi-organization reporting must include that column in join predicates to avoid duplicate or incorrect rows.

Related Objects

The following objects are the most significant in relation to CS_KB_SET_PLATFORMS:

• CS_KB_SETS_B — The base knowledge set table, joined on SET_ID. It provides set name, description, and other header attributes.
• FND_SECURITY_GROUPS — Referenced through SECURITY_GROUP_ID and used to enforce multi-organization data security.
• CS_KB_SETS_TL — The translated set definitions, providing language-specific set names and descriptions for reporting.
• CS_KB_ARTICLES / knowledge content tables — Content belonging to sets, for end-to-end tracing from platform to article.
• FND_ORG_ACCESS / HR_OPERATING_UNITS — Used to resolve PLATFORM_ORG_ID into a recognizable organization name.
• CS_KB_PLATFORM-level reference tables — Provide platform names for user-facing queries on PLATFORM_ID.

Developers and analysts should treat the FK relationships above as the authoritative join paths and always constrain on SET_ID and PLATFORM_ID together when validating knowledge base publishing configurations.