Search Results calculate_amount

Overview

APPS.GL_BIS_ALERTS_PKG is a private implementation package in the Oracle E-Business Suite Business Intelligence System (BIS) / Enterprise Performance Foundation (EPF) alerting framework. It is designed to drive alert processing for General Ledger revenue indicators — most significantly the FIIGLREVENUE performance measure — by resolving BIS indicator and target-level metadata into the values required by the alert engine. The package body referenced here corresponds to source header glubisab.pls 120.7, indicating an Oracle Applications 11i-era object that has been carried forward unchanged into 12.1.1 and 12.2.2.

Its principal business purpose is to evaluate GL revenue data across the BIS dimension hierarchy (GL COMPANY and GL SECONDARY MEASURE levels, together with their TOTAL variants) and to produce the inputs required for alert notification via Oracle Workflow. Because the object is classified as OTHER in the ETRM repository and exposes no publicly documented APIs, it is intended to be invoked only by the BIS alerting infrastructure and not by customer extensions.

Key Procedures and Functions

The ETRM metadata for this package documents zero public procedures or functions. The source excerpt confirms that the package consists of private variables, a private cursor, and private functions declared in the package body, several of which are named with an internal get_ convention (for example, the routine beginning at the get_pe comment block, whose role is to populate the global period context variables). These private routines are not exposed through the package specification and therefore cannot be called directly from external code.

The user’s search term calculate_amount is relevant here: no procedure or function by that name is documented in this package. Amount calculation for GL BIS alerts is performed by the shared BIS_UTILITIES_PUB and BIS data-cube routines; GL_BIS_ALERTS_PKG supplies the target/resolution context (period name, period set name, period number, period year, and relative period position) that those amount calculations consume. Analysts searching for calculate_amount within GL_BIS_ALERTS_PKG will not find a matching routine and should instead review BIS_UTILITIES_PUB and the indicator definitions in BIS_INDICATORS.

Tables Accessed

The documented cursor c_target_level joins the following BIS objects, all accessed through APPS synonyms:

• BIS_INDICATORS — provides the indicator definition matching the short name FIIGLREVENUE;
• BISBV_TARGET_LEVELS — supplies the target-level identifiers and the associated Workflow item type and process short name used for alert delivery;
• BISBV_DIMENSION_LEVELS (aliased twice, dl1 and dl2) — resolves the dimension level identifiers into short names so that GL COMPANY, TOTAL GL COMPANIES, GL SECONDARY MEASURE, and TOTAL GL SECONDARY MEASURES can be mapped to dimension level codes.

The package does not maintain application data on its own; it reads BIS configuration and returns the resolved context to the calling alert framework.

Usage Notes

GL_BIS_ALERTS_PKG is an internal dependency of the GL BIS alerting programs. It is not documented as referenced by any other package in the ETRM repository, which reflects its status as a top-level entry point whose callers are concurrent programs and Workflow background processes rather than other PL/SQL objects. Typical invocations occur when a BIS alert for the GL revenue performance measure is evaluated — for example, during the GL BIS refreshes or whenever the associated alert subscription is triggered.

Because the object exposes no public API and is classified as OTHER, Oracle does not support direct calls to it from custom code. Customizations requiring amount calculation or alert logic should use BIS_UTILITIES_PUB or the public BIS alert APIs. When migrating from 12.1.1 to 12.2.2, the object requires no functional change; the 120.7 file version remains the delivered baseline in both releases.