Search Results get_dbi_current_period

Overview

BSC_BIS_WRAPPER_PUB is a public PL/SQL package owned by the APPS schema within the Oracle E-Business Suite environment. Its identifier and header comment ($Header: BSCPBISS.pls) situate it within the Balanced Scorecard (BSC) and Business Intelligence System (BIS) product family, which delivers the Oracle EBS Daily Business Intelligence and Balanced Scorecard reporting framework. The package functions as a wrapper layer that exposes KPI-oriented data retrieval and measure-population logic to callers through a stable public interface, shielding them from the underlying BIS schema objects.

The package is declared with AUTHID CURRENT_USER, meaning its procedures execute with the privileges of the invoking user rather than the package owner. This design choice is consistent with EBS public APIs that are invoked from multiple contexts, including Oracle Forms-based dashboard pages and concurrent programs, where the calling session must resolve APPS synonyms under its own security profile.

The package defines several strongly typed collection and record structures that model its data domain: Dim_level_Rec_Type for dimension levels, Page_Parameter_Rec_Type for page-level parameter bindings, Kpi_Info_Rec_Type for KPI definitions and their associated dimension, series, dataset, and measure attributes, and the companion table types indexed by BINARY_INTEGER. A generic t_array_of_varchar2 table type is also supplied for variable-length string collections. These structures underpin the package's KPI computation and rendering operations.

Key Procedures and Functions

Eight public procedures and functions are documented for this package. They fall into three functional groups.

• GET_CURRENT_PERIOD — Returns the current period used by the Balanced Scorecard region rendering engine, resolving period context for the calling scorecard page.
• GET_CURRENT_PERIOD_BY_KPI — Returns the current period scoped to a specific KPI, allowing different scorecards to resolve period independently when KPI-specific time settings apply.
• GET_DBI_CURRENT_PERIOD — Returns the current period as defined for Daily Business Intelligence reporting. This is the procedure most directly associated with the user's search term and is typically invoked when a DBI dashboard or KPI region needs to determine which period's data to display.
• GET_ACTUAL_VALUE — Retrieves the actual (measured) value for a KPI.
• GET_ACTUAL_VALUE_BY_KPI — Retrieves the actual value scoped to a specific KPI code.
• GET_TARGET_VALUE — Retrieves the target value associated with a KPI or scorecard element.
• GET_TARGET_VALUE_BY_KPI — Retrieves the target value scoped to a specific KPI code.
• POPULATE_MEASURE_DATA — Populates measure data for KPIs, handling the insertion or update of computed measure results based on the insert_update_flag carried in the KPI info record.

The BY_KPI variants indicate that KPI context is passed explicitly, whereas the unsuffixed counterparts rely on ambient page or session context.

Tables Accessed

The ETRM metadata excerpt does not enumerate the underlying tables directly. The package header includes no table list, and the documentation confirms only that any tables referenced are resolved through APPS synonyms. Based on the BIS data model, these operations target the BIS KPI definition, measure, dimension, and period tables that store scorecard metadata and computed KPI values. The get_current_period family in particular reads BIS period configuration to establish the reporting window.

Usage Notes

BSC_BIS_WRAPPER_PUB is referenced by one other package in the EBS codebase, confirming it is an internal building block within the BIS layer rather than an end-user entry point. It is invoked from Oracle Forms-based Balanced Scorecard and DBI dashboard pages, from concurrent programs that precompute KPI measure data via POPULATE_MEASURE_DATA, and from custom extensions that need to retrieve KPI actual or target values programmatically. The package is present and compatible in both EBS 12.1.1 and 12.2.2. Custom code should call only the documented public procedures and avoid direct dependency on the record and table type definitions, whose header revision date (2003) indicates a long-stable but historically evolved interface.