Search Results resume_wf_eq

Overview

XDP_AQ_UTILITIES is an Oracle Application Object Library package owned by the APPS schema that centralizes Advanced Queuing (AQ) and Workflow enqueue/dequeue operations for the Oracle E-Business Suite supply chain and fulfillment execution modules. Its primary business function is to manage the lifecycle of Oracle Workflow queues used by Distributed Order Orchestration, Fusion Order Processing, and related fulfillment engines. The package abstracts the low-level DBMS_AQ API calls required to create, start, stop, drop, and monitor queues, and it orchestrates the handoff between queued messages and running Workflow processes. In the context of a search for xnp_message, XDP_AQ_UTILITIES is a direct dependency of the APPS.XNP_MESSAGE object; XNP_MESSAGE references XDP_AQ_UTILITIES and XDP_AQ_UTILITIES in turn depends on XNP_MESSAGE, indicating a tightly coupled messaging layer where the messaging infrastructure relies on this package to enqueue and dequeue the notification events it publishes. The package function is therefore foundational to the reliability of asynchronous communication across the fulfillment stack.

Key Procedures and Functions

The documented interface exposes roughly fifty procedures and functions. Queue lifecycle management is handled by START_WF_AQ, STOP_WF_AQ, and DROP_WF_AQ, which respectively start, halt, and remove the Workflow AQ infrastructure. REMOVE_PENDING_ORDER and PENDING_ORDER_EQ/PENDING_ORDER_DQ support inspection and cleanup of pending orders held on the queue. ADD_ORDERTOPROCESSORQ and START_ORDERPROCESSOR_WORKFLOW place orders onto the processor queue and launch the associated workflow. ADD_WORKITEM_TOQ and START_WORKITEM_WORKFLOW provide the equivalent operations for work items. ADD_FA_TOQ and START_FA_WORKFLOW enqueue fulfillment actions and start their workflow. Channel and workflow control routines include HANDOVER_CHANNEL, RESUME_NEXT_WF, SDP_RESUME_WF, RESUME_WF_EQ, and RESUME_PARENT_WORKFLOW, which manage transitions between workflows and parent/child workflow chains. GET_QUEUE_STATE returns queue status for monitoring, while DISABLE_SDP_AQ and ENABLE_SDP_AQ toggle the SDP advanced queue between active and inactive states, typically for maintenance windows.

Tables Accessed

Through APPS synonyms the package reads and writes the operational tables of the fulfillment engine: XDP_ORDER_HEADERS and XDP_ORDER_LINE_ITEMS for order data; XDP_FULFILL_ACTIONS and XDP_FULFILL_WORKLIST for action and worklist tracking; XDP_FA_RUNTIME_LIST for fulfillment action execution; XDP_FES for fulfillment execution state; XDP_DQ_CONFIGURATION for dequeue configuration settings; and XDP_ADAPTER_JOB_QUEUE with its sequence XDP_ADAPTER_JOB_QUEUE_S for adapter job enqueueing. Audit trails are recorded in XDP_FE_CMD_AUD_TRAILS and its sequence. The queue tables AQ$XNP_OUT_MSG_QTAB and XDP_PENDING_ORDER_QTAB back the actual AQ message storage, and FND_LOOKUP_VALUES supplies reference lookup values. DBMS_AQ is invoked directly for the underlying enqueue and dequeue primitives.

Usage Notes

XDP_AQ_UTILITIES is referenced by eight other packages, including XDPCORE_FA, XDPCORE_WI, XDP_ENG_UTIL, XDP_ORDER, XDP_PROC_CTL, XNP_EVENT, XNP_MESSAGE, and XNP_TIMER_MGR. It is typically invoked indirectly by these fulfillment and notification engine packages rather than directly by end users, and it is also self-referential. Administrators or concurrent programs may call the queue lifecycle routines (START_WF_AQ, STOP_WF_AQ, DROP_WF_AQ, DISABLE_SDP_AQ, ENABLE_SDP_AQ) during system setup or maintenance. Custom code interacting with the fulfillment queue should use the documented procedures rather than manipulating AQ tables directly, preserving workflow orchestration integrity.