Search Results bis_alert_service_pvt_java

Overview

The concurrent program BIS_ALERT_SERVICE_PVT_JAVA is owned by the BIS – Applications BIS product module within Oracle E-Business Suite. It carries the user-facing name BIS Alert Service Private (Java) and the short description BIS Alert Service. In the context of Oracle EBS 12.1.1 and 12.2.2, this program forms part of the Alert Management infrastructure, which supports the definition, scheduling, and delivery of business alerts across the E-Business Suite. The program is documented as Enabled: Yes, indicating that it is active and available for submission in a standard environment.

Alert Management in EBS relies on a set of background service components that evaluate alert conditions and dispatch notifications. The "Private" designation in the user-facing name signals that this program is typically invoked by the application framework rather than entered directly by end users. It provides the Java-based service processing that underpins alert generation and delivery.

Execution Details

The documented execution metadata for this program is as follows:

• Execution Method: Java Concurrent Program
• Argument Method: Standard
• Executable: BIS_ALERT_SERVICE
• Execution Filename: AlertService
• User Name (Executable): BISAlertService
• Subroutine Name: Not specified in the documented metadata
• Enabled: Yes

Because the execution method is Java Concurrent Program, the program runs the compiled Java class identified by the execution filename AlertService under the executable definition BIS_ALERT_SERVICE. The Standard argument method indicates that arguments, when supplied, follow the standard concurrent program parameter convention and are passed to the Java entry point in the order defined on the program's parameter form.

How to Run

As with other concurrent programs, this program is submitted through the Standard Request Submission (SRS) window in EBS (Requests > Run), or programmatically through the Concurrent Manager APIs such as FND_REQUEST.SUBMIT_REQUEST. Because the program is named "Private," it is generally scheduled and launched by Alert Management rather than run manually. Administrators may still submit it directly from SRS when diagnosing alert delivery issues.

The metadata records Standard argument handling but does not enumerate specific parameters. In practice, a Java concurrent program of this type receives framework-supplied context — such as the alert or subscription identifier and processing mode — rather than user-entered values. When submitting manually, users should supply the arguments expected by the alert service definition and verify that the executable and request group assignments permit submission in the current responsibility.

Related Objects

This program operates within the broader Alert Management schema owned by the BIS product. Commonly associated components include:

• The Alert Management setup and administration forms, through which alerts, subscriptions, and input parameters are defined.
• The BIS_ALERT_SERVICE executable definition and its Java execution file AlertService, as documented.
• Alert processing and delivery tables and views in the BIS schema that store alert definitions, subscription records, and dispatch history.
• The Concurrent Manager and Workflow Notification Mailer, which handle scheduling and the actual delivery of alert notifications.

Because the documented metadata is limited to execution and naming facts, the exact interface tables and internal APIs are not enumerated here. Implementers should consult the BIS Alert Management technical reference for the current release (12.1.1 or 12.2.2) to confirm table names and integration points before building custom extensions around this program.