Search Results jtf_task_workflow_pkg_w




Overview
Explore in AI Chat

Overview

JTF_TASK_WORKFLOW_PKG_W is a public wrapper package in the Oracle E-Business Suite Applications (APPS) schema that exposes the workflow-facing capabilities of the Task Management infrastructure delivered with the CRM Foundation (JTF) product family. Its primary business function is to initiate Oracle Workflow processes for tasks maintained by the Task Manager, allowing assignee and owner changes captured on a task record to drive the appropriate workflow notification and approval logic. The package acts as a thin, contract-stable entry point — a common Oracle EBS pattern in which the "_W" suffix denotes a wrapper that shields external callers from internal PL/SQL table typing and overloaded signatures used inside the base package JTF_TASK_WORKFLOW_PKG.

This wrapper is specifically designed to support the transfer of task detail data between the PL/SQL and Java/Workflow layers. It provides Rosetta-style conversion routines that flatten or reconstruct a nested PL/SQL collection type (task_details_tbl) into three parallel scalar VARCHAR2 tables, permitting interoperation with Java-based or OAF-side callers that cannot directly consume Oracle PL/SQL record collections.

Key Procedures and Functions

  • ROSETTA_TABLE_COPY_IN_P3 — Converts three parallel JTF_VARCHAR2_TABLE_100 collections inbound into the jtf_task_workflow_pkg.task_details_tbl nested table type. It is the ingress half of the Rosetta conversion pattern, used to marshal task detail attributes supplied by a Java or OAF caller into the structure required by the base package.
  • ROSETTA_TABLE_COPY_OUT_P3 — Performs the reverse conversion, expanding a populated task_details_tbl back out into three JTF_VARCHAR2_TABLE_100 collections. It is used to return task detail results to callers that operate on flat scalar arrays.
  • GET_WORKFLOW_DISP_NAME — A function that resolves and returns the display name of a workflow, accepting an item type and process name and a flag controlling error raising behavior. This supports presenting a human-readable workflow label to the user, typically on the Task Manager or workflow configuration UI.
  • START_TASK_WORKFLOW — The principal procedure of the package. It launches the task-related workflow invoked by the user search term "start_task_workflow". It accepts an API version, standard message-list and commit flags, the task identifier, the prior and new assignee codes and identifiers, the prior and new owner codes and identifiers, three detail collections (through the p12_a0/a1/a2 Rosetta arrays), and the event name together with the workflow display name, process name, and item type. It returns the standard EBS API out parameters x_return_status, x_msg_count, and x_msg_data for error handling.

Tables Accessed

The ETRM metadata documents a single referenced object via APPS synonym: PLITBLM, the standard Oracle EBS message/error stack table used by the FND_MSG_PUB messaging framework. Access to this table supports population of the x_msg_count and x_msg_data out parameters and the message list initialized by p_init_msg_list. Although the wrapper concentrates on marshaling and delegation, the underlying task detail and workflow instance data are managed by the base package JTF_TASK_WORKFLOW_PKG and the JTF_TASKS task schema.

Usage Notes

JTF_TASK_WORKFLOW_PKG_W is normally invoked from Oracle Forms, Oracle Application Framework (OAF) pages, or custom PL/SQL code in which a task's ownership or assignment changes and a corresponding workflow must be launched. The "_W" wrapper should be called rather than the base package when the caller is Java-based or OAF-based, because of the Rosetta conversion routines and the flat, stable signature. Callers are expected to pass a valid p_api_version and may request commit through p_commit. Return status must always be checked: x_return_status should be compared against FND_API.G_RET_STS_SUCCESS, and any error messages surfaced through the message stack.