Search Results create_ids

Overview

JTA_SYNC_TASK is a PL/SQL package owned by the APPS schema in Oracle E-Business Suite. It provides the top-level application programming interface for synchronizing tasks (to-dos) and appointments between the EBS Calendar/Task framework and external or remote clients. The package was introduced in 2002 and is declared with AUTHID CURRENT_USER, meaning its SQL statements execute under the privileges of the calling user rather than the defining user. The header comments in the source, filed as jtavstss.pls, describe its purpose as "top level API for syncing tasks(todos) and appointments," with a documented evolution covering recurrence support, exclusion handling, and progressive expansion of field lengths (category grows to 255 characters, subject to 2000, description to 4000).

The central data structure exposed by the package is the task_rec record type, which carries a unique sync ID, a relative record index, the task ID, a sync anchor date, a time zone ID, an event type ("New," "Delete," or "Modify"), and common task fields such as object code ("TASK" or "APPOINTMENT"), subject, description, and planned start/end dates. This record type is the vehicle through which transaction data is exchanged during a synchronization cycle.

Key Procedures and Functions

The ETRM metadata documents five entry points in this package:

• GET_COUNT — Returns the number of task or appointment records that qualify for a given synchronization request, allowing a client to size its payload before retrieval.
• GET_LIST — Retrieves the qualifying set of task and appointment records for synchronization, populating the task_rec structure for each.
• CREATE_IDS — Establishes or allocates the identifier values required by the synchronization process, mapping incoming external records to internal EBS task identities.
• UPDATE_DATA — Applies modifications to existing synchronized task or appointment records, corresponding to "Modify" events.
• DELETE_DATA — Removes synchronized task or appointment records, corresponding to "Delete" events.

Together these procedures form a complete publish/apply cycle: a client first determines the volume of pending work, then fetches the records, then applies creations, updates, and deletions back into the repository.

Tables Accessed

The package references three objects through APPS synonyms. JTA_SYNC_TASK_MAPPING_S is the principal persistent table and stores the mapping between external synchronization identifiers and native EBS task records; it is the backbone of the sync identity model that CREATE_IDS and the other procedures rely upon. DUAL is used for simple scalar evaluations and sequence-adjacent operations. PLITBLM is the standard PL/SQL indexed-table-of-varchar2 helper type used for passing collections of identifiers or values between procedures. The package does not directly manipulate the core task tables; synchronization is mediated through the mapping table.

Usage Notes

JTA_SYNC_TASK is classified as an OTHER API within the ETRM inventory, indicating it is intended primarily for internal or integration-layer consumption rather than broad customer-facing use. The metadata records that the package is referenced by four other packages, confirming that it occupies a mid-tier position in the synchronization stack. In practice it is invoked by synchronization engine code and concurrent programs that reconcile EBS Calendar data with external clients, and by custom integration code performing bulk task and appointment transfers. Because the package executes with AUTHID CURRENT_USER, callers must possess the necessary privileges on the underlying JTA objects. The presence of syncId, recordIndex, and syncAnchor fields indicates the API expects batched, incremental synchronization rather than single-record transactional calls. Developers extending the integration should preserve the existing task_rec field semantics and honor the "New," "Delete," and "Modify" event type contract when driving the create, update, and delete procedures.