Search Results hri_bpl_parameter




Overview
Explore in AI Chat

Overview

HRI_BPL_PARAMETER is a lightweight PL/SQL package in the APPS schema that functions as a centralized parameter provider for the Oracle E-Business Suite HRMS Business Intelligence (BI) and Balanced Scorecard reporting layer. The "HRI_BPL" prefix associates the package with the Human Resources Intelligence (HRI) family of packages that support the HRMS Intelligence and Oracle Balanced Scorecard Publisher components, where "BPL" designates the Business Process Library tier that supplies runtime settings to reporting engines, extraction programs, and dashboard components. In Oracle EBS 12.1.1 and 12.2.2 the package is classified as OTHER, indicating it is a supporting utility rather than a public integration API. Its primary and currently documented responsibility is to expose global configuration values — specifically the global start date used by the Balanced Scorecard / Business Intelligence reporting stack — so that multiple dependent packages can retrieve a consistent value without hard-coding dates or replicating lookup logic. The header comment preserved in the ETRM source extract (hribprm.pkh, version 120.0, dated 2005/11/11) confirms that the specification has remained stable across the 12.1.x and 12.2.x release lines, which is characteristic of a small, low-churn configuration utility.

Key Procedures and Functions

The ETRM metadata documents a single callable program unit:

  • GET_BIS_GLOBAL_START_DATE — A function returning a DATE. It supplies the global start date used by the Business Intelligence System (BIS) reporting layer, most likely bounding the earliest period for which Balanced Scorecard and HRMS Intelligence data is considered valid or available. Consumer code uses the returned DATE as a lower bound when building date ranges for extraction queries, scorecard period calculations, and initialization of reporting parameters, ensuring that every component of the BI stack applies the same starting point. The function takes no arguments, consistent with a global configuration accessor.

No other procedures or functions are documented for this package in the ETRM repository for 12.2.2. The absence of overloads or setter routines indicates that the underlying value is maintained by setup data rather than by programmatic maintenance.

Tables Accessed

The documented metadata records no direct table references through APPS synonyms for this package. Functions of this type commonly derive their return value from HRMS BI configuration tables (for example, the Balanced Scorecard or HRMS Intelligence setup tables that store global measures and parameters) or from a profile option evaluated at runtime. Because no tables are formally documented, implementers should treat the data source as an internal implementation detail and rely solely on the published function interface. Any investigation of the underlying storage should begin with the package body rather than with assumed table names.

Usage Notes

HRI_BPL_PARAMETER is an internal dependency rather than an entry point. ETRM records that it is referenced by five other packages, all located in the APPS schema, which invoke GET_BIS_GLOBAL_START_DATE during their own initialization or query-construction logic. This makes the package a shared leaf dependency in the HRMS BI call graph: changes to its behavior propagate to every referencing package.

  • Invocation context — Typically called from PL/SQL within other HRI/BIS packages, from Balanced Scorecard and HRMS Intelligence concurrent programs that build reporting extracts, and from OAF or Forms-based dashboard regions that compute date-bounded metrics.
  • Custom code — Customizations that need the same global start date should call APPS.HRI_BPL_PARAMETER.GET_BIS_GLOBAL_START_DATE rather than reading configuration tables directly, preserving upward compatibility across 12.1.1 and 12.2.2.
  • Grants and synonyms — As with other APPS packages, the executing schema requires EXECUTE privilege and a synonym or fully qualified reference; the return value is deterministic for a given configuration state and can safely be cached within a single concurrent request or transaction.
  • Diagnostics — Because five dependent packages rely on this function, an unexpected or NULL return value often surfaces as incorrect reporting date ranges in downstream BI output, making this package an early checkpoint when troubleshooting HRMS Intelligence reporting discrepancies.