Search Results do_notification

Overview

JTF_TASK_WF_UTIL_W is a public PL/SQL package owned by the APPS schema in Oracle E-Business Suite 12.1.1 and 12.2.2. It belongs to the Oracle Task Manager / Resource Manager family of modules (the JTF product prefix) and provides the workflow-facing interface for task notification processing. Its declared purpose is to determine whether a notification should be emitted for a given task and, when required, to construct and launch the corresponding Oracle Workflow notification. The package is defined with AUTHID CURRENT_USER, meaning that name resolution and privilege checking occur against the invoking schema rather than the package owner.

The "_W" suffix convention in Oracle EBS designates a wrapper or published interface package — typically an invoker-rights shell that delegates to an underlying implementation package, here named jtf_task_wf_util. The wrapper shields callers from the internal table type jtf_task_wf_util.nlist_tbl_type and from direct construction of the implementation's data structures, providing a stable signature for form-based and concurrent callers.

Key Procedures and Functions

• DO_NOTIFICATION — Accepts a task identifier and returns a Boolean-valued OUT parameter (ddrosetta_retval_bool) indicating whether a notification applies to that task. The name matches the user search term "do_notification". This procedure is the decision point invoked by callers to determine whether create_notification should subsequently be executed, allowing notification logic to be gated by task state, assignment, or business rules.
• CREATE_NOTIFICATION — Performs the substantive notification work. It accepts an event name and a task identifier, together with before-and-after images of the task attributes: old and new owner, old and new assignee, old type, priority, and status, the previous planned, scheduled, and actual start and end dates, the previous description, and an abort-workflow indicator. It returns the standard EBS API status triple (x_return_status, x_msg_count, x_msg_data) for error reporting.
• ROSETTA_TABLE_COPY_IN_P4 — A Rosetta-generated conversion routine that copies three parallel JTF_VARCHAR2_TABLE_400 collections into the implementation's internal nlist_tbl_type. This is the inbound half of the wrapper's marshalling layer.
• ROSETTA_TABLE_COPY_OUT_P4 — The symmetric outbound routine, copying values from nlist_tbl_type back into three out NOCOPY JTF_VARCHAR2_TABLE_400 collections.

Tables Accessed

The ETRM metadata records a single referenced table, access to which is made through an APPS synonym: PLITBLM. This is a standard Oracle EBS temporary/working table used by PL/SQL table and bulk-processing utilities to stage collection data between sessions. The package does not appear to read or write the JTF task entity tables directly; instead, callers supply task attribute values as scalar parameters, and the underlying implementation package presumably handles persistence and workflow invocation.

Usage Notes

JTF_TASK_WF_UTIL_W is not referenced by any other documented package, indicating that it is an entry point for external callers rather than an internal library. Typical invocation is from Task Manager forms, workflow function activities, or custom code that needs to raise a task notification after an assignment, status, priority, or date change. The standard pattern is to call do_notification first to evaluate eligibility, then pass the event name and old/new attribute images to create_notification, checking x_return_status for success and inspecting x_msg_data on failure. The Rosetta copy routines are intended for integration-layer marshalling and should not normally be called directly by application code.