Search Results cs_sr_kb_solution_links_v

Overview

CS_SR_KB_SOLUTION_LINKS_V is a read-only database view owned by the APPS schema in Oracle E-Business Suite, delivered as part of the CS (Service) product family. Its documented purpose is to serve as the base view for the notes section of the Workbench tab, presenting Knowledge Base solution notes that are linked to service requests. In release 12.1.1 and 12.2.2 environments the object is registered in the ETRM repository with a VALID status, confirming that it compiles cleanly against the standard schema.

The view exists primarily to support the Service Request Workbench user interface and any downstream reporting or integration logic that must surface the relationship between a service request incident and the Knowledge Base solution sets attached to it. It is not a transactional table and holds no data of its own; instead it joins incident records to the Knowledge Base linking structures and projects a denormalized result that is convenient for display and extraction.

Underlying Base Objects

The view is defined over three principal data sources. CS_INCIDENTS_ALL_B is the incident base table, providing the service request header and its incident number. CS_KB_LINKED_SOLUTIONS_VIEW is itself a view over the Knowledge Base solution structures and supplies the set attributes, visibility, link type, and publication status. CS_KB_SET_LINKS supplies the physical association between a solution set and its related object and contributes the creation date.

The view definition restricts results to object code 'SR', which means only links whose related object is a service request are returned. The joins are constructed so that the incident ID matches the OTHER_ID column in both CS_KB_LINKED_SOLUTIONS_VIEW and CS_KB_SET_LINKS, and additionally so that the SET_ID in each of those two structures matches. Documented dependencies include CS_KB_SECURITY_PVT and FND_GLOBAL, which indicate that Knowledge Base security and session context (such as organization or user) influence the rows visible through the underlying solution view.

Key Columns

• INCIDENT_NUMBER — the service request number from CS_INCIDENTS_ALL_B, used to relate the note back to the incident.
• SET_ID / SET_NUMBER / SET_NAME — identifiers and the display name of the Knowledge Base solution set linked to the incident.
• SET_VISIBILITY_ID / VISIBILITY_NAME — the visibility classification controlling who may view the solution set.
• SET_LINK_TYPE / SET_LINK_TYPE_MEANING — the type of linkage between the incident and the solution set, with its decoded meaning.
• SET_PUBLISHED_STATUS — indicates whether the linked solution set has been published.
• SET_LAST_UPDATE_DATE — the last modification timestamp for the set.
• OBJECT_CODE / OTHER_ID — the related object type (always 'SR' in this view) and its identifier.
• SET_TYPE_NAME — descriptive name of the solution set type.
• CREATION_DATE — creation date of the link from CS_KB_SET_LINKS.

Common Use Cases and Queries

Typical usage centers on reporting which solutions have been attached to a given service request, and on integration scenarios where a solution reference must be resolved from an incident. A simple query returns all linked solutions for a specific incident:

• SELECT incident_number, set_number, set_name, set_link_type_meaning FROM cs_sr_kb_solution_links_v WHERE incident_number = :p_incident;
• Counting links per solution set to identify the most frequently referenced knowledge articles: SELECT set_id, set_name, COUNT(*) FROM cs_sr_kb_solution_links_v GROUP BY set_id, set_name;
• Filtering to published sets only: SELECT incident_number, set_name FROM cs_sr_kb_solution_links_v WHERE set_published_status = 'PUBLISHED';

Because security is enforced within the Knowledge Base layer, query results are subject to the same visibility rules that govern the Workbench notes region, and the view should therefore be treated as a user-context-sensitive reporting source.