Search Results bis_alert_service

Overview

The concurrent program BIS_ALERT_SERVICE belongs to the BIS – Applications BIS product family within Oracle E-Business Suite, and is presented to end users under the name BIS Alert Service. The program is documented as enabled (Enabled: Yes) in the ETRM repository for release 12.2.2, and the same metadata applies to the 12.1.1 code line. Its purpose is to service alert requests generated by the Oracle Alert and Business Intelligence System infrastructure, providing the runtime engine that evaluates and dispatches alert conditions defined by the application.

Oracle Alert is the exception-detection and notification mechanism embedded in EBS. Alerts can be period-based, event-based, or triggered by database events; regardless of the definition type, the actual evaluation of an alert's SQL statement, comparison of results against thresholds, and assembly of the outgoing notification are executed through the alert service layer. BIS_ALERT_SERVICE is the concurrent program wrapper that invokes this service inside the standard concurrent manager framework, allowing alert processing to be scheduled, monitored, and retried like any other request.

Execution Details

The documented execution attributes for BIS_ALERT_SERVICE are as follows:

• Execution Method: PL/SQL Stored Procedure
• Argument Method: Standard
• Executable: BISPLARS
• Execution Filename: BIS_ALERT_SERVICE_PUB.Service_Alert_Request
• Subroutine Name: (not populated)

The executable short name BISPLARS (user-facing name BISPALRS) is the generic BIS PL/SQL executable registration. Because the execution method is PL/SQL Stored Procedure, the concurrent manager does not spawn an operating-system binary; instead it invokes the packaged procedure BIS_ALERT_SERVICE_PUB.Service_Alert_Request directly against the database schema. The Standard argument method indicates that the program accepts the conventional concurrent program token list, and any parameters defined on the concurrent program definition are passed positionally into the stored procedure.

How to Run

Like all standard concurrent programs, BIS_ALERT_SERVICE is submitted through the Submit Requests (SRS) window using the responsibility that owns the BIS/AOL alert administration function, typically System Administrator or a custom BIS responsibility. Users select BIS Alert Service from the list of values, optionally enter request parameters, choose a printer or leave the output destination as the default, and submit.

In practice, this program is rarely run manually. It is normally driven by the Oracle Alert scheduler, by request-set membership, or by a recurring schedule established in the concurrent manager, so that alert checks execute at the frequency configured on each alert definition. Because the documented argument method is Standard and no specific parameters are enumerated in the ETRM metadata, parameter usage should be confirmed against the concurrent program definition in the target instance; commonly the alert definition or alert identifier is supplied. When diagnosing alert delivery problems, review the concurrent request log and output for the BIS_ALERT_SERVICE request, which records the outcome of the service call.

Related Objects

BIS_ALERT_SERVICE operates in conjunction with the wider Oracle Alert and BIS object set, including:

• BIS_ALERT_SERVICE_PUB — the PL/SQL package that contains Service_Alert_Request, the routine executed by this program.
• BISPLARS / BISPALRS — the shared BIS executable registration used by this and other BIS concurrent programs.
• Oracle Alert definition and action tables — the alert header, input, and action records that the service reads to determine what to evaluate and whom to notify.
• Alert-related concurrent programs — companion processes that check periodic alerts, dispatch e-mail notifications, and perform alert maintenance, which together form the complete alert processing chain.

These objects should be reviewed together when troubleshooting alert behavior, since a failure in the service routine will surface on the BIS_ALERT_SERVICE request itself rather than on the individual alert definition.