Results for “jtf_task_confirmation_pub”
36 results
AI-generated from documented ETRM metadata — verify critical details on the linked pages.
Overview
JTF_TASK_CONFIRMATION_PUB is a public PL/SQL package in the APPS schema that supports the task confirmation feature of Oracle E-Business Suite. In Oracle Telephony, Field Service, and related task-management flows, a task assigned to a resource may require explicit confirmation by the assignee. The confirmation mechanism maintains both a status indicator (for example, required, confirmed, or rejected) and a numeric counter that records how many confirmation requests or responses have been accumulated against the task. JTF_TASK_CONFIRMATION_PUB exposes the public API surface through which forms, workflows, and custom code manipulate that confirmation state while preserving the standard EBS API contract.
The package follows Oracle's API conventions: procedures accept p_api_version, p_init_msg_list, and p_commit parameters, return x_return_status, x_msg_count, and x_msg_data, and delegate the actual persistence work to the private package JTF_TASKS_PVT. The documented source header identifies the file as jtfptcfb.pls version 120.2, indicating that the implementation has been stable since Release 11i-era maintenance and is carried forward unchanged into 12.1.1 and 12.2.2.
Key Procedures and Functions
- SET_COUNTER_STATUS — The primary driver procedure. It accepts a task identifier, a confirmation status value, and a confirmation counter value, then calls
jtf_tasks_pvt.update_taskto write the new status and counter onto the task record. It validates the caller's API version throughfnd_api.compatible_api_call, establishes a savepoint, and initializes the message list when requested. - RESET_COUNTER — Resets the confirmation counter associated with a task, typically to zero, without altering the confirmation status.
- INCREASE_COUNTER — Increments the confirmation counter by the appropriate amount, used when a new confirmation request or reminder is issued.
- DECREASE_COUNTER — Decrements the confirmation counter, applied when a confirmation event is withdrawn or reversed.
- CHANGE_COUNTER_SIGN — Reverses the sign of the counter value, supporting credit/reversal semantics without deleting the underlying task record. This is the procedure most frequently referenced by users investigating counter behavior.
- RESET_CONFIRMATION_STATUS — Returns the confirmation status of a task to its default or unconfirmed state.
- SET_CONFIRMATION_REQUIRED — Marks a task as requiring explicit confirmation from the assignee.
- SET_CONFIRMATION_CONFIRMED — Marks a task as confirmed, recording that the assignee has acknowledged it.
The package metadata documents twelve procedures and functions in total; in addition to the public entry points above, internal helper routines handle initialization and status derivation. None of these procedures expose a parameter list in the public metadata, so callers must rely on the ETRM-published signature or on the package specification shipped with the installation.
Tables Accessed
The documented table reference is JTF_TASKS_B, the base table holding task definitions in the Oracle Task Manager schema. The public package reads from the JTF_TASKS_VL view to retrieve the current task row, then writes confirmation status and counter values through JTF_TASKS_PVT, which ultimately updates the corresponding columns on JTF_TASKS_B. Because updates are performed inside a savepoint and with the standard API messaging model, failures roll back only the current API call when p_commit is false. No other application tables are documented as directly accessed by this package.
Usage Notes
JTF_TASK_CONFIRMATION_PUB is an API-classified public package (ETRM classification PUB) and is referenced by two other packages. It is typically invoked from Oracle Forms task and calendar windows, from workflow background processes that generate confirmation requests, and from custom PL/SQL code that needs to change confirmation state. Callers should always pass a valid p_api_version compatible with the packaged version (1.0 for the documented procedure), check x_return_status against fnd_api.g_ret_sts_success, and handle the p_object_version_number parameter for optimistic locking. Because JTF_TASKS_PVT performs the actual DML, direct updates to JTF_TASKS_B should be avoided; all confirmation counter and status changes should be routed through this package to preserve workflow and audit behavior.
-
12.2.2 DBA Data 12.2.2
-
12.1.1 DBA Data 12.1.1
-
12.1.1 DBA Data 12.1.1
-
12.2.2 DBA Data 12.2.2
-
SYNONYM: APPS.JTF_TASKS_B 12.1.1
-
SYNONYM: APPS.JTF_TASKS_B 12.2.2
-
VIEW: APPS.JTF_TASKS_VL 12.1.1
-
VIEW: APPS.JTF_TASKS_VL 12.2.2
-
12.2.2 DBA Data 12.2.2
-
12.2.2 DBA Data 12.2.2
-
12.1.1 DBA Data 12.1.1
-
12.1.1 DBA Data 12.1.1
-
eTRM - JTF Tables and Views 12.1.1
Interface table to store data that needs to be displayed in Excel
-
eTRM - JTF Tables and Views 12.1.1
Interface table to store data that needs to be displayed in Excel