Search Results cac_sync_task_common




Overview
Explore in AI Chat

Overview

APPS.CAC_SYNC_TASK_CURSORS is a supporting PL/SQL package within the Oracle E-Business Suite that provides centralized cursor definitions for the calendar and task synchronization framework. In Release 12.1.1 and 12.2.2, this framework is used to synchronize Oracle Tasks (JTF/JTA schema) with external calendar or scheduling targets such as Microsoft Exchange, Lotus Notes, or other third-party groupware systems. The package does not expose a public API in the conventional sense; instead, it acts as a repository of pre-defined SQL cursors consumed by higher-level synchronization packages.

Its primary companion is CAC_SYNC_TASK_COMMON, which aggregates task data, resolves resource mappings, and drives publishing logic. CAC_SYNC_TASK_CURSORS supplies the query definitions that CAC_SYNC_TASK_COMMON and CAC_SYNC_TASK open and fetch. By isolating cursor text into a dedicated package, Oracle kept the synchronization logic reusable and simplified maintenance across the various synchronization tasks defined in the JTA_SYNC_TASK_MAPPING table.

Key Procedures and Functions

The ETRM metadata for this object documents zero public procedures or functions. The package body structure is not exposed through documented procedures, confirming that CAC_SYNC_TASK_CURSORS is a cursor-only construct. The cursors it defines are referenced internally by sibling packages rather than invoked directly by forms or concurrent programs. Because no callable interface is documented, implementers should not attempt to call the package directly; its value lies entirely in the SQL result sets it produces for the synchronization engine.

Dependency analysis shows CAC_SYNC_TASK_CURSORS itself invokes logic from CAC_SYNC_TASK, CAC_SYNC_TASK_COMMON, CAC_VIEW_UTIL_PUB, and STANDARD, meaning some cursor definitions may be wrapped inside helper calls or shared view utilities rather than expressed as pure static SQL.

Tables Accessed

According to the documented dependency list, the package reads from the following APPS synonyms:

  • JTF_TASKS_B and JTF_TASKS_TL — the base and translated task tables that hold the core task records subject to synchronization.
  • JTF_TASK_ALL_ASSIGNMENTS — defines which resources own or are assigned to each task, driving calendar owner resolution.
  • JTF_TASK_PRIORITIES_B, JTF_TASK_STATUSES_B, JTF_TASK_RECUR_RULES — lookup and recurrence data used to render task attributes into the external calendar format.
  • JTA_SYNC_TASK_MAPPING and JTA_TASK_EXCLUSIONS — configuration tables that determine which tasks participate in a given synchronization task and which are filtered out.
  • FND_GRANTS and FND_PROFILE — security and profile option values that restrict cursor output to authorized users and honor setup such as enabled synchronization modes.

No write operations are documented; the package is read-only in behavior.

Usage Notes

CAC_SYNC_TASK_CURSORS is invoked indirectly whenever a task synchronization process runs. In a standard EBS deployment this occurs when an administrator initiates synchronization through the Calendar and Task synchronization setup or through a scheduled concurrent request that processes the JTA_SYNC_TASK_MAPPING entries. CAC_SYNC_TASK_COMMON opens the cursors provided by this package, iterates the resulting task rows, and publishes them to the target calendar system.

Because the package is referenced by exactly one other package (CAC_SYNC_TASK_COMMON), its lifecycle is tightly coupled to that consumer. Customizations should not modify CAC_SYNC_TASK_CURSORS directly, since Oracle may change cursor definitions during patching. Any extension should be implemented in a custom package that queries the underlying JTF and JTA tables independently. During upgrades from 12.1.1 to 12.2.2, the package status should remain VALID; invalidations typically indicate an underlying table or dependency change requiring recompilation of the APPS schema.