Search Results service_alert_request

Overview

The APPS.BIS_ALERT_SERVICE_PUB package body is the public API for Alert Services within the Oracle E-Business Suite Business Intelligence System (BIS) schema. It is the server-side implementation that supports the alerting and exception-reporting features of Oracle Daily Business Intelligence and related EBS intelligence dashboards, allowing users and applications to programmatically request that an alert be evaluated and delivered for a specific performance measure.

The package body header records a creation date of April 2000 and a public package name constant of BIS_ALERT_SERVICE_PUB. Subsequent revisions addressed distinct functional concerns: bug fix 2758428 (January 2003) introduced separate local variable declarations for IN and OUT parameters to avoid parameter aliasing, and enhancement 3148615 (December 2003) added Change/Target based alerting, extending the package beyond the original absolute-threshold mode. The package complies to version 115.16 of the source file BISPALRB.pls. In ETRM it is classified as a public (PUB) API owned by the APPS schema, and it is not referenced by any other documented packages, indicating it is intended as an entry point invoked directly by external callers rather than as an internal utility.

Key Procedures and Functions

• SERVICE_ALERT_REQUEST — The single documented procedure in the package and its principal public interface. It accepts an alert request that identifies the measure to be evaluated together with its dimensional context, then evaluates and processes that alert request. Parameter lists are not restated here, but the declared signature exposes a rich selection of optional arguments covering the measure identifier and short name, the plan, the organization level, organization, time level and time level value, and four numbered dimension levels (p_dim1 through p_dim4), each supplied as a level identifier, level short name, and level value identifier. Standard concurrent-program style ERRBUF and RETCODE parameters are returned for status. All dimensional parameters except the measure default to NULL, so callers may scope an alert narrowly (a single measure) or broadly (measure within plan, organization, time, and dimension contexts).

Tables Accessed

The ETRM metadata for this object does not enumerate a specific set of referenced tables through APPS synonyms. Functionally, an alert-service routine of this type operates against the BIS summary and alerting infrastructure — resolving the supplied measure, level, and value identifiers against the BIS measure and dimension metadata, and then invoking the alert evaluation logic that ultimately delivers the resulting alert. Because the documented metadata does not name the underlying tables, implementers should treat the physical table dependencies as an implementation detail of the BIS schema rather than a stable, documented contract.

Usage Notes

BIS_ALERT_SERVICE_PUB.SERVICE_ALERT_REQUEST is typically invoked from concurrent programs, from Oracle Forms-based intelligence setup and administration screens, or from custom PL/SQL that needs to trigger an alert request outside of the normal scheduled cycle. Callers should populate ERRBUF and RETCODE to receive outcome information and should be prepared to pass either identifiers or short names for the measure and dimensions, since the interface accepts both forms. The default NULL values on the plan, organization, time, and dimension parameters allow a minimally qualified request to be submitted when only a measure is known.

Given the object's age (originating in 2000, last revised for 12.x-era EBS usage) and its classification as a public API, it remains callable in Oracle EBS 12.1.1 and 12.2.2, but custom code should invoke it through the APPS synonym layer and avoid direct dependencies on its internal logic, which is not part of the documented public contract.