Results for “start_cleanup_process”

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

Overview

WF_BES_CLEANUP_INIT is an Oracle Workflow Business Event System (BES) utility package owned by the APPS schema. Its purpose is to initialize the Oracle E-Business Suite session context and to launch the recurring cleanup of the Business Event System control queue. The package header was introduced in release 11i (the source header records version 115.0, dated 2002/08/21) and it continues to be shipped in EBS 12.1.1 and 12.2.2 as part of the Workflow technology stack. The name of the package reflects its two responsibilities: "BES" denotes the Business Event System, "CLEANUP" denotes removal of processed event queue data, and "INIT" denotes session initialization and process start-up.

The package is classified as OTHER in the ETRM metadata; it is an internal utility rather than a public, supported API. It is not referenced by any other documented package, which confirms that it is designed to be invoked directly, typically from the command line or from a scheduled concurrent request, rather than being called from application code.

Key Procedures and Functions

• APPS_INITIALIZE — Establishes a valid Oracle EBS runtime context before any other work is performed. The procedure resolves the user identifier for the SYSADMIN user from FND_USER, then resolves the application identifier and responsibility identifier for the SYSTEM_ADMINISTRATOR responsibility owned by the SYSADMIN application. It then calls FND_GLOBAL.APPS_INITIALIZE, passing the resolved user, responsibility, and application identifiers. This sequence is the reason the term "apps_initialize" surfaces in searches against this object: the wrapper exists solely so that callers do not have to manually determine the SYSADMIN context. Because APPS_INITIALIZE relies on a SELECT INTO, the procedure raises NO_DATA_FOUND if the SYSADMIN user or the SYSTEM_ADMINISTRATOR responsibility is missing or renamed.
• START_CLEANUP_PROCESS — Determines whether the Business Event System control queue cleanup program is already scheduled and, if not, submits it. The procedure notes the appending of the cleanup program on the FND application, with the program short name FNDWFBES_CONTROL_QUEUE_CLEANUP, and configures a repeating schedule of twelve hours with a repeat type of START. It queries the concurrent request status for that program using FND_CONCURRENT.GET_REQUEST_STATUS before deciding whether to submit a new request, thereby preventing duplicate concurrent cleanup jobs.

Tables Accessed

• FND_USER — Read to obtain the USER_ID for the user name SYSADMIN. This value becomes the user identifier passed to FND_GLOBAL.APPS_INITIALIZE.
• FND_APPLICATION — Read to translate the application short name SYSADMIN into an APPLICATION_ID, which is required both for the responsibility lookup and for the initialization call. The same table (through its FND synonym) is used conceptually by the cleanup submission logic, since the cleanup program resides on the FND application.
• FND_RESPONSIBILITY — Read, joined to FND_APPLICATION, to obtain the RESPONSIBILITY_ID whose key is SYSTEM_ADMINISTRATOR under the SYSADMIN application. This responsibility completes the three-part context required by APPS_INITIALIZE.

The package performs no inserts, updates, or deletes against these tables; all access is read-only lookup.

Usage Notes

WF_BES_CLEANUP_INIT is intended for administrative and housekeeping use. A typical invocation sequence is to call APPS_INITIALIZE first, thereby establishing the SYSADMIN security context, and then call START_CLEANUP_PROCESS so that the twelve-hour recurring cleanup of the WF_BES control queue is registered. Because the package is not exposed through an Oracle Forms screen and is not documented as an API, it is normally invoked from a SQL*Plus or SQL Developer session connected as APPS, or from a small custom PL/SQL driver executed by a concurrent program or operating-system scheduler.

Several operational cautions apply. The initialization procedure depends on the SYSADMIN user and the SYSTEM_ADMINISTRATOR responsibility retaining their standard names; sites that rename or disable SYSADMIN will encounter a NO_DATA_FOUND error. The start-up procedure assumes the cleanup program FNDWFBES_CONTROL_QUEUE_CLEANUP exists on the FND application and will fail if that concurrent program has been removed. Finally, because the package is internal and unsupported for customization, extensions should be implemented in separate custom packages rather than by modifying WF_BES_CLEANUP_INIT directly.