Results for “jtf_object_mappings_u1”

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

Overview

JTF.JTF_OBJECT_MAPPINGS is a seed-data mapping table in the Oracle E-Business Suite CRM foundation (JTF) schema. It establishes the relationship between source object types and target object types, allowing generic CRM infrastructure components — such as notes, tasks, and references — to resolve the concrete business object they are attached to. The table description states its purpose directly: "Mapping Table between Source and Object Types eg Task Types, Note Types." As a result, it functions as the lookup backbone for polymorphic associations throughout JTF-based modules in both Release 12.1.1 and 12.2.2.

The table resides in the APPS_TS_SEED tablespace, reflecting its role as seeded reference configuration rather than high-volume transactional data. The provided metadata classifies this object heuristically as a link in Data Vault terms: it holds no descriptive history of its own and instead connects a source object (via SOURCE_OBJECT_CODE) to a concrete object reference, with surrogate and business keys enabling idempotent resolution. Modeling it as a link table is a reasonable suggestion given its associative character.

Key Information Stored

The primary key is the surrogate MAPPING_ID (JTF_OBJECT_MAPPINGS_PK), a system-generated identifier that uniquely names each mapping row. The documented business-key candidate is the unique index JTF_OBJECT_MAPPINGS_U1, defined over SOURCE_OBJECT_CODE, OBJECT_CODE, OBJECT_ID, and APPLICATION_ID (with ZD_EDITION_NAME in the 12.2.2 physical schema). This composite enforces that a given source object code maps to a unique object instance within an application context.

• MAPPING_ID — surrogate primary key for the mapping row.
• SOURCE_OBJECT_CODE — the originating object type (e.g. a task or note source), foreign key to JTF_OBJECTS_B.
• OBJECT_CODE — the resolved target object type code.
• OBJECT_ID — the instance identifier of the mapped object, described as "Source Code of the Object, e.g. ADMIN."
• APPLICATION_ID — the owning application, part of the unique key.
• END_DATE — effective end date, supporting date-bounded mappings.
• SEEDED_FLAG — indicates whether the row is Oracle-seeded or customer-defined.
• OBJECT_VERSION_NUMBER — optimistic locking control for HTML-based UI updates.
• SECURITY_GROUP_ID — foreign key to FND_SECURITY_GROUPS for multi-tenant isolation.
• FLE_LOOKUP_TYPE — foreign key to FND_LOOKUP_VALUES, tying descriptive flexfield context to a lookup.
• ATTRIBUTE_CATEGORY and ATTRIBUTE1–ATTRIBUTE15 — descriptive flexfield segments for extensible metadata.
• CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN — standard WHO audit columns.

Common Use Cases and Queries

The most frequent use is resolving which object a source item points to, for example when rendering notes or tasks against a CRM entity. A typical query filters on the business key and checks END_DATE for active mappings:

• Resolve a mapping: SELECT OBJECT_CODE, OBJECT_ID FROM JTF_OBJECT_MAPPINGS WHERE SOURCE_OBJECT_CODE = :src AND APPLICATION_ID = :app AND (END_DATE IS NULL OR END_DATE > SYSDATE);
• List seeded mappings for an application: SELECT SOURCE_OBJECT_CODE, OBJECT_CODE, OBJECT_ID FROM JTF_OBJECT_MAPPINGS WHERE APPLICATION_ID = :app AND SEEDED_FLAG = 'Y';
• Audit configuration changes by joining WHO columns to FND_USER via CREATED_BY / LAST_UPDATED_BY.
• Security-group-scoped reporting by joining SECURITY_GROUP_ID to FND_SECURITY_GROUPS.

Reporting use cases include validating that no duplicate business keys exist across the U1 index, identifying stale mappings past END_DATE, and reconciling object codes against JTF_OBJECTS_B.

Related Objects

The following objects are most significant, based on documented foreign keys and indexing:

• JTF_OBJECTS_B — referenced via SOURCE_OBJECT_CODE; supplies the canonical object type definitions.
• FND_LOOKUP_VALUES — joined through FLE_LOOKUP_TYPE for flexfield lookup resolution.
• FND_SECURITY_GROUPS — joined through SECURITY_GROUP_ID.
• FND_USER — implicit WHO-column relationship via CREATED_BY and LAST_UPDATED_BY.
• FND_LOGINS — implicit relationship via LAST_UPDATE_LOGIN.
• JTF_NOTES and JTF_TASKS — principal consumers that rely on these mappings for note and task type resolution.
• JTF_OBJECT_MAPPINGS_U1, _N1, _N3 — supporting indexes on the business key, OBJECT_CODE, and OBJECT_ID respectively.

Together these objects make JTF_OBJECT_MAPPINGS the connective tissue for polymorphic object references across the JTF CRM foundation layer.