Results for “cs_kb_elements_b”

50+ results




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

Overview

CS_KB_ELEMENTS_B is the base table that stores knowledge base elements within the Oracle E-Business Suite Service (CS) module. In Oracle EBS 12.1.1 and 12.2.2, the Knowledge Base feature allows organizations to author, categorize, and publish reusable solution content — articles, resolutions, FAQ entries, and related knowledge objects — that service agents and customers can search and retrieve. Every knowledge base element defined in the system has a single controlling row in CS_KB_ELEMENTS_B, making this table the central anchor for the knowledge management data model.

The _B suffix indicates that this is the base (non-translated) table, paired with a corresponding _TL table that holds language-dependent, translatable columns. The physical schema documented for ETRM 12.2.2 shows an owner of CS and 35 columns, with a unique index CS_KB_ELEMENTS_B_U1 on ELEMENT_ID and primary key constraint CS_KB_ELEMENTS_B_PK on the same column.

From a Data Vault modeling perspective, the FK structure mined for this object classifies it as hub-leaning. This is a heuristic suggestion rather than a physical property of the table: CS_KB_ELEMENTS_B carries the durable business key of each knowledge element and is referenced by numerous surrounding tables, which is characteristic of a hub entity surrounded by satellite and link structures in a Data Vault design.

Key Information Stored

The table centers on the surrogate primary key ELEMENT_ID, which uniquely identifies each knowledge base element and is also the documented business-key candidate via the unique index CS_KB_ELEMENTS_B_U1. The human-readable identifier is ELEMENT_NAME, supplemented by ELEMENT_NUMBER for numbering conventions.

Common Use Cases and Queries

Typical reporting scenarios include listing all active knowledge elements by type, auditing element lifecycles, and identifying elements pending reindexing after bulk content changes. A representative query joining the base and translated tables is:

  • SELECT e.element_id, e.element_name, e.status, t.name FROM cs_kb_elements_b e, cs_kb_elements_tl t WHERE e.element_id = t.element_id AND e.status = 'ACTIVE';
  • SELECT e.element_id, e.element_name FROM cs_kb_elements_b e WHERE e.reindex_flag = 'Y'; — to drive search reindexing jobs.
  • SELECT e.element_id, e.element_name, e.locked_by, e.lock_date FROM cs_kb_elements_b e WHERE e.locked_by IS NOT NULL; — to identify elements held under an editing lock.
  • SELECT e.element_id, e.element_name FROM cs_kb_elements_b e WHERE TRUNC(SYSDATE) BETWEEN e.start_active_date AND NVL(e.end_active_date, SYSDATE); — to retrieve currently effective elements.

Because the table carries SECURITY_GROUP_ID, any custom reporting should ordinarily be filtered through the appropriate security group to respect data segregation.

Related Objects

CS_KB_ELEMENTS_B participates in a dense web of relationships, both as a referencing and a referenced table.

  • CS_KB_ELEMENT_TYPES_B — referenced by CS_KB_ELEMENTS_B.ELEMENT_TYPE_ID; defines element classifications.
  • CS_KB_ELEMENTS_TL — references ELEMENT_ID; stores the translated name and description columns.
  • CS_KB_ELEMENT_LINKS — references ELEMENT_ID; models relationships or links between knowledge elements.
  • CS_KB_ELE_ATTR_VALS — references ELEMENT_ID; stores attribute values attached to elements.
  • CS_KB_ELE_CHG_HISTS — references ELEMENT_ID; records change history for elements.
  • CS_KB_ELE_ELES — references ELEMENT_ID via both ELEMENT_ID_1 and ELEMENT_ID_2; defines element-to-element associations.
  • CS_KB_SET_ELES — references ELEMENT_ID; associates elements with knowledge sets.
  • FND_SECURITY_GROUPS — referenced by CS_KB_ELEMENTS_B.SECURITY_GROUP_ID; enforces security-group segregation.

Together these objects form the complete knowledge base content model, with CS_KB_ELEMENTS_B serving as the central hub and all dependent tables joining through ELEMENT_ID.