Search Results jtf_activity




Overview
Explore in AI Chat

Overview

APPS.JTF_IH_NOTES_ACT_VL is an Oracle E-Business Suite view that exposes notes associated with interaction history (IH) activities. It is part of the CRM Foundation (JTF) schema, which supplies the shared infrastructure for notes, tasks, and interaction tracking used across Oracle Sales, Oracle Service, and Oracle Marketing. The view presents the textual note body alongside the activity identifier and the note context type identifier, effectively joining activity records to their attached notes.

The suffix "_VL" indicates a validation-list style or localized view, a common Oracle naming convention for views built over a base table pair ("_B" and "_TL") to present translatable, user-facing content. In reporting and integration scenarios, JTF_IH_NOTES_ACT_VL provides a convenient, denormalized access point for extracting activity notes without requiring the caller to reconstruct the note context linkage manually. Because activity records represent discrete interactions such as calls, meetings, or visits, this view is frequently used in Oracle CRM reporting where analysts need to read the remarks captured against those interactions.

Underlying Base Objects

The ETRM metadata documents that the view is defined over SYNONYM objects JTF_IH_ACTIVITIES and JTF_NOTE_CONTEXTS, together with the view JTF_NOTES_VL. The view text confirms the join logic:

  • JTF_NOTE_CONTEXTS stores the note context rows that link a note to its owning entity; the predicate NC.NOTE_CONTEXT_TYPE = 'JTF_ACTIVITY' restricts the context to activities.
  • JTF_IH_ACTIVITIES supplies the activity identifier; the join NC.NOTE_CONTEXT_TYPE_ID = ACT.ACTIVITY_ID ties each context row back to its activity.
  • JTF_NOTES_VL supplies the actual note text; the join NC.JTF_NOTE_ID = N.JTF_NOTE_ID retrieves the note content.

The metadata further lists FND_GLOBAL, JTF_COMMON_PVT, and JTF_NOTES_PKG as referenced objects, which is consistent with views that rely on the standard JTF security and note-handling packages for multi-org or user context, and with the "_VL" mechanism that typically delegates row filtering to the JTF package layer.

Key Columns

  • NOTES — The note text itself, sourced from JTF_NOTES_VL. This is the primary payload column for most reporting.
  • NOTE_CONTEXT_TYPE_ID — The identifier from JTF_NOTE_CONTEXTS that points to the owning entity. For activity notes this equals the activity ID, not the note ID.
  • ACTIVITY_ID — The interaction history activity identifier from JTF_IH_ACTIVITIES. This is the join key to activity-header tables and to other activity-detail views.

Note that the view does not expose a separate note ID column in the documented SQL, so consumers joining on note identity must use the context type ID column or go back to the underlying tables.

Common Use Cases and Queries

The most common use is extracting activity remarks for reporting. A representative query retrieves notes for a specific activity:

  • SELECT activity_id, notes FROM apps.jtf_ih_notes_act_vl WHERE activity_id = :activity_id;

For integration, developers join the view to activity headers to enrich extracts with note text. A typical pattern:

  • SELECT a.activity_id, a.subject, n.notes FROM jtf_ih_activities a, jtf_ih_notes_act_vl n WHERE a.activity_id = n.activity_id;

Because the view filters strictly on NOTE_CONTEXT_TYPE = 'JTF_ACTIVITY', it returns only activity-linked notes, which simplifies queries compared with accessing JTF_NOTE_CONTEXTS directly. When troubleshooting missing notes, verify that the context row exists in JTF_NOTE_CONTEXTS with the matching type and that the note is visible under the JTF security rules applied by the supporting JTF packages.