Search Results jtf_notes_source_type_map




Overview
Explore in AI Chat

Overview

JTF_NOTES_SOURCE_TYPE_MAP is a CRM Foundation (JTF) base table that defines application- and object-specific note types within Oracle E-Business Suite 12.1.1 and 12.2.2. It serves as the configuration registry that links a Source Object (for example, a service request, an opportunity, or a contact) to the note types that are valid for that object. Applications query this mapping at runtime to determine which note classifications a user may select when attaching a note to a specific business entity, thereby enforcing consistency across the Notes infrastructure that supports Oracle CRM modules.

The table is owned by the JTF schema and holds VALID status in the ETRM data dictionary. Under the heuristic Data Vault classification derived from its foreign-key structure, the object is satellite-leaning. This suggests it is best modeled as a descriptive satellite attached to a business key hub (the note-type/object mapping identity) rather than as an independent hub or a pure link, since its columns primarily carry attributes describing the mapping relationship.

Key Information Stored

The table comprises eleven documented columns. The most significant are:

The unique index JTF_NOTES_STM_U2, defined over NOTE_SOURCE_TYPE_MAP_ID and ZD_EDITION_NAME, functions as a business-key candidate and reinforces the edition-aware uniqueness required in 12.2.2. The surrogate NOTE_SOURCE_TYPE_MAP_ID therefore remains the primary identifier, while SOURCE_OBJECT_CODE and NOTE_TYPE together describe the substantive mapping semantics.

Common Use Cases and Queries

Typical scenarios include resolving which note types are permitted for a given object, validating note captures, and building reporting extracts of configured note taxonomies. A representative query joining the object definition follows:

  • Listing active note types per source object: SELECT m.NOTE_SOURCE_TYPE_MAP_ID, o.OBJECT_CODE, m.NOTE_TYPE FROM JTF.JTF_NOTES_SOURCE_TYPE_MAP m, JTF.JTF_OBJECTS_B o WHERE m.SOURCE_OBJECT_CODE = o.OBJECT_CODE AND (m.END_DATE IS NULL OR m.END_DATE > SYSDATE);
  • Restricting by security group: add AND m.SECURITY_GROUP_ID = :p_security_group_id to enforce data segregation.
  • Auditing recent configuration changes: filter on LAST_UPDATE_DATE and LAST_UPDATED_BY to identify who altered note-type availability.
  • Validating orphan mappings: outer-join to JTF_OBJECTS_B and select rows where the object code resolves to NULL.

Related Objects

The most significant related objects are those connected through documented foreign keys and the shared Notes infrastructure:

  • JTF_OBJECTS_B — referenced via SOURCE_OBJECT_CODE, providing the business object definition.
  • FND_SECURITY_GROUPS — referenced via SECURITY_GROUP_ID, supplying data-access segregation.
  • JTF_NOTES — the transactional notes table whose note types are governed by this mapping.
  • JTF_NOTES_TL — the translatable notes table sharing the same note framework.
  • JTF_OBJECTS_TL — the translated object definitions joined through the object code.
  • FND_APPLICATION — for resolving the application context of the source object.

Together these objects support the configuration, validation, and reporting of note types across Oracle CRM Foundation and its dependent applications.