Search Results bes_database_id

Overview

APPS.FND_BES_PROC is a lightweight PL/SQL package body belonging to the Oracle E-Business Suite foundation layer. Its name reflects its role as the Business Event System (BES) processing helper, and its purpose is to enrich outbound business event payloads with foundational context before those events are handed to the standard Workflow event subscription evaluation logic. In the Oracle EBS 12.1.1 and 12.2.2 architectures, the Business Event System is the propagation mechanism through which applications raise events (for example, order booking or user creation) and workflow subscriptions respond to them. FND_BES_PROC serves as a thin wrapper that standardizes two critical pieces of routing context — the database identifier and the security group identifier — so that downstream subscribers can filter or route events consistently across multi-organization and multi-instance deployments.

The package contains no state and declares only two package-level constants, BES_DATABASE_ID and BES_SECURITY_GROUP_ID, which are used as parameter names on the event payload. The header comment indicates the file was last revised in 2002 and marked "noship", meaning it is delivered but not treated as a customer-modifiable shipped file.

Key Procedures and Functions

The ETRM metadata documents exactly one procedure: PROCESS_EVENT. This function accepts a subscription GUID and a workflow event object, and returns a VARCHAR2 result. It performs two conditional enrichments before delegating to the standard rule engine:

• If the event payload does not already carry a parameter identified by BES_DATABASE_ID, the function obtains the database identifier via FND_WEB_CONFIG.DATABASE_ID and adds it to the event parameter list.
• If the event payload does not already carry a parameter identified by BES_SECURITY_GROUP_ID, the function reads the current security group from FND_GLOBAL.SECURITY_GROUP_ID and appends it to the event.
• After enrichment, control is passed to WF_RULE.DEFAULT_RULE, which evaluates the subscription and returns the standard workflow rule result code.

The guard conditions ensure idempotency: an event that already contains these parameters is not modified, preventing duplicate entries when the function is invoked more than once along an event's propagation path.

Tables Accessed

The documented table reference is WF_EVENT_T, which is the Workflow event type used throughout the Business Event System. FND_BES_PROC does not perform direct SQL against it; instead, it manipulates an instance of the WF_EVENT_T object type through its getValueForParameter and addParameterToList methods. Indirectly, the function depends on WF_RULE for subscription evaluation. No application tables are queried or updated, and the package holds no persistent data of its own.

Usage Notes

FND_BES_PROC is normally invoked by the Business Event System framework rather than by end users. It is referenced as a subscription processing function or as a pre-processing step in the event propagation chain, so administrators configuring subscriptions in the Workflow Administrator responsibility may select or encounter this package when defining an event subscription's rule function. Developers writing custom subscriptions in either 12.1.1 or 12.2.2 can call PROCESS_EVENT to obtain the same standardization of database and security group parameters before implementing their own logic, or they may replicate its pattern. Because the referenced metadata shows the package is referenced by no other documented packages, it should be regarded as a leaf utility invoked primarily through configuration or custom code. When troubleshooting missing events, confirming that the BES_DATABASE_ID and BES_SECURITY_GROUP_ID parameters are present on the payload is a useful diagnostic step, as downstream subscriptions may depend on them.