Search Results process_alerts

Overview

The APPS.OE_BIS_ALERTS package is a PL/SQL stored package that resides in the APPS schema and is classified under the ETRM repository as an "OTHER" API type. Its naming convention places it firmly within the Order Management (OE) module and, more specifically, within the Business Intelligence System (BIS) alerting subsystem. The package provides the backend PL/SQL logic required to evaluate and process Order Management business alerts — the event-driven notifications that warn order management personnel about conditions requiring attention, such as orders that are past their scheduled ship date, credit-check holds, or pending workflow approvals. In Oracle EBS 12.1.1 and 12.2.2, this package operates as an internal processing engine rather than a public, customer-facing API. Its status is VALID in the ETRM metadata, confirming it is a shipped, functioning component of the application, and its only documented external dependency is on the SYS schema package STANDARD, which is the implicit PL/SQL environment package present in every PL/SQL compilation unit.

Key Procedures and Functions

The ETRM metadata documents four procedures and functions within this package:

• CALCULATE_ACTUAL — Computes actual values used in alert evaluation. This likely derives actual performance or attainment figures (for example, actual versus expected shipment or fulfillment metrics) that the alert engine compares against configured thresholds.
• PROCESS_ALERTS — The central driver that iterates over the applicable alert definitions or alert records and evaluates them, determining which conditions have been met and should trigger notification or workflow action.
• POSTACTUAL — Persists the calculated actual values, presumably writing them to the underlying alert or BIS data structures so that they can be consumed by alert processing, reporting, or notification logic.
• OE_STRT_WF_PROCESS — Starts an Oracle Workflow process. This procedure bridges the alert engine to the Workflow engine, launching the appropriate workflow process (such as a notification or approval path) when an alert condition is satisfied.

As an ETRM "OTHER" classification, these routines are considered internal implementation details. No formal parameter lists are published, and the package is not intended as a supported public API.

Tables Accessed

The ETRM dependency data for OE_BIS_ALERTS records no direct table references beyond the SYS-owned STANDARD package. In practice, a package of this nature would operate against the Order Management Business Intelligence alert infrastructure — alert definition and alert history tables, and Order Management transactional tables accessed through APPS synonyms — to read order conditions, store calculated actuals, and record processed alert outcomes. Because the metadata documents no explicit table dependencies, direct table access should be confirmed by inspecting the package body rather than assumed.

Usage Notes

OE_BIS_ALERTS is an internal engine invoked by the Order Management alerting and Business Intelligence framework rather than by end users directly. Typical invocation points include concurrent programs or scheduled jobs that evaluate alerts on a periodic basis, and workflow-driven processes that call OE_STRT_WF_PROCESS to notify users of triggered conditions. The ETRM metadata confirms the package is referenced by zero other PL/SQL packages, indicating that it is a terminal consumer in the dependency graph rather than a shared utility. It is also self-referenced, consistent with internal, recursive PL/SQL calls within the package body. Customizations that call this package directly are not supported and risk breaking on upgrade, since "OTHER"-classified objects may change between releases without notice. Developers who need alert functionality should use documented, supported Order Management APIs or the standard alert configuration facilities instead of calling OE_BIS_ALERTS programmatically.