Search Results phase_maxthreshold

Overview

APPS.WF_EVENT is the core PL/SQL package of the Oracle Workflow Business Event System (product OWF). It provides the programmatic APIs through which the E-Business Suite communicates with the Business Event System and manages events. In practical terms, the package is responsible for raising events, resolving the subscriptions that a given event matches, executing the associated subscription code (rule functions, workflow processes, or agents), and controlling how events are dequeued from the underlying Advanced Queuing infrastructure.

The package is classified as a public API (API classification OTHER, compatibility S, lifecycle active) and is tagged to the business entity WF_EVENT. It is one of the most widely reused components in the EBS technology stack: the ETRM metadata records that it is referenced by 664 other packages, including the Oracle Workflow engine itself as well as application modules that emit or consume business events.

Key Procedures and Functions

Only the documented 43 procedures and functions are supported for direct use; the private variables in the package body (for example the phase threshold variables, navigation cursor, and account name) are explicitly marked as not for customer use.

• RAISE — Raises a business event into the Business Event System, making it available for subscription processing.
• SEND — Sends an event directly, bypassing normal raise semantics, to the intended recipient or event queue.
• DISPATCH and DISPATCH_INTERNAL — Determine which subscriptions should execute for an event and invoke them. The documented phase min/max threshold variables and PHASE_MAXTHRESHOLD / PHASE_MINTHRESHOLD constrain dispatch to subscriptions within a phase range.
• ENQUEUE and DEQUEUE — Enqueue and dequeue event messages against the underlying AQ queue.
• LISTEN, LISTEN_CONCURRENT, LISTEN_GRP, LISTEN_GRP_CONCURRENT — Dequeue events and process them. LISTEN and LISTEN_GRP run a single listening loop, while the _CONCURRENT variants are designed to be executed as synchronous or concurrent listeners so that event processing does not block the calling session.
• TEST — Validates event, agent, and parameter configuration.
• NEWAGENT, SET_RECIPIENT_LIST — Construct agent records and manage the list of intended recipients on an event.
• Parameter utilities — ADDPARAMETERTOLIST, ADDPARAMETERTOLISTPOS, GETVALUEFORPARAMETER, and GETVALUEFORPARAMETERPOS manipulate the parameter list attached to an event or agent.
• SETDISPATCHMODE, INITPHASEMINTHRESHOLD, SETERRORINFO — Control dispatch behaviour, initialize phase processing, and record error information raised during listening or dispatch.

Tables Accessed

WF_EVENT reads and writes the principal Workflow Business Event System tables, resolved through APPS synonyms. WF_AGENTS, WF_AGENT_T, WF_AGENT_GROUPS, WF_SYSTEMS, and WF_EVENT_SUBSCRIPTIONS supply the agents, systems, and subscription definitions that determine how an event is routed. WF_EVENT_T and WF_PARAMETER_LIST_T / WF_PARAMETER_T carry the event and its parameters. FND_USER, FND_RESPONSIBILITY, FND_APPLICATION, FND_CONCURRENT_PROGRAMS, and FND_CONCURRENT_REQUESTS are referenced for security and for raising concurrent requests, which is central to the LISTEN_CONCURRENT mechanism. DBMS_AQ and ALL_QUEUES are used for AQ enqueue/dequeue operations.

Usage Notes

WF_EVENT is normally invoked indirectly: the Workflow Business Event System and subscription-processing machinery call it internally, which explains the very large number of dependent packages. Custom code most often calls WF_EVENT.RAISE to publish an event, but the LISTEN and LISTEN_CONCURRENT procedures — the source of the "listen_concurrent" search — are commonly executed from concurrent programs or scheduled listeners that continuously dequeue and process events on a background database session. Developers should rely only on the documented procedures listed above; the private package variables are subject to change and must not be referenced by customer code.