Search Results alert_check

Overview

APPS.CST_BIS_ALERT is a PL/SQL package belonging to the Oracle E-Business Suite Cost Management (CST) product family, specifically the Business Intelligence System (BIS) component that underpins cost-related alerting and reporting. The BIS schema in EBS provides the analytical foundation used by Oracle Business Intelligence and Discoverer-based cost reporting, and packages in this family are generally concerned with evaluating cost measures against defined thresholds or business rules. CST_BIS_ALERT is declared with AUTHID CURRENT_USER, meaning the package executes with the privileges of the invoking user rather than the definer, which is typical for BIS utility packages that must respect the caller's security context when querying cost data.

Functionally, the package provides a mechanism to evaluate whether a particular cost or business measure has crossed a condition warranting notification. It is classified in ETRM as OTHER rather than a public API, indicating it is internal infrastructure rather than a supported integration interface.

Key Procedures and Functions

• ALERT_CHECK — The sole documented procedure in the package. It accepts a measure short name parameter (p_measure_short_name) identifying the measure to be evaluated, and performs the alert evaluation logic against that measure. The short name corresponds to one of the cost-related measure definitions held in the BIS measure metadata repository. This is the entry point a caller uses to trigger a check for a single named measure; no other documented procedures or functions are exposed.

No overloads, return values, or additional helper routines are documented for this package in the ETRM record.

Tables Accessed

The ETRM metadata lists no directly referenced tables for CST_BIS_ALERT via APPS synonyms, and it is not referenced by any other documented package. This absence is characteristic of BIS packages that rely on dynamically constructed SQL or invoke other BIS/APPS objects to resolve measure definitions, thresholds, and current values at runtime rather than embedding static table references. Consequently the package's data footprint is indirect: it operates in concert with the BIS measure and alert definition metadata maintained elsewhere in the APPS schema.

Usage Notes

• The package is not exposed through any documented concurrent program or form according to the ETRM record, and it is not referenced by other packages in the documented dependency graph, reinforcing its classification as internal infrastructure.
• Typical invocation is expected from Oracle Business Intelligence infrastructure or from custom cost-monitoring code that needs to trigger alert evaluation for a named measure, passing the measure short name at runtime.
• Because the package is declared AUTHID CURRENT_USER, callers must possess sufficient privileges on the underlying cost data and BIS metadata objects; granting execute on the package alone is not guaranteed to be sufficient.
• Given its classification as OTHER, direct custom invocation is not a supported extension point. Customizations should prefer documented public APIs where available and treat CST_BIS_ALERT as an internal implementation detail subject to change between 12.1.1 and 12.2.2.

The header comment indicates the package dates to an early release lineage, suggesting it is a stable, largely unchanged component carried forward into the 12.1.1 and 12.2.2 code lines.