Search Results clone_solution
Overview
CS_KB_SOLUTION_PVT is a private PL/SQL package in the APPS schema that encapsulates the core business logic for managing Oracle Knowledge Base solution sets within Oracle E-Business Suite Release 12.1.1 and 12.2.2. It belongs to the Customer Support (CS) product family and functions as the internal engine behind the public Knowledge Base APIs. The package governs the complete solution lifecycle: creation, checkout, update, submission for approval, publishing, cloning, obsoletion, and eventual removal. Its classification as a PVT package indicates that it is not a published integration interface; instead, it is intended for consumption by other APPS packages such as CS_KNOWLEDGE_PVT, CS_KB_SETS_PKG, CS_KB_WF_PKG, CS_KNOWLEDGE_AUDIT_PVT, and CSK_DIAG_SOLUTION_PVT. In total, five dependent packages reference CS_KB_SOLUTION_PVT, and nineteen documented procedures and functions constitute its API surface.
Key Procedures and Functions
- CREATE_SOLUTION / UPDATE_SOLUTION / SUBMIT_SOLUTION — Insert, modify, and submit a solution set for approval, forming the primary authoring workflow.
- CHECKOUT_SOLUTION / UNLOCK_SOLUTION — Manage edit locks so a single author can revise a solution without conflicting concurrent updates.
- CLONE_SOLUTION / OUTDATE_SOLUTION / MOVE_SOLUTIONS — Copy a solution into a new version, retire an obsolete version, and relocate solutions between sets or categories.
- LOCKED_BY / GET_LOCK_INFO / SNATCH_LOCK_FROM_USER — Query lock ownership, retrieve detailed lock context, and administratively override an abandoned lock.
- GET_SET_DETAILS / GET_SET_NUMBER / GET_LATEST_VERSION_ID / GET_PUBLISHED_SET_ID / GET_OBSOLETED_SET_ID — Retrieval utilities for set attributes, numbering, and identification of the latest, published, or obsoleted version.
- GET_SOLUTION_TITLE / GET_USER_SOLN_ACCESS — Return the solution title and validate a user's authorization to access the solution.
Tables Accessed
The package reads and writes the Knowledge Base solution-set schema through APPS synonyms. Header and version data reside in CS_KB_SETS_B and its translation tables CS_KB_SETS_TL; primary-key identifiers and controlled numbering come from CS_KB_SETS_S and CS_KB_SET_NUMBER_S. Classification attributes are held in CS_KB_SET_CATEGORIES, CS_KB_SOLN_CATEGORIES_B, CS_KB_SET_TYPES_B, and CS_KB_VISIBILITIES_B. Element-to-set and set-to-set relationships are maintained in CS_KB_SET_ELES, CS_KB_ELEMENTS_B, and CS_KB_SET_LINKS. Commerce attributes—supported products and platforms—are stored in CS_KB_SET_PRODUCTS and CS_KB_SET_PLATFORMS. DUAL supports single-row lookups and PLITBLM provides APPS-standard list handling.
Usage Notes
CS_KB_SOLUTION_PVT is normally invoked indirectly. Oracle Knowledge Base end-user and authoring forms call the public CS_KNOWLEDGE_PVT or CS_KB_SETS_PKG interfaces, which delegate to this private package. The Oracle Workflow integration in CS_KB_WF_PKG uses it to advance approval and publishing transitions, while CS_KNOWLEDGE_AUDIT_PVT uses it to capture change history. Customers extending the Knowledge Base should avoid calling CS_KB_SOLUTION_PVT directly; because the package is private, its specification is subject to change without notice between point releases. Customizations should instead target the supported public packages or register logic through the documented API layer. For diagnostics, the package remains valuable during troubleshooting: errors surfaced through CS_KB_SOLUTION_PVT during a create, update, or submit operation typically indicate lock contention on a checked-out solution, invalid set-type or category references, or failed workflow submission steps. DBAs should treat it as a core dependency of the Customer Support schema and recompile it after any patch that alters the CS_KB_SET* tables.