Results for “cs_kb_ele_attr_vals”

24 results




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

Overview

CS_KB_ELE_ATTR_VALS is a Service (CS) module table in the Oracle E-Business Suite that stores knowledge base element attribute values. In functional terms, it implements the many-to-many relationship between knowledge base elements and their associated attribute values. The table resides in the CS schema and is documented as VALID in the ETRM repository for releases 12.1.1 and 12.2.2, although Oracle's own documentation notes that it has not been used since before release 11.5.8. This status makes the object primarily of interest for historical data inspection, upgrade assessment, and schema-completeness verification rather than for new development.

From a Data Vault modeling perspective, the heuristic classification for this object is link. This classification is derived from the foreign key structure: the table's two principal columns, ELEMENT_ID and ATTRIBUTE_VAL_ID, each reference a separate parent table, and together they form the composite primary key. A link classification is offered here as a modeling suggestion rather than a prescriptive design; the physical object itself is a conventional intersection table with descriptive and audit columns attached.

Key Information Stored

The documented physical schema comprises 25 columns. The most significant are the following:

The surrogate-style row identity is the composite primary key CS_KB_ELE_ATTR_VALS_PK (ELEMENT_ID, ATTRIBUTE_VAL_ID). A separate unique index, CS_KB_ELE_ATTR_VALS_U1, enforces the same column pair, confirming that the (element, attribute value) pairing is the business-key candidate for this table. No additional natural identifier is documented.

Common Use Cases and Queries

Because the table is obsolete for releases 11.5.8 and later, common use cases center on migration auditing and legacy data reconciliation. A typical validation query confirms whether any residual rows exist for the installation:

  • Row-count check: SELECT COUNT(*) FROM cs.cs_kb_ele_attr_vals; to determine whether legacy knowledge base data was carried forward.
  • Orphan detection: left-join against CS_KB_ELEMENTS_B and CS_KB_ATTR_VALS_B on ELEMENT_ID and ATTRIBUTE_VAL_ID respectively to find rows whose parent records no longer exist.
  • Security-group distribution: SELECT SECURITY_GROUP_ID, COUNT(*) FROM cs.cs_kb_ele_attr_vals GROUP BY SECURITY_GROUP_ID; to assess which operating units or security partitions the legacy rows belong to.
  • Ordering audit: inspecting ATTRIBUTE_VAL_ORDER values to reconstruct the intended display sequence of attribute values for each element.

Reporting on this table is generally limited to data-cleanup scripts, pre-upgrade impact analysis, and archival decisions. It should not be treated as an active transactional source in 12.1.1 or 12.2.2 environments.

Related Objects

The table's referential relationships, as documented, are the most reliable guide to dependent objects:

  • CS_KB_ELEMENTS_B — Parent of ELEMENT_ID; holds the knowledge base element definition.
  • CS_KB_ATTR_VALS_B — Parent of ATTRIBUTE_VAL_ID; holds the attribute value definition.
  • FND_SECURITY_GROUPS — Parent of SECURITY_GROUP_ID; defines the security grouping applied to the row.
  • CS_KB_ELEMENTS_TL and CS_KB_ATTR_VALS_TL — Translated counterparts of the two parent tables, typically joined for language-specific reporting.

No child tables or dependent APIs are documented for this object, consistent with its deprecated status. Consumers should verify current usage against the specific environment before relying on it in any integration or extract.