Search Results jta_sync_task_mapping_pk

Overview

JTA_SYNC_TASK_MAPPING is a CRM Foundation (JTF) table in Oracle E-Business Suite that stores the mapping records used to synchronize tasks between the Oracle EBS Task Manager and external scheduling or groupware systems, most notably Microsoft Outlook and Exchange. The table resides in the JTF schema and carries a VALID status in both the 12.1.1 and 12.2.2 releases. Its purpose is to correlate a native EBS task identifier with an external synchronization principal and resource, so that subsequent insert, update, or delete operations on a task can be propagated to, or reconciled with, the corresponding item in the external calendar or task store.

The table is governed by the primary key constraint JTA_SYNC_TASK_MAPPING_PK on TASK_SYNC_ID, with a matching unique index JTA_SYNC_TASK_MAPPING_U1 that reinforces the same column as the business key candidate. The documented schema for 12.2.2 lists ten columns. From a heuristic Data Vault perspective, mined from the foreign-key structure, this object is best modeled as a standalone table (an independent hub or reference structure) rather than a dependent satellite or associative link, since its documented foreign keys reference independent reference or master tables rather than forming a chain of dependent relationships.

Key Information Stored

The most significant columns in the documented schema are:

• TASK_SYNC_ID — The surrogate primary key and the single-column unique business-key candidate, uniquely identifying each synchronization mapping record.
• TASK_ID — The native Oracle EBS task identifier being mapped; this is the business reference that ties the row back to the task record itself.
• PRINCIPAL_ID — A foreign key to CAC_SYNC_PRINCIPALS, identifying the synchronization principal (for example, the groupware or Exchange account) for which the mapping is valid.
• RESOURCE_ID — Identifies the resource associated with the mapping, typically the person or resource entry whose calendar is synchronized.
• SECURITY_GROUP_ID — A foreign key to FND_SECURITY_GROUPS, enforcing multi-tenant data isolation across the CRM Foundation application.
• CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN — The standard Oracle EBS WHO columns that record audit and change-tracking metadata for each row.

Together these ten columns allow the synchronization engine to locate the correct external destination for a task while respecting the owning security group and principal.

Common Use Cases and Queries

Typical usage centers on diagnosing and monitoring the JTF task synchronization against external mail/calendar systems. Administrators and support analysts query this table to determine which tasks are mapped to which synchronization principal and resource, and to detect orphaned or stale mappings.

A representative query lists all synchronization mappings for a given principal:

• SELECT TASK_SYNC_ID, TASK_ID, RESOURCE_ID, SECURITY_GROUP_ID FROM JTA_SYNC_TASK_MAPPING WHERE PRINCIPAL_ID = :p_principal;

Another common pattern joins to CAC_SYNC_PRINCIPALS to report synchronization coverage by principal, and joins to FND_SECURITY_GROUPS to verify that every mapping is anchored to a valid security group. Reconciliation reports frequently compare TASK_ID values in this table against the task tables to identify tasks that exist but were never synchronized, or mappings whose underlying task no longer exists. Because the table carries audit columns, trend reporting on CREATION_DATE and LAST_UPDATE_DATE can reveal synchronization volume and staleness.

Related Objects

The following documented objects are most significant in relation to this table:

• CAC_SYNC_PRINCIPALS — Referenced via JTA_SYNC_TASK_MAPPING.PRINCIPAL_ID; the master list of synchronization principals.
• FND_SECURITY_GROUPS — Referenced via JTA_SYNC_TASK_MAPPING.SECURITY_GROUP_ID; provides the multi-tenant security grouping.
• JTA_SYNC_TASK_MAPPING_PK / JTA_SYNC_TASK_MAPPING_U1 — The primary key constraint and unique index enforcing uniqueness on TASK_SYNC_ID.
• JTF task tables — The native EBS task records referenced by TASK_ID, providing the source side of each mapping.
• JTA (Task Manager) synchronization APIs and concurrent programs — Processes that consume these mappings to push and reconcile tasks with external systems.

These relationships make JTA_SYNC_TASK_MAPPING the central correlation point between EBS task data and the external synchronization principals defined in CAC_SYNC_PRINCIPALS.