Results for “wf_bes_cleanup_init”

AI-generated from documented ETRM metadata — verify critical details on the linked pages.

Overview

WF_BES_CLEANUP_INIT is a small, purpose-built PL/SQL package in the APPS schema that belongs to the Oracle Workflow Business Event System (BES) infrastructure. Its name reflects its role: it initializes the runtime environment and launches the background maintenance that removes obsolete control queue subscriber records from the Workflow control queue. The seed script header (WFBESCUIS.pls, version 120.1, dated 2005) identifies the package as a shipped Oracle artifact.

In the Oracle EBS 12.1.1 and 12.2.2 architectures, the Business Event System routes events between applications using subscriptions. Each subscription is materialized at runtime as a control queue subscriber entry. Over time, stale, disabled, or completed subscriber rows accumulate, degrading queue performance and inflating WF_* queue tables. WF_BES_CLEANUP_INIT exists to reclaim that residue. It carries an API classification of OTHER in the ETRM 12.2.2 repository and is owned by APPS. It is not an end-user API and is not referenced by any other documented package, so its invocation is deliberate and administrative rather than embedded in application code paths.

Key Procedures and Functions

The package exposes exactly two documented procedures and no public functions.

• APPS_INITIALIZE — Establishes the Oracle EBS session context by initializing the APPS environment for the SYSADMIN user. The source comment states its purpose plainly: "Initializes the apps context to SYSADMIN." Because Workflow cleanup operates across the entire application schema and must resolve responsibility and user records, the session must be elevated to a fully privileged, application-aware context before any cleanup work begins. This procedure is the mandatory first step in the two-step sequence.
• START_CLEANUP_PROCESS — Starts the control queue subscriber cleanup process. Per the source annotation, this is the procedure that actually kicks off the deletion or retirement of obsolete control queue subscribers. It is intentionally separated from initialization so that the environment is guaranteed to be valid before the process is launched.

No parameter lists are documented in the ETRM metadata; both procedures are invoked by name only. The package specification declares no additional overloads and no return values, confirming a simple, fire-and-forget administrative interface.

Tables Accessed

The ETRM 12.2.2 metadata documents three tables referenced through APPS synonyms: FND_APPLICATION, FND_RESPONSIBILITY, and FND_USER. These are the core Oracle Applications foundation tables and their presence indicates the package validates and resolves the security and ownership context of the cleanup.

• FND_APPLICATION — Identifies the registered application owning the subscribers being evaluated, allowing the cleanup to scope its work by application.
• FND_RESPONSIBILITY — Resolves responsibility assignments associated with subscriber records, which are commonly defined in terms of a responsibility.
• FND_USER — Resolves the user identities referenced by subscribers and confirms the SYSADMIN context established by APPS_INITIALIZE.

The metadata does not document direct DML against Workflow queue tables in this package; the actual row removal is performed by the cleanup process the package launches, not by the package itself.

Usage Notes

WF_BES_CLEANUP_INIT is an administrative utility rather than a functional or integration API. It is never called from Oracle Forms or from a standard concurrent program manager request in the shipped product, and no other documented package references it. Typical invocation is therefore manual or scripted: a DBA or Workflow administrator connects to SQL*Plus as APPS, executes WF_BES_CLEANUP_INIT.APPS_INITIALIZE to raise the session to SYSADMIN context, and then executes WF_BES_CLEANUP_INIT.START_CLEANUP_PROCESS to begin purging stale control queue subscribers.

Because the package name and the user's search terms concern "cleanup" and "starting clean," the object is frequently encountered during environment housekeeping rather than during setup of home screen layouts or application configuration. There is no relationship between this package and home screen or device UI setup; any association arises only from keyword overlap. Practitioners should treat WF_BES_CLEANUP_INIT as a narrowly scoped Workflow maintenance entry point, invoke it during scheduled queue hygiene windows, and avoid running it concurrently with active event processing. As with all shipped APPS packages, customization is unsupported; any extension should be implemented in a separate wrapper package that calls these two procedures.