Search Results create_task_recurrence




Overview
Explore in AI Chat

Overview

The APPS.JTF_TASK_RECURRENCES_PUB_OA_W package is a public PL/SQL API belonging to the Oracle E-Business Suite Task Manager (JTF) module, which underpins task and resource management across CRM and field service applications. The package provides a wrapper interface for creating task recurrences, allowing a task to be scheduled so that it repeats according to a defined pattern—daily, weekly, monthly, or at another cadence—within the Oracle EBS 12.1.1 and 12.2.2 environments. The _OA_W suffix identifies this as an Open Applications (OA) wrapper superimposed on the underlying public API, JTF_TASK_RECURRENCES_PUB, so that the recurrence creation logic can be invoked from OA Framework pages, business flows, and other integration surfaces. The package is declared AUTHID CURRENT_USER and carries the header identifier jtfbtkus.pls 115.1, indicating a long-established, relatively stable interface in the JTF codebase.

Key Procedures and Functions

  • CREATE_TASK_RECURRENCE — The principal business procedure. It accepts an API version, standard message-list and commit flags, the identity of the task to be recurring (p_task_id or p_task_number), and the parameters that define the recurrence pattern: which occurrence governs the schedule, whether the record is a template, day of week, date of month, month of the year, the recurrence unit and interval, the number of occurrences, and the active start and end dates. It also accepts the Sunday-through-Saturday indicator columns and fifteen descriptive attribute columns plus an attribute category for extensibility. On completion it returns the standard x_return_status, x_msg_count, and x_msg_data values together with the generated x_recurrence_rule_id, three positional out parameters, and the count of recurrences generated (x_reccurences_generated).
  • ROSETTA_TABLE_COPY_IN_P1 — A helper that copies a JTF_DATE_TABLE collection into the PL/SQL record structure jtf_task_recurrences_pub.output_dates_rec, converting a table-style payload into the record format expected by the wrapper.
  • ROSETTA_TABLE_COPY_OUT_P1 — The inverse helper, moving data from the output_dates_rec record back into a JTF_DATE_TABLE collection so that callers receive the generated date set in table form.

These two Rosetta procedures exist primarily to support the OA Framework layer, which cannot bind PL/SQL record types directly and therefore relies on table-to-record conversion.

Tables Accessed

The only table identified in the documented metadata is PLITBLM, referenced through an APPS synonym. In Oracle EBS, PLITBLM is a standard internal table used by the PL/SQL message-handling infrastructure for buffering and retrieving messages associated with the API's FND_MSG_PUB error stack. Its presence here confirms that the package participates in the standard message-list mechanism, storing and returning messages through x_msg_count and x_msg_data. The recurrence data itself is persisted by the underlying JTF_TASK_RECURRENCES_PUB layer into the JTF task recurrence tables, which the wrapper invokes rather than touching directly.

Usage Notes

This package is typically invoked from OA Framework task pages, from custom PL/SQL integration code, or from concurrent processing that needs to establish repeating task schedules programmatically. When called, the standard pattern applies: initialize the message list when p_init_msg_list is set, supply a valid task identifier and recurrence pattern, and pass p_commit as FND_API.G_TRUE only when the caller has no broader transaction to manage. Callers should always inspect x_return_status for FND_API.G_RET_STS_ERROR or G_RET_STS_UNEXP_ERROR and retrieve messages through FND_MSG_PUB, since the wrapper uses PLITBLM to stage them. Because the package is documented as referenced by zero other packages, it is best regarded as a leaf-level entry point rather than a shared internal dependency.