Search Results csc_sr_kb_note_links_v




Overview
Explore in AI Chat

Overview

CSC_SR_KB_NOTE_LINKS_V is a VALID view owned by the APPS schema within the CSC – Customer Care product family in Oracle E-Business Suite 12.1.1 and 12.2.2. The view combines JTF notes with knowledge management element links and set links, and is used by Oracle Support for integration from Service Requests to Knowledge Management. Practically, it functions as a unified record set that normalizes two distinct sources of service-related content — free-form notes captured through the JTF note framework and structured knowledge base element links — into a single, queryable shape. This normalization is what allows downstream Service Request processing to treat notes and KB links interchangeably when rendering or exporting knowledge content.

Underlying Base Objects

Documented view metadata for 12.2.2 lists the following referenced base objects: FND_GLOBAL (PACKAGE), JTF_COMMON_PVT (PACKAGE), JTF_NOTES_PKG (PACKAGE), JTF_NOTES_VL (VIEW), JTF_NOTE_CONTEXTS (SYNONYM), and DBMS_LOB (SYNONYM). These underpin note handling, locale (NLS) resolution, multi-language note text, and large-object access. The view text reveals a UNION ALL over three branches:

Because both branches expose the same column list, the FND_LOOKUPS-driven JTF_NOTE_TYPE and JTF_NOTE_STATUS meanings are reused to describe knowledge element types, keeping the output consistent across source systems.

Key Columns

The most significant column in the user's search context is APP_OBJ_CODE. In the note branch it is sourced from NOTE.SOURCE_OBJECT_CODE, while in the element branch it is populated from ELEM_LINK.OBJECT_CODE. It identifies the application object type (for example, a Service Request or another TCA/JTF entity) that the note or KB link is associated with, and is essential for filtering records to a specific business object. APP_OBJ_ID carries the corresponding SOURCE_OBJECT_ID or OTHER_ID, providing the object instance key. Additional notable columns include ID (JTF_NOTE_ID or ELEMENT_ID or SET_ID), NOTE_TYPE_CODE and NOTE_TYPE_MEANING, NOTE (the note or element name), NOTE_STATUS and NOTE_STATUS_MEANING, RECORD_SOURCE_TYPE ('JTF_NOTE' or 'KB_ELEM'), and CREATED_BY / CREATION_DATE / LAST_UPDATE_DATE audit columns. TRUE_STMT is a literal 'T' flag used to mark note records, while SOLUTION_ID, OUTCOME, and SOLUTION_NUMBER are deliberately NULL placeholders reserved for downstream solution enrichment.

Common Use Cases and Queries

Typical consumption paths include Service Request note listings, knowledge integration feeds, and reporting on the mix of notes versus KB-linked content per object. A representative query filters by application object code and joins back to the SR header:

  • SELECT id, app_obj_id, app_obj_code, note_type_code, note_type_meaning, note, record_source_type FROM csc_sr_kb_note_links_v WHERE app_obj_code = 'SR';
  • Segregate sources: SELECT record_source_type, COUNT(*) FROM csc_sr_kb_note_links_v GROUP BY record_source_type;
  • Retrieve KB element links only: SELECT id, app_obj_id, note FROM csc_sr_kb_note_links_v WHERE record_source_type = 'KB_ELEM';

Because language resolution depends on USERENV('LANG'), queries should be run in the session language expected by the requesting user to guarantee the correct _TL row is returned.