Search Results cac_sync_mappings




Overview
Explore in AI Chat

Overview

The CAC_SYNC_MAPPINGS table is a core data object within the Oracle E-Business Suite (EBS), specifically under the JTF (CRM Foundation) product family. It functions as a central repository for synchronization mapping data, which is critical for the integration and data exchange between the Oracle EBS platform and external synchronization clients, such as mobile devices or desktop applications like Microsoft Outlook. Its primary role is to maintain the logical relationships and correspondences ("mappings") between data records for appointments, tasks, and contacts that exist on the EBS server and their synchronized counterparts on a client device. This ensures data consistency and integrity during bidirectional synchronization processes.

Key Information Stored

The table stores a unique mapping record for each synchronized item. While the full column list is not detailed in the provided metadata, the documented primary and foreign keys reveal its essential structure. The MAPPING_ID column serves as the unique primary key identifier for each mapping record. A critical foreign key is the PRINCIPAL_ID column, which links to the CAC_SYNC_PRINCIPALS table. This relationship associates each mapping with a specific synchronization principal, representing the user or client application involved in the sync session. The table's description indicates it holds separate mapping information for the three key synchronized entities: appointments, tasks, and contacts, likely involving columns that store the server-side object ID and the corresponding client-side identifier.

Common Use Cases and Queries

This table is primarily accessed during synchronization operations and for troubleshooting sync-related data issues. A common operational use case is resolving synchronization conflicts by querying the mapping history between server and client objects. Administrators may also query this table to audit synchronization activity for a specific user or to clean up orphaned mappings after a client device is decommissioned. A typical reporting query would join with the CAC_SYNC_PRINCIPALS table to list all mappings for a particular user.

  • Sample Query (Find Mappings for a User):
    SELECT pr.principal_name, map.*
    FROM jtf.cac_sync_mappings map,
         jtf.cac_sync_principals pr
    WHERE map.principal_id = pr.principal_id
    AND pr.principal_name = 'JSMITH';

Related Objects

The CAC_SYNC_MAPPINGS table has a documented, direct foreign key relationship with the CAC_SYNC_PRINCIPALS table. This is a fundamental dependency where the CAC_SYNC_MAPPINGS.PRINCIPAL_ID column references the primary key of the CAC_SYNC_PRINCIPALS table. The CAC_SYNC_PRINCIPALS table defines the users or client applications authorized for synchronization. Therefore, any valid mapping must be associated with a defined principal. This table is also likely referenced by other synchronization engine tables and views within the JTF schema that manage sync sessions, history, and conflict logs, forming a key part of the EBS CRM synchronization infrastructure.