Search Results convert_gmt_to_server




Overview

APPS.CAC_SYNC_TASK_COMMON is a shared PL/SQL package body in the Oracle E-Business Suite CRM/TeleService and Trade Management (JTA) family. Its stated purpose, per the embedded header comment, is to act as a "common for sync task" — that is, a central library of utility logic used by the task synchronization programs that move appointment and task data between the EBS database and external calendar or collaboration clients. The package ships under the file name cacvstcb.pls and carries a revision header dated 2008, consistent with the 12.1.1 code line and unchanged in 12.2.2 apart from standard file versioning.

The body encapsulates date and time-zone handling, resource and group calendar resolution, assignment lookups, security checks, and recurring-task validation. In the context of the user's search term convert_gmt_to_server, this package is the definitive source of the GMT-to-server time-zone conversion routine used throughout task synchronization, ensuring that timestamps stored in GMT are presented in the server's local time zone before being written to or compared against task records.

Key Procedures and Functions

Of the 56 documented procedures and functions, the ones most relevant to scheduling and time handling are grouped below.

Tables Accessed

The package reads and writes through APPS synonyms. Task and synchronization data resides in JTA_SYNC_TASK_MAPPING, JTA_SYNC_TASK_MAPPING_S, and JTA_TASK_EXCLUSIONS. Recurrence and task definitions are drawn from JTF_TASKS_B and JTF_TASK_RECUR_RULES. Resource and group calendar information comes from JTF_RS_GROUPS_B, JTF_RS_GROUPS_TL, JTF_RS_GROUP_MEMBERS, JTF_RS_GROUP_USAGES, and JTF_RS_RESOURCE_EXTNS. Security and menu metadata are read from FND_GRANTS, FND_MENUS, and FND_OBJECTS. Collaboration data is sourced from CAC_SYNC_PRINCIPALS and the CAC_VIEW_COLLAB_DETAILS, CAC_VIEW_COLLAB_DETAILS_S, and CAC_VIEW_COLLAB_DETAILS_TL views.

Usage Notes

CAC_SYNC_TASK_COMMON is not a public API. It is invoked internally by the three packages that reference it, which in turn support the task synchronization concurrent programs and the TeleService appointment forms. Custom code should not call the package directly; where a time-zone conversion is required, the supported approach is to use the documented conversion functions only within the synchronization flow they were designed for. Because conversion results depend on the server's configured time zone, behavior differs between 12.1.1 and 12.2.2 only insofar as the underlying server time-zone configuration differs; the package logic is unchanged.