Results for “cs_kb_set_ele_types”
50+ results
AI-generated from documented ETRM metadata — verify critical details on the linked pages.
Overview
CS_KB_SET_ELE_TYPES is a Service (CS) module table in Oracle E-Business Suite 12.1.1 and 12.2.2 that stores knowledge base set element types. It implements the many-to-many relationship between set types and element types, allowing a single set type to be associated with multiple element types and vice versa. In the Service knowledge base model, set types define reusable groupings (for example, a diagnostic set or a resolution set), while element types describe the individual components that populate those groupings. This table is the associative bridge that binds the two masters together and controls ordering and optionality of the constituent elements.
From a data-modeling perspective, the ETRM metadata classifies this object heuristically as a link table. Its grain is one row per set-type/element-type combination, which is consistent with a link construct between two hubs (CS_KB_SET_TYPES_B and CS_KB_ELEMENT_TYPES_B). This classification is a modeling suggestion derived from the foreign-key structure rather than a mandated implementation.
Key Information Stored
The table contains 27 documented columns. The most significant are:
- SET_TYPE_ID — Foreign key to CS_KB_SET_TYPES_B; identifies the parent set type.
- ELEMENT_TYPE_ID — Foreign key to CS_KB_ELEMENT_TYPES_B; identifies the element type associated with the set.
- ELEMENT_TYPE_ORDER — Controls the sequence in which element types appear within the set, supporting deterministic presentation and evaluation order.
- OPTIONAL_FLAG — Indicates whether the element type is mandatory or optional when the set is used.
- SECURITY_GROUP_ID — Foreign key to FND_SECURITY_GROUPS; enforces multi-tenant/security-group data isolation.
- ZD_EDITION_NAME — Editioning column used in the 12.2 online patching architecture.
- CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN — Standard EBS WHO columns for audit and concurrency tracking.
- ATTRIBUTE_CATEGORY and ATTRIBUTE1 through ATTRIBUTE15 — Descriptive flexfield (DFF) columns for customer-specific extensions.
The composite primary key CS_KB_SET_ELE_TYPES_PK is defined on (SET_TYPE_ID, ELEMENT_TYPE_ID). A unique index, CS_KB_SET_ELE_TYPES_U1 on (SET_TYPE_ID, ELEMENT_TYPE_ID, ZD_EDITION_NAME), serves as the business-key candidate in the editioning model. There is no single-column surrogate key; the association itself is the identifier.
Common Use Cases and Queries
Typical usage revolves around enumerating the elements that belong to a given set type, in order, and determining which are optional. A common query joins through the set type master:
- Resolving element membership:
SELECT ELEMENT_TYPE_ID, ELEMENT_TYPE_ORDER, OPTIONAL_FLAG FROM CS_KB_SET_ELE_TYPES WHERE SET_TYPE_ID = :set_type_id ORDER BY ELEMENT_TYPE_ORDER; - Reverse lookup — finding sets that contain a given element: filter on ELEMENT_TYPE_ID.
- Reporting on mandatory versus optional composition using OPTIONAL_FLAG counts grouped by set type.
- Validating configuration integrity, for example detecting sets with no member elements or orphaned associations.
- Extracting DFF values from ATTRIBUTE columns for customer-specific set/element rules.
Because this is a link table with no standalone descriptive identity, reporting views generally join it to CS_KB_SET_TYPES_B and CS_KB_ELEMENT_TYPES_B to present human-readable names.
Related Objects
The most significant related objects are its referenced parents and the security-group lookup:
- CS_KB_SET_TYPES_B — joined on SET_TYPE_ID; provides the set type master record.
- CS_KB_ELEMENT_TYPES_B — joined on ELEMENT_TYPE_ID; provides the element type master record.
- FND_SECURITY_GROUPS — joined on SECURITY_GROUP_ID; governs row-level access.
- CS_KB_SET_ELE_TYPES_PK and CS_KB_SET_ELE_TYPES_U1 — the primary and unique indexes enforcing association uniqueness and editioning.
Dependent application logic in the Service knowledge base references this association when assembling sets for authoring, browsing, or solution generation. Administrators should treat the table as a controlled association store and perform maintenance through supported Service application flows rather than direct DML.
-
Knowledge base set element types. This table implements the many to many relationship between set types and element types.
-
Knowledge base set element types. This table implements the many to many relationship between set types and element types.
-
12.2.2 DBA Data 12.2.2
-
12.2.2 DBA Data 12.2.2
-
12.2.2 DBA Data 12.2.2
-
12.1.1 FND Design Data 12.1.1