Results for “jtf_object_mappings”

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

Overview

JTF_OBJECT_MAPPINGS is a CRM Foundation (JTF) table in Oracle E-Business Suite 12.1.1 and 12.2.2 that functions as a mapping repository between source objects and target object types. The table allows applications to define relationships between a source identifier and a particular object type, such as task types or note types. In practice, it is the mechanism by which the CRM Foundation associates generic object definitions with the concrete source records that applications use, providing a central point of reference for object-to-source resolution across JTF-based features.

The table is owned by the JTF schema and is documented as VALID in ETRM 12.2.2, containing 31 columns. From a Data Vault modeling perspective, the heuristic classification derived from its foreign key structure is link. This classification is a modeling suggestion: the table primarily captures relationships between JTF_OBJECTS_B records and lookup-backed source definitions, with the SECURITY_GROUP_ID FK introducing an additional association to FND_SECURITY_GROUPS.

Key Information Stored

The surrogate primary key is MAPPING_ID, enforced by the JTF_OBJECT_MAPPINGS_PK constraint. The table also carries a documented unique index, JTF_OBJECT_MAPPINGS_U1, defined on the combination (SOURCE_OBJECT_CODE, OBJECT_CODE, OBJECT_ID, APPLICATION_ID, ZD_EDITION_NAME), which identifies a business-key candidate that guarantees uniqueness of a mapping within an application and edition context.

The most significant columns include:

• MAPPING_ID — surrogate primary key uniquely identifying each mapping row.
• SOURCE_OBJECT_CODE — references JTF_OBJECTS_B, identifying the source object being mapped.
• OBJECT_CODE — business key component identifying the target object type.
• OBJECT_ID — identifier of the specific object instance participating in the mapping.
• APPLICATION_ID — the application context that owns or defines the mapping.
• END_DATE — effective end date supporting date-tracked validity of the mapping.
• SEEDED_FLAG — indicates whether the mapping was delivered as seed data or created by a user.
• SECURITY_GROUP_ID — references FND_SECURITY_GROUPS, controlling multi-tenant visibility.
• OBJECT_VERSION_NUMBER — optimistic locking column used by the framework.
• ATTRIBUTE_CATEGORY and ATTRIBUTE1–ATTRIBUTE15 — descriptive flexfield storage for extensible attributes.
• CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN — standard WHO audit columns.
• ZD_EDITION_NAME — editioning column supporting EBR-enabled deployments in 12.2.x.

Lookup-backed columns such as FLE_LOOKUP_TYPE, FLE_LOOKUP_CODE, FLE_LANGUAGE, FLE_SECURITY_GROUP_ID, and FLE_VIEW_APPLICATION_ID resolve against FND_LOOKUP_VALUES, enabling flexible value sets for mapping definitions.

Common Use Cases and Queries

Typical scenarios involve resolving which source object a task type or note type belongs to, or reporting all mappings defined within a given application. A common query pattern joins the table to JTF_OBJECTS_B to retrieve source object descriptions:

• SELECT m.mapping_id, m.source_object_code, o.object_code, m.object_id, m.application_id FROM jtf_object_mappings m, jtf_objects_b o WHERE m.source_object_code = o.object_code;
• Filtering active mappings using END_DATE IS NULL OR END_DATE > SYSDATE to obtain currently valid relationships.
• Restricting by SECURITY_GROUP_ID to enforce organization-level data security in reporting.
• Querying by APPLICATION_ID to audit mappings delivered by a specific module such as a CRM task or notes application.

Because the ROWID or MAPPING_ID uniquely identifies rows, incremental extraction for data warehouse loads can rely on LAST_UPDATE_DATE, making the table suitable for change-data-capture feeds into CRM analytics.

Related Objects

The following objects are most significant in relation to JTF_OBJECT_MAPPINGS:

• JTF_OBJECTS_B — referenced through SOURCE_OBJECT_CODE; the primary lookup for source object definitions.
• FND_LOOKUP_VALUES — referenced through the FLE_LOOKUP_TYPE, FLE_LOOKUP_CODE, FLE_LANGUAGE, FLE_SECURITY_GROUP_ID, and FLE_VIEW_APPLICATION_ID columns for lookup resolution.
• FND_SECURITY_GROUPS — referenced through SECURITY_GROUP_ID for data security enforcement.
• JTF_OBJECT_MAPPINGS_PK — primary key constraint on MAPPING_ID.
• JTF_OBJECT_MAPPINGS_U1 — unique index on SOURCE_OBJECT_CODE, OBJECT_CODE, OBJECT_ID, APPLICATION_ID, and ZD_EDITION_NAME.

These relationships make JTF_OBJECT_MAPPINGS a central link table within the CRM Foundation, bridging object definitions, lookup values, and security groups for applications that require source-to-object traceability.