Results for “fndwfbes_control_queue_cleanup”
6 results
AI-generated from documented ETRM metadata — verify critical details on the linked pages.
Overview
FNDWFBES_CONTROL_QUEUE_CLEANUP is a standard Oracle E-Business Suite concurrent program that belongs to the FND — Application Object Library product. It is exposed to end users under the name Workflow Control Queue Cleanup and is delivered enabled in the ETRM metadata for both Release 12.1.1 and 12.2.2.
The program forms part of the Oracle Workflow Business Event System (BES) infrastructure. Within that subsystem, inbound business events and event subscriptions are staged in a control queue before being processed by the Workflow Event Agent or its related background engines. Over time, this queue can accumulate obsolete, orphaned, or already-processed subscriber entries — particularly where subscriptions have been deactivated, where agents have been shut down abnormally, or where repeated errors have caused entries to remain resident. The Workflow Control Queue Cleanup program is designed to purge these stale control queue records so that queue processing remains efficient and the underlying WF_* tables do not grow without bound.
Because the program resides in the FND product, it is available to any application installation that has seeded Oracle Workflow, regardless of the functional modules in use. Its scope is administrative and housekeeping-oriented rather than transactional.
Execution Details
The documented execution attributes are as follows:
- Product: FND — Application Object Library
- User Name: Workflow Control Queue Cleanup
- Enabled: Yes
- Execution Method: PL/SQL Stored Procedure
- Argument Method: Standard
- Executable: FNDWFBES_CONTROL_QUEUE_CLEANUP
- Execution Filename: wf_bes_cleanup.cleanup_subscribers
The "Execution Filename" entry identifies the actual PL/SQL package and procedure invoked by the concurrent manager. In Oracle EBS the convention is to list the package specification followed by the procedure name, so wf_bes_cleanup.cleanup_subscribers indicates the cleanup logic implemented in the WF_BES_CLEANUP package. The "Standard" argument method means the program is submitted through the standard SRS parameter form rather than through a custom or token-based interface, and any parameters exposed by the procedure are presented to the submitting user in the usual way.
How to Run
The program is submitted from the standard Submit Requests (SRS) window — Requests > Run — after the user selects the appropriate responsibility. In most implementations submissions are made from a Workflow Administrator or System Administrator responsibility, since the cleanup touches shared Workflow metadata.
Because the metadata records Argument Method as "Standard" and does not enumerate specific parameters in the excerpt, the safest guidance is to submit the program with no arguments unless the local implementation has documented otherwise. The cleanup is typically run as a scheduled or ad hoc maintenance job rather than on a fixed production cycle. It should be executed during periods of low activity, because it operates on the live Workflow control queue; concurrent event processing may otherwise contend with the cleanup. Where the deployment spans multiple instances (for example, a cloned test instance), the program is safe to run independently in each instance against that instance's own queue.
Related Objects
The cleanup logic operates against the Oracle Workflow BES data model. Objects commonly associated with this program include:
- WF_BES_CLEANUP — the PL/SQL package containing the
cleanup_subscribersprocedure executed by this program. - WF_EVENT_SUBSCRIPTIONS and the related subscription definition tables, which describe who receives which business events.
- WF_EVENT_GROUPS and WF_AGENTS, which determine how events are routed and which agents process them.
- WF_BES_CONTROL_QUEUE — the queue of pending controls consumed by the Business Event System, and the primary target of the cleanup.
- Business Event System administrative concurrent programs such as Workflow Agent Listener, Workflow Control Queue Cleanup's companion processes, and the Purge Obsolete Workflow Runtime Data program, which is often scheduled alongside it to manage the wider WF_* tables.
Administrators should verify that no event agent is mid-processing before running the program, and should confirm that the WF_BES_CLEANUP package is compiled valid on the database version in use. Where the cleanup is intended as a recurring maintenance job, define it as a standard request set so that it can be scheduled and reviewed through the Concurrent Manager.
-
Workflow Control Queue Cleanup
-
Workflow Control Queue Cleanup
-
12.1.1 FND Design Data 12.1.1
-
12.2.2 FND Design Data 12.2.2