Search Results wfj_queue




Overview
Explore in AI Chat

Overview

WFJ_QUEUE is an Oracle Workflow Java (WFJ) support package owned by the APPS schema in Oracle E-Business Suite 12.1.1 and 12.2.2. It is classified in the ETRM repository under the API classification OTHER, indicating that it is an internal infrastructure package rather than a published, customer-facing API. The package provides the PL/SQL-side plumbing that allows the Oracle Workflow Java engine and the Business Event System to hand work items and event payloads back and forth through the database. Specifically, WFJ_QUEUE manages the enqueueing of inbound messages and the dequeueing of outbound messages on Workflow queues, together with the manipulation of the event data payload attached to those messages. Because it is referenced by zero other documented packages, it is best understood as a leaf-level utility invoked by the Workflow Java layer, the Workflow Agent Listener, or by custom code that must interact with the same queue structures.

Key Procedures and Functions

The ETRM metadata documents seven program units within WFJ_QUEUE. Their names describe their roles:

  • ENQUEUEINBOUND — places an inbound message onto the Workflow queue so that it can be processed by the inbound agent or listener. It is the entry point used to make a message available for Workflow consumption.
  • DEQUEUEOUTBOUND — removes the next available outbound message from the queue for delivery. It controls the sequencing by which Workflow hands messages to its outbound agents.
  • GETEVENTDATA — retrieves the event data payload associated with a queue message. This payload carries the business event attributes that will be raised or consumed by the Business Event System.
  • SETEVENTDATA — writes or replaces the event data payload for a queue message, allowing the message contents to be assembled or modified before enqueue or after dequeue.
  • APPLYTRANSFORMATION — applies an event transformation to the message payload, permitting the data structure to be converted between the format expected by the sender and the format expected by the receiver.
  • SETDEQUEUEDELAY — configures the delay interval applied when dequeueing, allowing retry and backoff behaviour for messages that are not immediately processable.
  • GETDEQUEUEDELAY — returns the currently configured dequeue delay value.

Tables Accessed

WFJ_QUEUE operates against the Workflow event and attribute tables, accessed through APPS synonyms. WF_EVENT_T is the core Business Event System table holding event definitions and, in the case of this package, event instances as they are moved through the queue; it underpins the GETEVENTDATA and SETEVENTDATA operations. WF_ITEM_ATTRIBUTE_VALUES stores the item attribute values associated with a Workflow item, and it is read or written when event and item data must be synchronised with the queued message. In addition, the package depends on DBMS_AQ, the Oracle Advanced Queuing PL/SQL package, which supplies the underlying enqueue and dequeue primitives that WFJ_QUEUE wraps. The remaining documented dependency is the SYS.STANDARD package, reflecting the normal PL/SQL runtime environment rather than any application data access.

Usage Notes

WFJ_QUEUE is an internal Workflow component and is not intended for direct invocation by end users. In practice it is called by the Oracle Workflow Java services and by the Workflow queue-handling infrastructure rather than from an Oracle Forms screen or a standard concurrent program. Customisations and extensions should avoid calling these procedures directly where a supported Workflow PL/SQL API exists, since the internal signature and behaviour are not part of the published interface and may change between point releases. Where custom code must interact with the Workflow queue, the preferred approach is to use the supported Workflow and Business Event System APIs, which in turn rely on packages such as WFJ_QUEUE. Administrators monitoring Workflow throughput should be aware that failures or delays surfaced by outbound message processing, retry behaviour, or event transformation frequently trace back to the dequeue delay and event data routines documented above.