Search Results note_entered_by_name

Overview

APPS.CSC_SR_KB_NOTE_LINKS_V is a reporting and integration view in Oracle E-Business Suite that exposes service request knowledge-base note links in a standardized format. It is defined in the APPS schema and draws its content directly from JTF_NOTES_VL, the translatable view over the JTF_NOTES entity used throughout the Oracle Interaction Center and Service (TeleService) modules. The view's central purpose is to present note records together with the identifiers and metadata required to associate them with a source application object, most commonly a service request, so that downstream components can treat notes as linkable knowledge-base artifacts.

The "_LINKS" suffix reflects the fact that every row returned carries an application object identifier (APP_OBJ_ID) and an application object code (APP_OBJ_CODE). This allows a note to be joined back to its owning entity, which is the defining characteristic of a link record rather than a standalone note. For users searching on "jtf_note," this view is the primary APPS-layer projection of the underlying JTF_NOTES_VL data with link semantics layered on top.

Underlying Base Objects

The documented metadata identifies the following referenced objects:

• JTF_NOTES_VL (VIEW) — the direct source of all selected columns; it provides the translatable note text and note attributes.
• JTF_NOTE_CONTEXTS (SYNONYM) — the context/association entity that links notes to source objects such as service requests.
• JTF_NOTES_PKG (PACKAGE) — the PL/SQL API that governs note creation, update, and validation.
• JTF_COMMON_PVT (PACKAGE) — shared private utilities referenced by the note infrastructure.
• FND_GLOBAL (PACKAGE) — provides session-level context (user, responsibility, login) used in note security and auditing.
• DBMS_LOB (SYNONYM) — the Oracle LOB package used to evaluate the length of the notes detail CLOB.

Because the view selects from JTF_NOTES_VL, it inherits that view's join to the underlying JTF_NOTES table and its translation mechanism. No aggregation or filtering is applied; the projection is a straight column mapping with two literal constants added.

Key Columns

• ID — maps to JTF_NOTE_ID, the unique note identifier.
• APP_OBJ_ID / APP_OBJ_CODE — the source object identifier and object code; these carry the link target, typically the service request or knowledge article.
• NOTE_TYPE_CODE / NOTE_TYPE_MEANING — the note classification code and its translated display value.
• NOTES — the short note text; NOTES_DETAIL — the long note body stored as a CLOB.
• DETAIL_EXIST — a derived flag computed with DECODE(DBMS_LOB.GETLENGTH(...)); returns 'Y' when detailed text exists, otherwise 'N'.
• TRUE_STMT — a literal 'T' constant supplied by the view.
• RECORD_SOURCE_TYPE — a literal 'JTF_NOTE' constant identifying the origin system.
• NOTE_STATUS / NOTE_STATUS_MEANING — the workflow status code and translated meaning.
• NOTE_ENTERED_BY_NAME / NOTE_ENTERED_DATE — the display name and timestamp of the originating author.
• CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN — standard WHO-column audit trail.

Common Use Cases and Queries

Typical scenarios include extracting all notes attached to a service request, building knowledge-base dashboards, and integrating note data into external systems. Because APP_OBJ_ID and APP_OBJ_CODE identify the parent object, the view is joined to SR tables when the request number is required.

• Retrieve all notes for a given object:
  SELECT id, note_type_meaning, note_status_meaning, note_entered_by_name, note_entered_date FROM csc_sr_kb_note_links_v WHERE app_obj_id = :sr_id;
• List notes that carry detailed text:
  SELECT id, notes FROM csc_sr_kb_note_links_v WHERE detail_exist = 'Y';
• Filter by status for open items:
  SELECT id, app_obj_id, note_status_meaning FROM csc_sr_kb_note_links_v WHERE note_status = 'OPEN';

Consumers should be aware that details of security predicates are not enumerated in the ETRM excerpt; row visibility may be governed by JTF_NOTES_PKG and FND_GLOBAL session context, so production queries should be validated against the responsibility's profile options.