Search Results jtf_task_workflow_process_s




Overview
Explore in AI Chat

Overview

APPS.JTF_EC_WORKFLOW_PKG is a PL/SQL package body in the Oracle E-Business Suite Applications (APPS) schema that implements mobile field service workflow integration for the E-Business Suite. The package supports the "Escalation" (EC) framework, which automates the routing of escalated service and task-related events through Oracle Workflow. Its principal role is to initiate, subscribe to, and manage workflow notifications associated with escalation records, task records, and the parties connected to them.

The package is validated and marked VALID in the ETRM metadata. It is classified as an "OTHER" API, meaning it is primarily an internal, non-published implementation package rather than an officially supported public API. It is referenced by one other database object, indicating it is invoked from within the JTF (Common Technology Foundation) task and mobile field service modules. In the context of Oracle EBS 12.1.1 and 12.2.2, this package depends on the Oracle Workflow engine (WF_ENGINE, WF_CORE, WF_DIRECTORY, WF_EVENT), the FND message and lookup infrastructure, and various JTF task and resource objects.

Key Procedures and Functions

The package exposes ten documented procedures and functions that collectively manage escalation workflow lifecycle and notification behavior.

  • START_RESC_WORKFLOW — Initiates a workflow process for a resource escalation, launching the configured workflow to drive subsequent notification and approval activity.
  • CHECK_EVENT — Validates whether a given event should be processed, providing gatekeeping logic before workflow or notification actions are taken.
  • SET_NOTIF_MESSAGE — Constructs or assigns the notification message body used in escalation workflow notifications.
  • SET_NOTIF_PERFORMER — Determines and assigns the performer (recipient role or user) for an escalation notification.
  • GET_DOC_DETAILS — Retrieves document or record details required to populate notification payloads and workflow attributes.
  • RAISE_ESC_CREATE_EVENT — Raises a workflow business event when an escalation record is created.
  • RAISE_ESC_UPDATE_EVENT — Raises a workflow business event when an escalation record is updated.
  • CREATE_ESC_NOTIF_SUBS — Creates notification subscriptions for escalation events so that appropriate recipients receive notifications.
  • UPDATE_ESC_NOTIF_SUBS — Updates existing notification subscriptions when escalation criteria or recipients change.

These routines work in concert: events raised on insert or update flow through subscription management to generate workflow notifications, with performer and message content supplied by the SET_NOTIF_* procedures.

Tables Accessed

The package reads and writes several JTF and Workflow tables through APPS synonyms. It queries and manipulates JTF_TASKS_B and JTF_TASK_CONTACTS to obtain task and contact information for escalations, and reads JTF_TASK_WORKFLOW_PROCESS_S to resolve the workflow process mapped to a task. Escalation status and event data are drawn from JTF_EC_STATUSES_VL and JTF_EC_WF_EVENTS_S. Object and party details are sourced from JTF_OBJECTS_B, JTF_OBJECTS_VL, HZ_PARTIES, and JTF_PARTY_ALL_CONTACTS_V, while employee/resource information is retrieved from JTF_RS_EMP_DTLS_VL, PER_ALL_PEOPLE_F, and PER_PEOPLE_F. Workflow state is read from WF_ITEM_ACTIVITY_STATUSES, WF_USERS, WF_ROLES, and WF_EVENT_T, and runtime parameters are passed via WF_PARAMETER_LIST_T. FND_USER supplies user identity, and DUAL and PLITBLM support utility and bulk operations.

Usage Notes

JTF_EC_WORKFLOW_PKG is typically invoked indirectly rather than called directly by end users. It fires when escalation records are created or updated within the field service and task management flows, most commonly triggered through Oracle Forms or through the Workflow Business Event System. The CREATE_ESC_NOTIF_SUBS and UPDATE_ESC_NOTIF_SUBS routines support subscription maintenance, often executed during configuration or setup of escalation notification rules. Because the package is classified as OTHER and is not referenced by other database objects, customizations should treat it as an internal dependency. Developers extending escalation behavior should account for its dependencies on FND_MSG_PUB, WF_ENGINE, and the JTF task tables, and should validate any modifications against both 12.1.1 and 12.2.2 environments given their shared reliance on this package.