Search Results update_task_recurrence

Overview

The APPS.JTF_TASK_RECURRENCES_PUB_W package is a public PL/SQL API within the Oracle E-Business Suite CRM Foundation (JTF) module. It governs the creation and maintenance of recurring task definitions used by the Task Manager and resource scheduling components of EBS. In release 12.1.1 and 12.2.2, the package provides the programmatic interface through which applications define recurrence patterns for tasks, allowing a single task template to spawn multiple scheduled occurrences across a date range according to configurable rules.

The package follows the standard EBS API wrapper ("_PUB_W") convention, meaning it exposes a public, versioned interface that shields callers from the underlying private implementation and provides a stable contract for both Oracle-delivered forms and customer extensions. It is documented as an OTHER classification API, reflecting its role as a supporting utility rather than a transactional business object API such as those for orders or invoices.

Key Procedures and Functions

Four documented procedures comprise the package interface:

• ROSETTA_TABLE_COPY_IN_P1 — A generated table-copy helper that converts an incoming JTF_DATE_TABLE PL/SQL collection into the pl/sql record type jtf_task_recurrences_pub.output_dates_rec. It handles bulk transfer of date values from external callers into the package's internal recurrence-date structure.
• ROSETTA_TABLE_COPY_OUT_P1 — The inverse helper, copying the internal output_dates_rec structure back out to a caller-supplied JTF_DATE_TABLE. Together with the prior routine, these support the calculation and return of generated recurrence dates.
• CREATE_TASK_RECURRENCE — Establishes a new recurrence rule for a task. Based on the documented signature it accepts task identifiers, an "occurs which" pattern indicator, day-of-week and date-of-month settings, occurrence frequency (UOM and interval), active start and end dates, day-of-week flags (Sunday through Saturday), a template flag, and fifteen descriptive flexfield attribute columns plus an attribute category. It returns the new recurrence rule identifier, a count of recurrences generated, and standard x_return_status, x_msg_count, and x_msg_data messaging outputs.
• UPDATE_TASK_RECURRENCE — Modifies an existing recurrence rule. It accepts the task identifier, the recurrence rule identifier, and the recurrence parameters to be changed, applying the same validation and messaging conventions as the create routine.

Tables Accessed

The documented metadata lists a single referenced table accessed through an APPS synonym: PLITBLM. This is the standard EBS message and error-tracking table used by the messaging framework to retrieve the text of error and informational messages keyed by message name, ensuring consistent x_msg_data output. Recurrence definitions themselves are persisted in the JTF task recurrence base tables maintained by the private implementation that JTF_TASK_RECURRENCES_PUB_W wraps; the public package thereby mediates inserts and updates to recurrence rules and their associated generated date entries.

Usage Notes

JTF_TASK_RECURRENCES_PUB_W is typically invoked from Task Manager forms, scheduling concurrent programs, and custom PL/SQL integrations that automate recurring task setup. Because the metadata records that no other packages reference it, it is not an internal dependency of other documented APIs; callers should invoke it directly as the supported entry point for recurrence maintenance rather than reaching into the underlying worker package.

Standard EBS API conventions apply: callers should pass p_init_msg_list = FND_API.G_TRUE, inspect x_return_status for FND_API.G_RET_STS_SUCCESS, and loop over x_msg_count/x_msg_data to surface errors. Commit behavior is governed by the p_commit argument. The header revision 120.2 (dated 2006) remains consistent across the 12.1.1 and 12.2.2 code lines, so customizations built against it in 12.1.1 can generally be carried forward to 12.2.2 without interface changes, though regression testing is advised after any patching to the JTF task family.