Search Results bis_alert_service_pvt




Overview
Explore in AI Chat

Overview

The concurrent program BIS_ALERT_SERVICE_PVT is a technical, privately scoped program registered under the BIS – Applications BIS product family in Oracle E-Business Suite. Its user-facing name is BIS Alert Service Private, and the program is described in the ETRM metadata simply as “BIS Alert Service”. The suffix _PVT indicates that the program is intended for internal, private use by the Oracle Alert infrastructure rather than for direct submission by end users. It is not a functional business program that performs transactional or reporting work in the sense of an FI, INV, or PO concurrent request; instead it supports the Alert engine’s ability to evaluate alert conditions and dispatch alert notifications.

In the documented ETRM metadata for 12.2.2, the program is explicitly marked Enabled: No, meaning that it is registered but not intended to be submitted from the standard Submit Requests window by ordinary users. It exists to be invoked programmatically by the Alert subsystem when an alert check requires the alert service routine to run.

Execution Details

The documented execution characteristics of BIS_ALERT_SERVICE_PVT are as follows:

  • Product: BIS – Applications BIS
  • Execution Method: PL/SQL Stored Procedure
  • Argument Method: Standard
  • Executable: BISVALRS
  • Executable user name: BISVALRS
  • Execution Filename: BIS_ALERT_SERVICE_PVT.Service_Alert_Request_Pvt
  • Enabled: No

The executable short name BISVALRS is the registered executable that the concurrent manager invokes. The execution file specification BIS_ALERT_SERVICE_PVT.Service_Alert_Request_Pvt identifies the PL/SQL package and procedure that are actually executed when the request runs. The “Standard” argument method means that the program accepts its arguments in the standard concurrent program token list rather than through a specialized argument method. The behavior is identical on 12.1.1 and 12.2.2 ETRM documentation since the concurrent program definition is carried forward across releases without functional change.

How to Run

Because the program is registered as Enabled: No, it is not normally exposed to end users through the Submit Requests (SRS) form. Users do not submit BIS_ALERT_SERVICE_PVT directly; instead it is typically launched indirectly by the Oracle Alert processing framework when an alert’s periodic check or event-based check is evaluated. In practice, the Alert Manager or the alert processing background logic invokes the private alert service procedure to validate alert conditions and generate alert messages.

Where the program is invoked programmatically, the standard argument list associated with the BISVALRS executable would be passed by the calling alert process. Administrators who need to verify the program can do so through the Concurrent Programs and Executables definition forms in the Application Developer or System Administrator responsibility, where the BISVALRS executable and the BIS_ALERT_SERVICE_PVT program row can be reviewed. Attempting to schedule it manually from SRS is neither supported nor typical, since its disabled status reflects its private nature.

Related Objects

BIS_ALERT_SERVICE_PVT belongs to the Alert infrastructure in the BIS product. Closely related objects include the Oracle Alert tables and the alert processing packages that invoke it, such as the alert check and alert action packages used by the Alert Manager. The program is associated with the BISVALRS executable definition in the concurrent program architecture. Related diagnostics include the Concurrent Manager log and output files for requests generated by the alert framework, as well as alert-specific setup forms (Define Alert, Periodic Alert Scheduler) in the Alert Manager responsibility. Troubleshooting typically focuses on the alert definition, the alert processing schedule, and the concurrent manager log rather than on submitting this private program directly.