Search Results delete_set_link

Overview

CS_KB_SET_LINKS_PKG is an Oracle E-Business Suite PL/SQL package owned by the APPS schema that manages the association records, or "links," between knowledge base solution sets and other business objects within the Oracle Knowledge Management and iSupport (TeleService) framework. Its role is to maintain the CS_KB_SET_LINKS and CS_KB_SET_LINKS_S tables, which store the relationships that connect a solution set (CS_KB_SETS_B) to related objects such as other solution sets, service requests, or business entities identified by an object code. The package exposes a set of programmatic APIs for cloning, creating, updating, and deleting these links, and it raises workflow or business events when a solution becomes linked.

In Oracle EBS 12.1.1 and 12.2.2, the package is classified as an "OTHER" API. It is referenced by three other packages, indicating it functions as a dependent utility layer used by higher-level knowledge management processing rather than as a standalone end-user interface.

Key Procedures and Functions

The package documents thirteen callable elements. The principal routines govern the lifecycle of a set link:

• CLONE_LINK — a function that copies an existing link relationship from a source set to a target set, using the set source and target identifiers as the basis for duplication.
• CREATE_SET_LINK — an overloaded procedure (with both a procedure version and a function version) that establishes a new link between a set and another object, accepting a link type, object code, set identifier, and other identifier, along with a flexible descriptive flexfield attribute category and 15 attribute columns.
• CREATE_SET_EXT_LINK — creates an extended variant of a set link, providing handling for extended link definitions.
• UPDATE_SET_LINK — modifies the attributes or properties of an existing set link.
• DELETE_SET_LINK_W_OBJ_CODE — deletes a set link where the object code is supplied as part of the identifying criteria.
• DELETE_SET_LINK — removes a set link using its primary identifying information.
• INSERT_ROW — a low-level routine that performs the physical insert into the underlying link table.
• UPDATE_ROW — a low-level routine that performs the physical update against the underlying link table.
• RAISE_SOLUTION_LINKED_EVENT — the routine relevant to the search term "raise_solution_linked_event"; it raises the business event that signals a solution has been linked, making it available to downstream subscribers and workflow processing.
• RAISE_SOLN_LINK_UPDATED_EVENT — raises the corresponding event when an existing solution link is updated.

The package defines two status constants, ERROR_STATUS (-1) and OKAY_STATUS (0), used to interpret return values from the API calls.

Tables Accessed

The package reads and writes several documented tables through APPS synonyms. CS_KB_SETS_B is the base table for solution sets, serving as the anchor for the link relationships. CS_KB_SET_LINKS and its companion CS_KB_SET_LINKS_S store the link definitions and their translated or secured counterparts. JTF_OBJECT_USAGES supports the object-code framework that classifies linkable business entities. WF_PARAMETER_LIST_T is used to assemble parameter lists, consistent with the package's role in raising workflow-related events. DBMS_SQL, DUAL, and PLITBLM are referenced for dynamic SQL, singleton value retrieval, and PL/SQL table bulk processing respectively.

Usage Notes

CS_KB_SET_LINKS_PKG is invoked programmatically rather than through a direct end-user form. It is typically called by parent knowledge management packages that manage solution sets, by custom extensions that need to relate a solution set to another object, and by any process that must trigger the solution-linked or solution-link-updated business events. The RAISE_SOLUTION_LINKED_EVENT routine is of particular interest when integrating with Oracle Workflow or event subscription, because it publishes the link notification after a create operation succeeds. Because three other packages reference this package, changes to its signature can cascade across the knowledge management module. Custom code should honor the ERROR_STATUS and OKAY_STATUS return conventions and inspect the OUT message parameters for diagnostics.