Search Results default_task_details_tbl
Overview
JTF_TASK_WORKFLOW_PKG is an Oracle Applications (APPS) PL/SQL package that integrates the Oracle E-Business Suite Task Manager (JTF Tasks) with the Oracle Workflow engine. Its primary business function is to create, monitor, and terminate workflow processes that are attached to task records maintained in the JTF_TASKS schema. When a task is created, updated, or escalated, this package determines whether the task is subject to a workflow-driven business process and, if so, initiates the appropriate process, resolves its display name, and tracks its runtime state. It also exposes utility functions that other product modules, such as Advanced Service (CS) incidents and Marketing (AMS) tasks, rely upon to embed workflow behaviour into their own task-related business flows. Because the package is classified as API classification OTHER, it is treated as an internal supporting API rather than a public, customer-facing interface, though it is broadly referenced across the application suites.
Key Procedures and Functions
- START_TASK_WORKFLOW — Initiates a workflow process for a given task record, typically resolving the applicable process definition from the JTF_TASK_WORKFLOW_PROCESS_S setup table.
- ABORT_TASK_WORKFLOW — Terminates an active workflow associated with a task, used when tasks are cancelled or superseded.
- IS_TASK_ITEM_ACTIVE — Returns whether a workflow item for the task is currently active, enabling callers to avoid duplicate process launches.
- CHECK_EVENT — Validates whether a particular workflow event applies to a task, supporting conditional process triggering.
- GET_WORKFLOW_DISP_NAME — Retrieves the display name of the workflow associated with a task for presentation in forms and inquiries.
- DEFAULT_TASK_DETAILS_TBL — Populates a PL/SQL table of default task details, used to seed workflow attributes before process initiation.
Tables Accessed
The package reads and writes core Task Manager tables through APPS synonyms. JTF_TASKS_B and JTF_TASKS_TL supply the task definition and its translated attributes, while JTF_TASK_PRIORITIES_TL, JTF_TASK_STATUSES_TL, and JTF_TASK_TYPES_TL provide reference lookups. JTF_TASK_WORKFLOW_PROCESS_S maps task conditions to workflow process definitions. WF_ITEMS and WF_ITEM_ACTIVITY_STATUSES represent the active Workflow runtime, and FND_USER is used to resolve user identity involved in workflow routing. DUAL and PLITBLM are referenced for standard dual-table queries and PL/SQL table manipulation.
Usage Notes
JTF_TASK_WORKFLOW_PKG is normally invoked indirectly by the Task Manager forms and by dependent product packages rather than called directly by end users. It is referenced by six packages, including AMS_TASK_PVT, AMS_TASKS_V, CS_INCIDENTS_DIARY_V, JTF_BRM_3D_TASK_V, JTF_TASKS_V, and its own wrapper JTF_TASK_WORKFLOW_PKG_W, which means workflow start and abort operations often occur as side effects of saving a task, creating an incident diary entry, or running marketing campaign task logic. It depends on FND_API and SYS.STANDARD for standard API and error-handling constructs. Customisations that extend task workflows should call the governed wrapper or the documented procedures rather than manipulating WF_ITEMS directly, and should respect the JTF_TASK_WORKFLOW_PROCESS_S configuration to ensure consistent workflow initiation across EBS 12.1.1 and 12.2.2 environments.