Results for “jtf_note_contexts”

AI-generated from documented ETRM metadata — verify critical details on the linked pages.

Overview

JTF_NOTE_CONTEXTS is the base table in the JTF (CRM Foundation) schema that stores contexts for notes. A context is a reference that links a note to another business object in the E-Business Suite — for example, a sales lead, a service request, an opportunity, or a customer. In this sense, the table is the associative backbone of the Notes framework: it answers the question "which record does this note belong to?" without having to hard-code a foreign key to every possible entity in the system.

The metadata classifies this object, using a heuristic Data Vault mining of its foreign key structure, as a link table. This is a sensible modeling suggestion: JTF_NOTE_CONTEXTS sits between JTF_NOTES_B and the wider universe of contextual objects, and its natural role is to record a relationship (note ↔ context type ↔ context record) rather than to act as a standalone hub or as a descriptive satellite.

Key Information Stored

The documented physical schema contains ten columns. The most significant are:

• NOTE_CONTEXT_ID — surrogate primary key, enforced by JTF_NOTE_CONTEXTS_PK and also backed by unique index JTF_NOTE_CONTEXTS_U1. This is the single strongest business-key candidate in the table and is the column users typically search for when they quote "note_context_id".
• JTF_NOTE_ID — foreign key to JTF_NOTES_B; identifies the note to which the context belongs.
• NOTE_CONTEXT_TYPE — foreign key to JTF_OBJECTS_B; identifies the type of object (e.g., lead, opportunity, service request) that the note is attached to.
• NOTE_CONTEXT_TYPE_ID — the physical identifier of the referenced context record. Documented FK targets include AS_LEADS_ALL and AS_SALES_LEADS, indicating the classic CRM lead scenarios that use this table.
• SECURITY_GROUP_ID — foreign key to FND_SECURITY_GROUPS, supporting Multi-Org / security-group access control on the context row.
• LAST_UPDATE_DATE, LAST_UPDATED_BY, CREATION_DATE, CREATED_BY, LAST_UPDATE_LOGIN — the standard EBS WHO columns used for audit and concurrency tracking.

Common Use Cases and Queries

Typical scenarios include retrieving all notes for a given lead or opportunity, listing the objects a note is attached to, and enforcing security-group filtered reporting on notes.

A simple lookup by primary key:

• SELECT * FROM JTF.JTF_NOTE_CONTEXTS WHERE NOTE_CONTEXT_ID = :p_id;

Finding all contexts for a note (join back to the notes base table):

• SELECT c.NOTE_CONTEXT_ID, c.NOTE_CONTEXT_TYPE, c.NOTE_CONTEXT_TYPE_ID
• FROM JTF.JTF_NOTE_CONTEXTS c, JTF.JTF_NOTES_B n
• WHERE c.JTF_NOTE_ID = n.JTF_NOTE_ID
• AND n.JTF_NOTE_ID = :note_id;

Reporting by context type, useful for "notes per object type" dashboards, can group on NOTE_CONTEXT_TYPE and join to JTF_OBJECTS_B for a descriptive name.

Related Objects

The most significant related objects, based on the documented foreign-key relationships, are:

• JTF_NOTES_B — parent note table, joined on JTF_NOTE_ID.
• JTF_OBJECTS_B — defines valid context types, joined on NOTE_CONTEXT_TYPE.
• AS_LEADS_ALL and AS_SALES_LEADS — lead tables referenced via NOTE_CONTEXT_TYPE_ID for lead-attached notes.
• FND_SECURITY_GROUPS — joined on SECURITY_GROUP_ID to apply org security.

Because the table is a link between notes and arbitrary objects, any CRM module — Sales, Service, or TeleSales — that surfaces notes on its records will pass through JTF_NOTE_CONTEXTS during query and reporting.