Search Results update_assignment_status

Overview

JTF_TASK_REPEAT_APPT_PVT is a private (PVT) PL/SQL package body owned by APPS in Oracle E-Business Suite. Its stated purpose, drawn from the package header comments in jtfvtkob.pls, is to "process the change of repeating appointments." In practical terms, the package provides the internal engine that propagates edits applied to a recurring task or appointment across the series of related task records that share a synchronization identifier. When a user modifies the time, duration, assignment, or other attributes of a repeating appointment, the business layer calls into this package to determine which tasks in the recurrence belong to the affected set and to apply the appropriate updates consistently.

The package originated in 2002 as part of the Oracle Task Manager / Task Recurrence functionality and remained largely stable through later releases, with the last documented changes dated 2006. It is classified as an API of type PVT, indicating that it is intended for internal consumption by other application modules rather than being a public, supported integration interface.

Key Procedures and Functions

The ETRM metadata documents a single procedure for this package: UPDATE_REPEAT_APPOINTMENT. This procedure is the core routine for applying changes across a repeating appointment series. It accepts a change mode governed by the package constants (notably c_future and c_all), which determines the scope of the update:

• c_future — Applies the modification to the current task and all subsequent occurrences of the series, checking the deleted_flag so that logically deleted occurrences are excluded.
• c_all — Applies the modification to the entire series regardless of where the change is initiated. Per the change history, in this mode the package does not test whether the task is the first task in the series.

The procedure coordinates related work through helper routines historically defined in jtf_task_utl and later moved to jta_sync_task_utl, including is_this_first_task, get_new_first_taskid, and exist_syncid. The package change history also references modify_time and an update_assignment_status routine. Notably, update_assignment_status was added on 08-Apr-2002 and commented out on 02-May-2002, meaning it is not part of the active, documented callable surface. Any custom code attempting to invoke it would fail.

Tables Accessed

The package reads and writes across the task model tables accessed through APPS synonyms:

• JTF_TASKS_B — Core task records; object_changed_date and last_update_date are updated with SYSDATE.
• JTF_TASKS_TL — Translated (language-dependent) task attributes.
• JTF_TASK_ALL_ASSIGNMENTS — Task-to-resource assignment data modified during series updates.
• JTA_SYNC_TASK_MAPPING — Maps synchronized tasks, used to identify series members.
• JTA_TASK_EXCLUSIONS and JTA_TASK_EXCLUSIONS_S — Excluded occurrence records and their sequence.
• JTF_TASK_RECUR_RULES and JTF_TASK_RECUR_RULES_S — Recurrence rule definitions and their sequence.
• DUAL — Used for scalar evaluations.

Usage Notes

JTF_TASK_REPEAT_APPT_PVT is referenced by six other packages, confirming it is an internal dependency of the task management stack rather than a directly invoked API. It is typically called when a form or business process modifies a recurring appointment and the change must be rolled out to the remainder of the series. Custom developers should not call this package directly; the supported entry points reside in the corresponding public task APIs. The recurrence-rule and exclusion table dependencies also make it sensitive to the integrity of the sync mapping data, so any custom manipulation of JTA_SYNC_TASK_MAPPING or the exclusion tables can directly affect repeat-appointment behavior.