Search Results jtf_note_type




Overview
Explore in AI Chat

Overview

APPS.JTF_NOTES_SOURCE_TYPE_MAP_V is a reporting and integration view in Oracle E-Business Suite (documented across 12.1.1 and 12.2.2) that exposes the mapping between source objects and note types used by the Notes/Attachments infrastructure. It is a thin, denormalized projection of the JTF_OBJECT_MAPPINGS_V mapping table, joined to object definitions and lookup values, and filtered specifically to the note-type object context. The view carries a hard-coded literal column value of 'JTF_NOTE_TYPE', confirming that it is purpose-built to present only source-to-note-type relationships rather than the full mapping set.

Its primary role is to provide a read-only, human-readable surface for joins. Instead of forcing callers to resolve raw object IDs and codes against FND_LOOKUPS and JTF_OBJECTS_VL manually, the view pre-resolves the source object name and the note type meaning, making it convenient for concurrent programs, OAF/extensibility components, and ad hoc reporting queries that need to translate internal note-type identifiers into display values. The user search term jtf_note_type corresponds directly to the lookup type and object code constants embedded in the view definition, which is why this view is the canonical entry point for that search.

Underlying Base Objects

The view is defined over, and documented as referencing, the following objects:

  • JTF_OBJECT_MAPPINGS_V (VIEW, aliased OBM) — the driving object, furnishing ROW_ID, MAPPING_ID, SOURCE_OBJECT_CODE, OBJECT_ID, END_DATE, audit columns, APPLICATION_ID and SEEDED_FLAG.
  • JTF_OBJECTS_VL (VIEW, aliased OBJ) — supplies the translation of SOURCE_OBJECT_CODE into a display NAME (returned as SOURCE_MEANING).
  • FND_LOOKUPS (VIEW, aliased LKUP) — supplies the MEANING of the note type, resolved from LOOKUP_CODE matched to OBJECT_ID where LOOKUP_TYPE = 'JTF_NOTE_TYPE'.
  • JTF_OBJECTS_PVT (PACKAGE) — the PL/SQL API supporting the objects layer referenced by the mapping infrastructure.
  • FND_GLOBAL (PACKAGE) — provides session/context functions (such as user and application context) used throughout the JTF objects stack.

The joins are strict equi-joins: OBM.SOURCE_OBJECT_CODE = OBJ.OBJECT_CODE, and LKUP.LOOKUP_CODE = OBM.OBJECT_ID with LKUP.LOOKUP_TYPE = 'JTF_NOTE_TYPE'. A final predicate restricts the result set to OBM.OBJECT_CODE = 'JTF_NOTE_TYPE', so only mappings whose target object type is the note type are returned.

Key Columns

  • ROW_ID — unique row identifier inherited from the mapping table.
  • MAPPING_ID — identifier of the underlying object mapping definition; useful for tracing back to the mapping entity.
  • SOURCE_OBJECT_CODE — code of the source business object participating in the mapping (for example, a note-enabled entity type).
  • SOURCE_MEANING — the translated, displayable name of the source object, resolved from JTF_OBJECTS_VL.NAME.
  • OBJECT_ID — the identifier of the target object; in this view it is matched to FND_LOOKUPS.LOOKUP_CODE.
  • TYPE_MEANING — the translated note type meaning from FND_LOOKUPS.MEANING; this is the value most users actually want to display.
  • END_DATE — effective end date of the mapping, enabling time-bounded filtering.
  • SEEDED_FLAG — indicates whether the mapping was seeded by Oracle or created by the customer, relevant for upgrade and patch impact analysis.
  • APPLICATION_ID — owning application of the mapping row.
  • Audit columns — LAST_UPDATE_DATE, LAST_UPDATED_BY, CREATION_DATE, CREATED_BY, LAST_UPDATE_LOGIN.
  • Literal column — a constant 'JTF_NOTE_TYPE' returned for every row, identifying the object context.

Common Use Cases and Queries

Typical scenarios include resolving a note type ID to its display meaning for reports, enumerating the objects that support notes for a given type, auditing seeded versus customer-defined mappings prior to an upgrade, and validating that an expected source-object-to-note-type assignment exists during integration testing.

SELECT mapping_id,
       source_object_code,
       source_meaning,
       type_meaning
  FROM apps.jtf_notes_source_type_map_v
 WHERE (end_date IS NULL OR end_date > SYSDATE)
 ORDER BY source_meaning;

SELECT type_meaning,
       COUNT(*) AS source_count
  FROM apps.jtf_notes_source_type_map_v
 WHERE seeded_flag = 'Y'
 GROUP BY type_meaning
 ORDER BY source_count DESC;

Because the view is filtered to OBJECT_CODE = 'JTF_NOTE_TYPE' and exposes resolved meanings, it is generally preferable to querying JTF_OBJECT_MAPPINGS_V directly when only note-type mappings are required. Callers needing edits should use the JTF_OBJECTS_PVT APIs against the base mapping entity rather than the view, which is read-only.