Search Results get_actual_value

Overview

APPS.BIS_PMV_ACTUAL_PUB is a public PL/SQL package belonging to the Oracle E-Business Suite Business Intelligence System (BIS) product family, which underpins the Performance Management Framework (PMF) and its successor, the Performance Management Viewer (PMV). In Oracle EBS 12.1.1 and 12.2.2, this package serves as the exposed application programming interface for retrieving actual performance values associated with a configured region, function, and set of attributes. It is the public-facing counterpart to the private worker package BIS_PMV_ACTUAL_PVT, which performs the heavy computation. The package is declared with AUTHID CURRENT_USER, meaning that name resolution and privilege checking for unqualified references execute under the privileges of the invoking user rather than the definer. The source header indicates a stable, low-version lineage (115.12, dated November 2002), reflecting that the API has remained essentially unchanged across the 12.1.1 and 12.2.2 releases and is therefore safe for long-lived custom integrations.

Key Procedures and Functions

The package exposes three documented overloads of a single procedure, GET_ACTUAL_VALUE. All three share the same conceptual purpose: accepting a region code, optional function and user context, responsibility context, a time parameter record, a table of parameters, and one or more actual and comparison attribute codes, and returning the resolved actual values along with standard concurrent-style messaging outputs.

• GET_ACTUAL_VALUE (first overload) — Returns a pair of scalar output values (x_actual_value and x_compareto_value) as VARCHAR2, together with x_return_status, x_msg_count, and x_msg_data. This form is suited to callers that need a single attribute value and its optional comparison value.
• GET_ACTUAL_VALUE (second overload) — Accepts an additional p_page_id and a p_ranking_level parameter, and returns x_actual_value as a PL/SQL table of type BIS_PMV_ACTUAL_PVT.ACTUAL_VALUE_TBL_TYPE. This form supports ranked, multi-row result sets typically required by dashboard or scorecard-style displays.
• GET_ACTUAL_VALUE (third overload) — Accepts p_page_id and a collection of measure attribute codes (p_measure_attribute_codes of type BIS_PMV_ACTUAL_PVT.MEASURE_ATTR_CODES_TYPE), enabling a single call to resolve multiple measures at once. This overload is the most efficient for batch evaluation of a full region layout.

All overloads accept p_region_code, p_function_name, p_user_id, p_responsibility_id, p_time_parameter, p_parameters, p_param_ids, p_actual_attribute_code, and p_compareto_attribute_code, with the second and third additionally accepting p_page_id.

Tables Accessed

The ETRM metadata for this package does not enumerate specific base tables; the package is documented as referencing tables indirectly through APPS synonyms and relies on the BIS PMV metadata model (region, function, attribute, and parameter definitions) plus the underlying transactional or summary tables mapped to the requested measures. Because the package is marked as referenced by two other packages, it is intended primarily as an internal-but-public building block of the PMV runtime rather than a direct SQL access layer.

Usage Notes

GET_ACTUAL_VALUE is typically invoked from Oracle Forms-based PMV configuration screens, from concurrent programs that pre-compute scorecard values, and from custom PL/SQL that must reproduce PMV behavior outside the standard UI. Callers should always inspect x_return_status before consuming x_actual_value, and should iterate x_msg_count / x_msg_data to surface errors. Because the overloads differ in output type and parameter set, existing custom code compiled against 12.1.1 will continue to function in 12.2.2 without change. Custom code should call the _PUB package rather than _PVT, since the private package signature is not a supported integration point.