Search Results jtf_ih_all_notes_vl




Overview
Explore in AI Chat

Overview

The JTF_IH_ALL_NOTES_VL view is a CRM Foundation (JTF) database object owned by the APPS schema. Its documented purpose is to allow users and applications to view JTF Notes attached to Interactions. In the Oracle EBS 12.1.1 and 12.2.2 releases, this view serves as a consolidated, read-only presentation layer that joins note context information, interaction activities, and the base notes records into a single denormalized result set.

Because it is defined as a view rather than a table, JTF_IH_ALL_NOTES_VL carries no independent storage and inherits its lifecycle from the underlying base objects. It participates in the CRM Foundation product family, which underpins Interaction History, Telephony, and multichannel contact-center functionality. The view is particularly relevant to the note_context_type search term, as that column is one of the principal joining and filtering attributes exposed by the view. Consumers typically use it to retrieve notes linked to a specific activity, interaction, or media item without needing to understand the polymorphic relationship between notes and their contexts.

As an integrated reporting and integration object, the view supports custom reports, Oracle Discoverer workbooks, BI Publisher data templates, and OAF/Forms-based extensions where a unified note listing for interactions is required.

Underlying Base Objects

According to the documented view text, JTF_IH_ALL_NOTES_VL is defined over three principal objects:

The documented referenced-base-object metadata additionally lists FND_GLOBAL, JTF_COMMON_PVT, and JTF_NOTES_PKG as dependencies, reflecting standard JTF security and utility packages invoked indirectly through the underlying views and synonyms. The join logic is polymorphic: a note context joins to an activity, interaction, or media item depending on the value of NOTE_CONTEXT_TYPE. Only rows whose context type matches one of the three supported literals (JTF_ACTIVITY, JTF_INTERACTION, JTF_MEDIA_ITEM) are returned.

Key Columns

  • ROW_ID — unique row identifier inherited from the notes view; useful for addressing a specific note record.
  • NOTES — the actual note body text.
  • NOTE_CONTEXT_TYPE — the discriminator indicating whether the note is attached to an activity, an interaction, or a media item.
  • NOTE_CONTEXT_TYPE_ID — the identifier of the specific context record; interpreted against the matching activity, interaction, or media ID.
  • ACTIVITY_ID — the interaction history activity identifier, the primary anchor for the interaction view.
  • LAST_UPDATE_DATE, LAST_UPDATED_BY, CREATION_DATE, CREATED_BY, LAST_UPDATE_LOGIN — standard EBS audit columns enabling who/when tracking and incremental extraction.

Common Use Cases and Queries

Typical scenarios include listing all notes for a given interaction, filtering notes by context type, and extracting note data for reporting or migration.

  • Retrieve all notes for a specific activity: SELECT * FROM JTF_IH_ALL_NOTES_VL WHERE ACTIVITY_ID = :p_activity_id;
  • Retrieve only notes attached at the interaction level: SELECT ROW_ID, NOTES, NOTE_CONTEXT_TYPE_ID FROM JTF_IH_ALL_NOTES_VL WHERE NOTE_CONTEXT_TYPE = 'JTF_INTERACTION';
  • Incremental extraction using audit columns: SELECT * FROM JTF_IH_ALL_NOTES_VL WHERE LAST_UPDATE_DATE >= :p_since;
  • Count notes by context type for a dashboard: SELECT NOTE_CONTEXT_TYPE, COUNT(*) FROM JTF_IH_ALL_NOTES_VL GROUP BY NOTE_CONTEXT_TYPE;

Because the view applies no additional row-level filtering beyond the context-type predicate, implementers should apply their own business or security filters as required.