Search Results jtf_notes_source_type_map_v




Overview
Explore in AI Chat

Overview

JTF_NOTES_SOURCE_TYPE_MAP_V is a reporting and integration view owned by the APPS schema within the JTF — CRM Foundation product family. In Oracle E-Business Suite 12.1.1 and 12.2.2 it is catalogued as a VALID database view whose stated purpose is to serve as a decoded, presentation-layer view over JTF_OBJECT_MAPPINGS_V. The object is registered in ETRM with the object type VIEW and its documentation explicitly identifies JTF_OBJECT_MAPPINGS_V as the primary source. Functionally, the view maps the internal note source/object identifiers used by the Notes (JTF_NOTES) framework to their human-readable descriptions. This is achieved by joining the object mapping rows to JTF_OBJECTS_VL for the source object name and to FND_LOOKUPS for the note type lookup meaning. Because the view exposes translated meanings rather than raw codes, it is well suited to operational reporting, BI Publisher datasets, OAF or Forms LOV population, and interface extraction where business users or downstream systems require descriptive text instead of internal IDs.

Underlying Base Objects

The documented base objects referenced by this view are JTF_OBJECT_MAPPINGS_V (VIEW), JTF_OBJECTS_VL (VIEW), FND_LOOKUPS (VIEW), JTF_OBJECTS_PVT (PACKAGE), and FND_GLOBAL (PACKAGE). The core definition is built by joining three views:

The view is additionally restricted by OBM.OBJECT_CODE = 'JTF_NOTE_TYPE' and projects the literal string 'JTF_NOTE_TYPE' as OBJECT_CODE for the note-type context. JTF_OBJECTS_PVT and FND_GLOBAL are supporting package objects referenced through JTF_OBJECT_MAPPINGS_V and JTF_OBJECTS_VL rather than being joined directly in the view text; they handle object resolution and session/environment context respectively.

Key Columns

  • ROW_ID — the mapping row identifier from JTF_OBJECT_MAPPINGS_V, and the primary row-uniqueness candidate in the view.
  • NOTE_SOURCE_TYPE_MAP_ID — the alias applied to OBM.MAPPING_ID, the note source-to-type mapping identifier.
  • SOURCE_OBJECT_CODE — the internal code of the source object from which notes originate.
  • SOURCE_MEANING — the descriptive name of the source object (OBJ.NAME). This column answers the common "type_meaning"-style query for the source side of the mapping.
  • NOTE_TYPE — the lookup code drawn from OBM.OBJECT_ID; the internal note type identifier.
  • TYPE_MEANING — the lookup MEANING from FND_LOOKUPS for LOOKUP_TYPE 'JTF_NOTE_TYPE'. This column is the typical target of a "type_meaning" search because it is the translated, user-facing description of the note type.
  • END_DATE, LAST_UPDATE_DATE, LAST_UPDATED_BY, CREATION_DATE, CREATED_BY, LAST_UPDATE_LOGIN, APPLICATION_ID, SEEDED_FLAG, OBJECT_CODE — standard concurrency, audit, ownership, and seeded-data indicator columns inherited from the mapping row and the literal note-type context.

Common Use Cases and Queries

The view is typically queried to retrieve decodings of note type and source object for reporting, to validate seeded note configurations, and to drive dependent LOVs. A representative query returning the type meaning for all note types is:

SELECT NOTE_TYPE, TYPE_MEANING, SOURCE_OBJECT_CODE, SOURCE_MEANING FROM APPS.JTF_NOTES_SOURCE_TYPE_MAP_V ORDER BY TYPE_MEANING;

To filter to a specific note type, add a predicate on NOTE_TYPE or TYPE_MEANING, for example:

SELECT ROW_ID, NOTE_SOURCE_TYPE_MAP_ID, TYPE_MEANING FROM APPS.JTF_NOTES_SOURCE_TYPE_MAP_V WHERE NOTE_TYPE = :note_type;

Because the view applies an implicit inner join to FND_LOOKUPS and JTF_OBJECTS_VL, rows orphaned at the code level will not appear; when auditing incomplete mappings, query the underlying objects directly. As the view contains no application-level WHERE on APPLICATION_ID, callers should filter by APPLICATION_ID or SEEDED_FLAG when the context requires only seeded CRM Foundation data. No VALUESET or parameter binding is defined, so the view may be joined directly into reporting SQL against other JTF CRM Foundation and FND tables.