Search Results execute_selector_function

Overview

WF_ENGINE_UTIL is an internal utility package in the Oracle Workflow engine layer of Oracle E-Business Suite, owned by the APPS schema. It is classified as a UTIL package and is documented as VALID in both Oracle EBS 12.1.1 and 12.2.2. Where WF_ENGINE exposes the primary runtime entry points for running a workflow process, WF_ENGINE_UTIL provides the lower-level building blocks that the engine and its callers rely on: manipulating the process stack, resolving activity parents, moving items through activities, executing function and selector calls, and managing child processes and notifications. The package is not intended as a public end-user API; it is a supporting library whose behavior underpins workflow runtime semantics such as activity execution, completion, reset, and history migration.

Key Procedures and Functions

The documented API surface comprises 28 procedures and functions. These can be grouped by purpose:

• Caching and process stack management: CLEARCACHE, ADDPROCESSSTACK, and REMOVEPROCESSSTACK manage the in-memory representation of the workflow process execution stack used by the engine.
• Activity execution and lifecycle: PROCESS_ACTIVITY, EXECUTE_ACTIVITY, COMPLETE_ACTIVITY, and ACTIVITY_PARENT_PROCESS drive a workflow activity through its execution path, resolve its parent process context, and mark completion.
• Reset and history operations: RESET_ACTIVITIES, RESET_TREE, and MOVE_TO_HISTORY allow workflow administrators and engine internals to reset activity state and relocate completed status rows into history tables.
• Function and selector invocation: FUNCTION_CALL and EXECUTE_SELECTOR_FUNCTION evaluate named workflow functions and selector functions associated with activities.
• Process hierarchy and control: GET_ROOT_PROCESS, START_PROCESS_INTERNAL, PROCESS_KILL_CHILDPROCESS, PROCESS_KILL_CHILDREN, SUSPEND_CHILD_PROCESSES, and RESUME_CHILD_PROCESSES manage parent/child process relationships and control lifecycle of subordinate processes.
• Notification handling: NOTIFICATION and NOTIFICATION_SEND provide the utility layer used to compose and dispatch workflow notifications to recipients.

Tables Accessed

WF_ENGINE_UTIL reads and writes the core runtime tables of the Workflow schema, accessed through APPS synonyms. It references WF_ITEMS and WF_ITEM_TYPES for item and process definition context; WF_ACTIVITIES, WF_ACTIVITY_ATTR_VALUES, WF_ACTIVITY_TRANSITIONS, and WF_ITEM_ACTIVITY_STATUSES (plus the _H history table) for activity execution, attribute resolution, transition routing, and status persistence; WF_NOTIFICATIONS, WF_NOTIFICATIONS_S, WF_NOTIFICATION_ATTRIBUTES, and WF_MESSAGE_ATTRIBUTES for notification composition and delivery; WF_COMMENTS and WF_AGENT_T for comments and agent assignment; WF_EVENT_T for event capture; and WF_ERROR_PROCESSES_S for error process handling. Collectively these tables support the transactional lifecycle of a workflow item as it moves from activity to activity.

Usage Notes

WF_ENGINE_UTIL is referenced by 18 other packages, including WF_ENGINE, WF_ENGINE_BULK, WF_STANDARD, WF_MONITOR, WF_QUEUE, WF_ITEM_ACTIVITY_STATUS, and FND_WF_STANDARD, as well as application packages such as OE_CREDIT_WF, PO_WF_UTIL_PKG, PO_NEGOTIATIONS_SV2, LNS_DISTRIBUTIONS_PUB, and several HR performance-management packages. Customers and integrators should treat it as an internal engine utility rather than a supported public API; custom code that requires workflow operations should normally call the documented WF_ENGINE or WF_STANDARD entry points instead. Because its interfaces can change between EBS releases and patches, any direct invocation should be validated against the specific 12.1.1 or 12.2.2 instance and tested after applying workflow-family patches. It is most commonly exercised indirectly whenever a workflow item is launched, an activity completes, an item is reset, or a notification is sent from standard EBS flows.