Search Results jta_sync_task_mapping_u1

Overview

JTF.JTA_SYNC_TASK_MAPPING is an Oracle E-Business Suite table that stores the association between CRM tasks and the sync resources and principals used to propagate them to client devices. It belongs to the JTF schema (Java Task Framework / CRM Foundation) and is installed under the FND Design Data object of the same name. The table resides in the APPS_TS_TX_DATA tablespace with PCT Free 10, while all three of its indexes are created in APPS_TS_TX_IDX.

The object is classified with a heuristic Data Vault designation of standalone. In Data Vault modeling terms, this suggests the table behaves as an independent structure rather than participating in a classic hub-and-satellite or link topology; it carries its own surrogate key, standard audit columns, and no outgoing primary-key-to-primary-key relationships that would define it as a link between two business hubs. Modelers treating this as a raw data source may therefore choose to treat it as a standalone entity with descriptive attributes rather than splitting it into hub and satellite components.

Oracle flags the object with a warning that it is for Oracle Internal Use Only and that access from outside standard Oracle Applications programs is unsupported. This is significant because the table is populated and maintained by Oracle's synchronization infrastructure rather than by customer extension code.

Key Information Stored

The table contains ten documented columns. The most important are summarized below.

• TASK_SYNC_ID (NUMBER) — The surrogate primary key. It is driven by the sequence JTA_SYNC_TASK_MAPPING_S and is the single column of the unique index JTA_SYNC_TASK_MAPPING_U1. This index is the authoritative business-key candidate documented for the table.
• TASK_ID (NUMBER) — The task identifier, documented as a foreign key to JTF_TASKS_B. It ties each sync mapping row back to the underlying task record.
• RESOURCE_ID (NUMBER) — Identifier of the sync resource. It is the leading column of the non-unique index JTA_SYNC_TASK_MAPPING_N1.
• PRINCIPAL_ID (NUMBER) — Uniquely identifies a user's sync device. Per the documented comment, this column was added to support the use of multiple client devices per user. It is a foreign key to CAC_SYNC_PRINCIPALS.
• SECURITY_GROUP_ID (NUMBER) — Security group identifier, used for multi-organization data partitioning. It is documented as a foreign key to FND_SECURITY_GROUPS.
• CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN — The five standard WHO audit columns recording row creation and last modification context.

The composite non-unique index JTA_SYNC_TASK_MAPPING_N2 covers TASK_ID, PRINCIPAL_ID, and RESOURCE_ID, indicating that the primary access path filters task synchronization rows by principal and resource.

Common Use Cases and Queries

Because this table is Oracle-internal, customer reporting against it is typically diagnostic rather than functional. Typical scenarios include investigating why a task has not appeared on a user's device, reconciling which principals hold a given task, and auditing orphaned mappings after task deletion.

• Retrieve all sync mappings for a specific task, using the N2 index path: SELECT task_sync_id, task_id, resource_id, principal_id FROM jtf.jta_sync_task_mapping WHERE task_id = :task_id;
• List every task synchronized to a given principal: SELECT task_id, resource_id FROM jtf.jta_sync_task_mapping WHERE principal_id = :principal_id ORDER BY task_id;
• Join to JTF_TASKS_B to confirm the task still exists and is valid: SELECT m.task_sync_id, t.task_id, t.task_name FROM jtf.jta_sync_task_mapping m, jtf.jtf_tasks_b t WHERE m.task_id = t.task_id;
• Check security-group partitioning for multi-org environments by grouping on SECURITY_GROUP_ID.

All queries should be executed read-only. Direct DML against this table bypasses Oracle's synchronization logic and is not supported.

Related Objects

The following objects are the most significant to consider when working with this table.

• JTF.JTF_TASKS_B — Referenced through the TASK_ID column; the parent task definition.
• CAC_SYNC_PRINCIPALS — Referenced through PRINCIPAL_ID; defines the sync device or principal identity.
• FND_SECURITY_GROUPS — Referenced through SECURITY_GROUP_ID; governs data partitioning.
• JTA_SYNC_TASK_MAPPING_S — The sequence supplying TASK_SYNC_ID values.
• JTA_SYNC_TASK_MAPPING_U1 / _N1 / _N2 — The unique and non-unique indexes supporting primary key lookup and principal/resource filtering.
• APPS.JTA_SYNC_TASK_MAPPING — The synonym through which Oracle Applications code accesses the table.