Search Results jtf_object_mappings




Overview
Explore in AI Chat

Overview

The JTF_OBJECT_MAPPINGS table is a core metadata repository within the Oracle E-Business Suite CRM Foundation (JTF) module. It functions as a centralized mapping table that defines relationships between source systems and specific object types used across the CRM application framework. Its primary role is to enable applications to dynamically configure and retrieve appropriate object definitions—such as Task Types or Note Types—based on a given source context. This abstraction layer provides significant flexibility, allowing for the customization and extension of object behavior without direct modification of core application code. The table is essential for maintaining the integrity of object-source relationships in complex, multi-source CRM implementations in both releases 12.1.1 and 12.2.2.

Key Information Stored

The table's structure is designed to capture the essential elements of a mapping rule. The primary identifier is the MAPPING_ID column, which is the table's primary key. A critical column is SOURCE_OBJECT_CODE, which identifies the specific object type being mapped (e.g., a code for 'Task'). This column is a foreign key to JTF_OBJECTS_B. The table also stores references to lookup values in the FND_LOOKUP_VALUES table through a composite foreign key involving columns such as FLE_LOOKUP_TYPE, FLE_LOOKUP_CODE, FLE_LANGUAGE, FLE_SECURITY_GROUP_ID, and FLE_VIEW_APPLICATION_ID. These columns typically store the source system identifier or other contextual classification codes that determine which mapped object definition to use.

Common Use Cases and Queries

A primary use case is the dynamic assignment of task or note properties based on the originating application or transaction source. For instance, a task created from a Service Request may be mapped to a different task type with unique attributes than a task created from a Sales Opportunity. Developers and system integrators query this table to understand or validate configured mappings. A typical diagnostic query would join to the related objects table to get descriptive names:

  • SELECT jom.MAPPING_ID, job.OBJECT_NAME, jom.SOURCE_OBJECT_CODE, flv.MEANING AS SOURCE_MEANING FROM JTF.JTF_OBJECT_MAPPINGS jom, JTF.JTF_OBJECTS_B job, applsys.FND_LOOKUP_VALUES flv WHERE jom.SOURCE_OBJECT_CODE = job.OBJECT_CODE AND jom.FLE_LOOKUP_TYPE = flv.LOOKUP_TYPE AND jom.FLE_LOOKUP_CODE = flv.LOOKUP_CODE AND flv.LANGUAGE = 'US';

This table is also critical for custom reporting that needs to categorize data based on the source-to-object mapping logic.

Related Objects

The JTF_OBJECT_MAPPINGS table has documented foreign key relationships with two key metadata tables, as per the provided ETRM data:

  • FND_LOOKUP_VALUES: The mapping references standard application lookup codes to define the source context. The join is made on the composite key: (FLE_LOOKUP_TYPE, FLE_LANGUAGE, FLE_LOOKUP_CODE, FLE_SECURITY_GROUP_ID, FLE_VIEW_APPLICATION_ID).
  • JTF_OBJECTS_B: This relationship links the mapping to the actual object definition being selected. The join is on the column SOURCE_OBJECT_CODE referencing the OBJECT_CODE in JTF_OBJECTS_B.

These relationships underscore that JTF_OBJECT_MAPPINGS sits at the intersection of generic object definitions and contextual source codes, serving as a vital configuration point within the JTF architecture.