Search Results exclude_modified_repeat_appts




Overview
Explore in AI Chat

Overview

JTF_TASK_SYNC_UPGRADE_PKG is an Oracle Applications database package owned by APPS and declared with AUTHID CURRENT_USER. Its purpose, as stated in the package header, is to migrate existing task data so that it can function correctly with the synchronization feature introduced in Oracle E-Business Suite. The package was created in August 2002 (header revision 115.0) to remediate data inconsistencies produced by earlier releases, most notably defects in the Repeating Appointment API that generated repeating appointments on dates that should not have been created. Because the synchronization code depends on well-formed recurrence data, these legacy inconsistencies would otherwise cause errors during synchronization. The package is classified as OTHER rather than as a public API, indicating that it supports a one-time or upgrade-style data migration path rather than ongoing runtime business logic. It is referenced by zero other packages, confirming that it stands alone as a remediation utility. In the ETRM 12.2.2 metadata, six procedures are documented; the ETRM 12.1.1 metadata describes the same object lineage, since the package predates both releases and remains present in the APPS schema.

Key Procedures and Functions

  • UPDATE_INVALID_REPEATING_APPS — Scans repeating appointment series and repairs four categories of recurrence defects: invalid dates (removed from the repeating series), extra dates (removed from the series), missing dates (inserted into the exclusion table), and duplicate dates (removed from the series). No appointments are deleted and no exclusions are created for the removal cases; only missing dates produce exclusion rows. Invalid start times or durations are not corrected by this procedure.
  • INITIALIZE_OBJECT_CHANGED_DATE — Initializes the object changed-date values on task records as part of the migration, establishing a consistent baseline timestamp for synchronization change tracking.
  • EXCLUDE_MODIFIED_REPEAT_APPTS — Identifies modified repeating appointments and records the appropriate exclusions so that synchronization does not reinterpret user-modified occurrences as recurrence anomalies.
  • CORRECT_RECURRENCE_RULE — Repairs the recurrence rule associated with a repeating appointment series, nullifying or adjusting the rule where the underlying dates or occurrences are inconsistent.
  • RESET_ASSIGNMENT_STATUS — Resets the status of task assignments so that legacy assignment records conform to the states expected by the synchronization function. This procedure supports the user search term directly and is the documented entry point for repairing assignment-level data prior to or alongside sync enablement.
  • NULLIFY_WRONG_ASSIGNMENTS — Clears incorrect assignment records, presumably removing or deactivating assignments that would otherwise conflict with synchronization processing of the parent task.

Tables Accessed

The package operates against the following APPS-synonymed tables:

  • JTF_TASKS_B — the base task table; read for repeating appointment series and written when recurrence rules or changed-date values are adjusted.
  • JTF_TASK_RECUR_RULES — stores recurrence rules; corrected or nullified by CORRECT_RECURRENCE_RULE.
  • JTA_TASK_EXCLUSIONS_S — the exclusion table populated when missing dates are detected in a repeating series.
  • JTF_TASK_ALL_ASSIGNMENTS — task assignment records; read and updated by RESET_ASSIGNMENT_STATUS and NULLIFY_WRONG_ASSIGNMENTS.
  • DUAL — used for single-row queries and constant evaluation.
  • PLITBLM — a PL/SQL table/index-by-table construct used for in-memory collections during processing.

Usage Notes

JTF_TASK_SYNC_UPGRADE_PKG is an upgrade-time remediation utility rather than a runtime API. It is intended to be invoked once during the upgrade or migration that enables task synchronization, typically as a step within an upgrade driver or a one-off concurrent program executed by an administrator. Because it is not referenced by any other package, it has no automatic caller within the application and must be launched explicitly. When diagnosing the search term "reset_assignment_status," the relevant action is to invoke the RESET_ASSIGNMENT_STATUS procedure alone if only assignment statuses must be normalized, or to run the full migration sequence (update_invalid_repeating_appts, initialize_object_changed_date, exclude_modified_repeat_appts, correct_recurrence_rule, reset_assignment_status, nullify_wrong_assignments) when preparing an entire task dataset for synchronization. As with all upgrade packages, it should be executed in a controlled maintenance window with a validated backup, since it modifies task, assignment, exclusion, and recurrence data in the APPS schema.