Search Results bis_pmf_alert_reg_pvt




Overview
Explore in AI Chat

Overview

BIS_PMF_ALERT_REG_PVT is a private PL/SQL package in the APPS schema that underpins the Oracle E-Business Suite Business Intelligence System (BIS) alerting framework, commonly associated with the Daily Business Intelligence (DBI) and Performance Management products. Its primary business function is to manage the registration of alerts and their associated parameter sets, providing the persistence, validation, and rendering logic that higher-level public APIs and services rely upon. The package is classified as a PVT object, meaning it is intended for internal consumption by other BIS packages rather than direct invocation by end users or external integrations.

The package builds on several peer components, including BIS_PMF_ALERT_REG_PUB, BIS_MEASURE_PUB, BIS_DIM_LEVEL_VALUE_PUB, and BIS_UTILITIES_PUB, and leverages the standard FND_API error-handling and messaging conventions. Its role is essentially to guarantee that alert definitions, notification targets, scheduling parameters, and user-role assignments are created, validated, retrieved, and deleted consistently within the alerting data model.

Key Procedures and Functions

Eighteen documented procedures and functions make up the package interface. The most significant include:

  • CREATE_PARAMETER_SET, DELETE_PARAMETER_SET, RETRIEVE_PARAMETER_SET — manage the lifecycle of alert parameter sets, allowing alert definitions to be created, fetched for display or processing, and removed when no longer required.
  • PARAMETER_SET_EXIST and VALIDATE_PARAMETER_SET — provide existence checks and business-rule validation before a parameter set is persisted or consumed.
  • RETRIEVE_NOTIFIERS_CODE — returns the set of notification recipients or notifier codes associated with an alert registration.
  • MANAGE_ALERT_REGISTRATIONS — the core orchestration routine that creates, updates, or removes alert registration records.
  • FORM_PARAM_SET_REC — supports the OAF/Forms user interface by assembling a parameter set record suitable for rendering.
  • BUILDALERTREGISTRATIONURL and BUILDSCHEDULEREPORTURL — construct the URLs used to link an alert notification directly to its registration detail page or its scheduled report.
  • ADD_USERS_TO_ROLE — assigns users to the ad hoc workflow role used for alert delivery.

No parameter or signature detail is reproduced here; the descriptions reflect documented purpose only.

Tables Accessed

The package works against a small, focused set of tables via APPS synonyms:

  • BIS_ALERT_REGISTRATION_S — the primary alert registration table, holding active alert definitions and their scheduling context.
  • BIS_PMF_ALERT_PARAMETERS — stores the parameter values that drive each alert registration.
  • WF_ADHOC_ROLE_S — the Workflow ad hoc role table used to route alert notifications to designated users.
  • DUAL — used for single-row lookups and utility evaluations.
  • PLITBLM — the PL/SQL integer table (index-by table) type used for passing collections of identifiers such as alert or user IDs.

Usage Notes

BIS_PMF_ALERT_REG_PVT is referenced by five other packages, notably BIS_ALERT_SERVICE_PVT, BIS_CONCURRENT_MANAGER_PVT, BIS_CORRECTIVE_ACTION_PVT, BIS_PMF_ALERT_REG_PUB, and BIS_PMF_REG_SERVICE_PVT. These callers expose the functionality through public APIs, concurrent programs, and the alerting user interface. Because it is a PVT package, customizations should not call it directly; instead, developers should use BIS_PMF_ALERT_REG_PUB or the alert service APIs. The package behaves identically in EBS 12.1.1 and 12.2.2, as the underlying alerting data model and APIs were not materially changed between those releases.