Search Results convert_server_to_gmt

Overview

JTA_SYNC_TASK_COMMON is a shared PL/SQL package body in the Oracle E-Business Suite Applications (APPS) schema that supports synchronization of Oracle Task Manager (JTA) task and appointment records across the E-Business Suite and its associated calendar, resource, and client environments. Its source header (jtavstcb.pls, revision 120.2) identifies it as a "common" utility layer for the sync task, consolidating logic shared between multiple synchronization entry points rather than exposing a single business-facing API. The package provides the reference data lookups, time-zone conversion routines, date adjustment helpers, and access-control checks that the sync process requires before task data can be created, updated, or deleted. It is classified as an OTHER API in the ETRM repository for 12.2.2 and is also present in 12.1.1, and it is referenced by four other packages, confirming its role as a dependency of higher-level synchronization logic rather than an externally called interface.

Key Procedures and Functions

The package exposes 46 documented procedures and functions. The time-handling group is directly relevant to the search term "convert_gmt_to_task": CONVERT_GMT_TO_TASK converts a stored GMT timestamp into the task-local time zone, while CONVERT_GMT_TO_CLIENT, CONVERT_GMT_TO_SERVER, CONVERT_TASK_TO_GMT, and CONVERT_SERVER_TO_GMT perform the complementary conversions among client, server, task, and GMT representations. CONVERT_DATES and ADJUST_TIMEZONE provide broader date normalization and offset handling, and SET_ALARM_DATE (referenced in the change history) supports alarm scheduling.

Resource and calendar lookups are handled by GET_RESOURCE_DETAILS, GET_GROUP_CALENDAR, GET_GROUP_RESOURCE, and GET_MAX_ENDDATE. Scheduling attributes are retrieved through GET_ALARM_MINS and GET_CLIENT_PRIORITY, while MAKE_PREFIX supports key or identifier construction. Access and ownership checks are provided by GET_ACCESS, GET_OWNER_INFO, GET_ASSIGNMENT_ID, GET_ASSIGNMENT_STATUS_ID, and GET_ASSIGNMENT_INFO, with CHECK_DELETE_DATA validating whether deletion is permitted. The change log documents additional internal members such as GET_EVENT_TYPE, GET_ALL_NONREPEAT_TASKS, GET_ALL_REPEAT_TASKS, CREATE_NEW_DATA, UPDATE_EXISTING_DATA, ADD_TASK, ADD_NONREPEAT_TASK, ADD_REPEAT_TASK, DELETE_EXCLUSION_TASK, DELETE_TASK_DATA, REJECT_TASK_DATA, CHANGED_REPEAT_RULE, UPDATE_REPEATING_RULE, CAN_UPDATE_TASK, and GET_EVENT_TYPE. Notably, the 20-Feb-2002 entry records that conversions between Task and Appointment are deliberately not synchronized, and tasks on public calendars are excluded.

Tables Accessed

Through APPS synonyms the package reads and writes JTA_SYNC_TASK_MAPPING and JTA_SYNC_TASK_MAPPING_S, which hold the mapping between source and synchronized task records, and JTA_TASK_EXCLUSIONS, which stores dates excluded from repeating tasks. Resource and team data come from JTF_RS_GROUPS_B, JTF_RS_GROUPS_TL, JTF_RS_GROUP_MEMBERS, JTF_RS_GROUP_USAGES, JTF_RS_RESOURCE_EXTNS, and JTF_RS_TEAM_MEMBERS, supporting the group, calendar, and resource lookups. WF-style state responsibility and rule definitions are read from JTF_STATE_RESPONSIBILITIES and JTF_STATE_RULES_B, and access decisions draw on FND_USER, FND_GRANTS, FND_MENUS, and FND_OBJECTS for user identity and function/object privileges.

Usage Notes

JTA_SYNC_TASK_COMMON is not intended for direct end-user invocation. It is called by the four dependent packages and by the sync task framework during task and appointment synchronization, typically triggered from Task Manager forms, the calendar or resource administration flows, and scheduled concurrent processing. Custom code should treat it as an internal dependency: callers should not assume stable signatures, and any direct use of CONVERT_GMT_TO_TASK must supply GMT input already validated against the task time-zone definition, since the routine performs conversion only and does not validate the target zone.