Search Results cs_kb_sets_s

Overview

CSK_SETUP_UTILITY_PKG is a PL/SQL setup and seed-data utility belonging to the Oracle E-Business Suite Customer Service (CSK) knowledge management schema. In Oracle EBS 12.1.1 and 12.2.2, it is owned by the APPS schema and classified as an "OTHER" API, meaning it is intended for internal seed and setup operations rather than as a published or supported public interface. Its principal role is to provision and maintain the base configuration records required by the CS Knowledge Base: category groups, solution/set types, set and element definitions, and their associated translated (TL) and denormalized (denorm) rows.

The header of the package body (csktsub.pls, version 120.0, dated 2005/06/01) indicates the package predates the multi-org and later knowledge management refactorings. Notably, the seed insertion procedures write a fixed CREATED_BY / LAST_UPDATED_BY of -1351, the conventional seeded-user identifier used throughout EBS seed data, and populate translation rows for every installed language via a FND_LANGUAGES select with a NOT EXISTS guard. This design makes the package idempotent with respect to language rows, which is important when setup routines are run repeatedly during patching or fresh installs.

Key Procedures and Functions

The ETRM metadata documents twelve procedures and functions. The CREATE_* and DELETE_* procedures manage the lifecycle of knowledge base setup entities:

• VALIDATE_SEEDED_SETUPS — verifies that the expected seeded category groups, solution types, and set types are present and consistent, typically invoked as a post-install or diagnostic step.
• CREATE_CATEGORY / DELETE_CATEGORY — insert and remove category group base, translation, and denormalized records.
• CREATE_SOLUTION / DELETE_SOLUTION / OBSOLETE_SOLUTION — manage knowledge base solution (set) definitions; the obsolete variant marks an existing solution as inactive rather than physically deleting it.
• GET_NEXT_SET_ID, GET_NEXT_SET_NUMBER, GET_NEXT_ELEMENT_ID, GET_NEXT_ELEMENT_NUMBER, and GET_NEXT_CATEGORY_ID — ID and numbering utility functions that supply the next available surrogate key or user-visible sequence number for sets, elements, and categories.
• CALCULATE_SET_INDEX_CONTENT — computes the denormalized content of a set index, supporting the CS_KB_CAT_GROUP_DENORM and related denormalization tables used to accelerate knowledge base lookups.

Parameter lists are not reproduced here; the excerpt confirms that the category and solution type creation procedures accept numeric ID and name (VARCHAR2) parameters.

Tables Accessed

The package reads and writes the core CS Knowledge Base model through APPS synonyms, including CS_KB_CATEGORY_GROUPS_B and its _TL translation table, CS_KB_CAT_GROUP_DENORM, and CS_KB_CAT_GROUP_MEMBERS for category composition. Solution and set data live in CS_KB_SETS_B, CS_KB_SETS_S, and CS_KB_SETS_TL, with membership in CS_KB_SET_CATEGORIES. Element definitions are held in CS_KB_ELEMENTS_B, CS_KB_ELEMENTS_S, and CS_KB_ELEMENTS_TL, with element types in CS_KB_ELEMENT_TYPES_B and _TL, numbering in CS_KB_ELEMENT_NUMBER_S, and cross-references in CS_KB_SET_ELES. The _B tables hold base columns, the _TL tables hold language-specific names and descriptions, and the _S tables hold translated or sequence attributes.

Usage Notes

CSK_SETUP_UTILITY_PKG is not a user-facing API. It is invoked during knowledge base setup, patching, and seed-data maintenance, generally from other Oracle Customer Service packages (the metadata records two referencing packages) or from internal concurrent initialization routines rather than from Oracle Forms. Custom code should not depend on it, because the fixed seeded-user IDs, direct table inserts, and lack of public API designation mean its behavior is unsupported and may change between point releases. When the user searches for create_visibility, it should be noted that no such procedure exists in the documented procedure list; visibility-related setup for knowledge base categories is more likely to be handled by other CSK configuration packages or by direct updates to the category group tables. In 12.2.2 the object remains valid, and the underlying CS_KB tables are the same as those used in 12.1.1, so the package continues to function as a setup utility, though it should be treated strictly as internal metadata.