Search Results convert_gmt_to_client

Overview

JTA_SYNC_TASK_COMMON is an Oracle E-Business Suite PL/SQL package owned by the APPS schema and declared with AUTHID CURRENT_USER. Its header carries the source identifier jtavstcs.pls, version 115.58, and the internal description "This package is a common for sync task." It functions as the shared calendar and task-synchronization backbone for the Oracle Task Manager / Calendar (JTA) module, providing the low-level primitives that move task, assignment, alarm, and recurrence data between the EBS database and external synchronization clients such as desktop calendaring or groupware connectors.

The package history shows an intensive refactoring effort during February and March 2002 by developers cjang, sanjeev, and arpatel. Successive revisions added recurrence handling, task conversion routines, deletion and rejection logic, exclusion support, mapping maintenance, and status transformation. The result is a cohesive API layer whose procedures and functions are reused by four other packages in the JTA schema, establishing it as a common dependency rather than an end-user entry point.

Key Procedures and Functions

The package exposes 46 documented procedures and functions, which fall into several logical groups:

• Resource and access resolution: GET_RESOURCE_DETAILS, GET_GROUP_RESOURCE, GET_GROUP_CALENDAR, GET_OWNER_INFO, GET_ASSIGNMENT_INFO, GET_ASSIGNMENT_ID, GET_ASSIGNMENT_STATUS_ID, GET_ACCESS, GET_CLIENT_PRIORITY. These resolve the resource, group, owner, and security context for a task so that synchronization respects assignment and access rules.
• Alarm and priority handling: GET_ALARM_MINS, GET_CLIENT_PRIORITY, GET_MAX_ENDDATE. These derive alarm offsets, client-priority values, and the maximum end date permitted for synchronized records.
• Time zone conversion: CONVERT_GMT_TO_CLIENT, CONVERT_GMT_TO_TASK, CONVERT_TASK_TO_GMT, CONVERT_SERVER_TO_GMT, CONVERT_GMT_TO_SERVER, CONVERT_DATES, ADJUST_TIMEZONE. Together these normalize dates between server GMT storage and client-local representations, which is essential for multi-region deployments.
• Data validation and utilities: CHECK_DELETE_DATA, MAKE_PREFIX. CHECK_DELETE_DATA validates whether a task may be removed; MAKE_PREFIX builds the identifier prefix used in mapping records.
• Task and recurrence maintenance: The header notes reference add_task, add_nonrepeat_task, add_repeat_task, add_task_with_recurrence, create_new_data, update_existing_data, get_all_repeat_tasks, get_all_nonrepeat_tasks, delete_task_data, delete_exclusion_task, reject_task_data, changed_repeat_rule, update_repeating_rule, insert_or_update_mapping, transformStatus, and getChangedStatusId. These procedures and functions create, update, delete, and reconcile synchronization records, including recurring series and exclusion instances. The parameter set of add_task was explicitly revised during the 06-Mar-2002 refactoring.

Tables Accessed

The package reads and writes a set of APPS synonyms that span security, resource, and synchronization data:

• Synchronization mapping: JTA_SYNC_TASK_MAPPING and JTA_SYNC_TASK_MAPPING_S store the durable correspondence between EBS tasks and external client objects. Insert_or_update_mapping maintains these records.
• Task exclusions: JTA_TASK_EXCLUSIONS supports recurring-task exception handling used by delete_exclusion_task and related routines.
• Resource model: 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 provide group, team, and resource attributes used in resolving calendars and assignments.
• Security and workflow: JTF_STATE_RESPONSIBILITIES and JTF_STATE_RULES_B supply state-rule and responsibility context used by status transformation and access checks.
• Foundation: FND_USER, FND_OBJECTS, FND_MENUS, and FND_GRANTS support user identification, object and menu metadata, and function-security grant evaluation via GET_ACCESS.

Usage Notes

JTA_SYNC_TASK_COMMON is not intended as a direct user-facing interface. It is invoked indirectly from the Oracle Calendar and Task Manager forms, from concurrent programs that reconcile task data, and from the four dependent JTA packages that call into it. Custom integrations that implement task synchronization should call the documented API rather than manipulate the mapping or exclusion tables directly, because timezone normalization, mapping maintenance, and recurrence expansion are performed inside these routines.

Because the package uses AUTHID CURRENT_USER, privileges are evaluated against the invoking schema, so any custom caller must hold appropriate grants on the referenced JTA, JTF, and FND tables. Most of the documented history records refactoring rather than functional change, signaling that the interface is stable across EBS 12.1.1 and 12.2.2, though the 12.2 online patching architecture means the package must not be modified in a running file system edition without adopting the editioning model.