Search Results get_dbi_date




Overview
Explore in AI Chat

Overview

APPS.HRI_OLTP_PTL_PARAM is a lightweight PL/SQL specification belonging to the Oracle HR Intelligence (HRI) family of packages. It is declared with AUTHID CURRENT_USER, meaning that its executable statements and SQL run with the privileges of the invoking schema rather than the definer, a common convention for HRMS reporting utilities. The package occupies a small but specific role in the Oracle E-Business Suite: it supplies default parameter values and parameter lists that drive the HRI Online Transaction Processing (OLTP) portal and its Business Intelligence (DBI) dashboards. In effect, it acts as a central parameter-provider for HR self-service analytics, letting portal regions present consistent filters for the viewing manager, reporting currency, and reporting date without requiring every calling component to hard-code those values. The only documented table reference is PER_ALL_PEOPLE_F, consistent with a package whose primary job is to resolve personnel and session context.

Key Procedures and Functions

Five documented functions make up the public interface of the package. None are listed with explicit parameter lists in the ETRM metadata; the behavior described below follows the documented signatures where available.

  • GET_PARAMS — Returns a VARCHAR2 parameter string for a given region identifier. It produces the general parameter block used by the portal when rendering an OLTP region.
  • GET_DBI_PARAMS — Returns a VARCHAR2 parameter block specifically tailored for DBI (dashboard) regions, given a region identifier. It is the DBI counterpart to GET_PARAMS.
  • GET_DBI_MGR_ID — Returns the default manager identifier as a VARCHAR2. This is the value the user searched for. It resolves the "current viewing manager" that DBI dashboard queries filter against, so that a manager sees only their own reporting population by default.
  • GET_DBI_CURR — Returns the default currency as a VARCHAR2, used to standardise monetary amounts displayed across DBI regions.
  • GET_DBI_DATE — Returns the default date as a VARCHAR2, providing the effective date or "as of" reference against which date-effective HR records are evaluated.

The three GET_DBI_* functions are explicitly annotated in the source header as returning default values only, indicating they are convenience accessors rather than full parameter builders.

Tables Accessed

The ETRM metadata documents a single table reference: PER_ALL_PEOPLE_F, accessed through an APPS synonym. This is the core date-effective People table in Oracle HRMS. GET_DBI_MGR_ID in particular depends on it, because resolving the manager identity for a self-service session requires looking up the person record associated with the current user (typically via PERSON_ID or the login-to-person mapping). The date-effective nature of PER_ALL_PEOPLE_F also explains why a companion GET_DBI_DATE function exists: the effective date determines which row version of the person record is valid. No other tables are documented, so the package is intentionally narrow in its data footprint.

Usage Notes

This package is an internal HRI utility rather than a public API. It is most commonly invoked from the HR Intelligence portal framework and DBI dashboard regions, where the portal infrastructure calls GET_PARAMS or GET_DBI_PARAMS to assemble the parameter string passed to the underlying OLTP query. The individual GET_DBI_* accessors are called when a region needs a single default value — the viewing manager, currency, or date — rather than a complete parameter set.

The ETRM metadata records that the package is referenced by zero other packages, confirming that it sits at the leaf of the dependency tree and is not a shared library consumed by broader HRMS code. Customisations should therefore avoid depending on it directly. Because it is AUTHID CURRENT_USER, any custom caller must have appropriate grants on PER_ALL_PEOPLE_F and the underlying HRMS objects. The header revision (hriopprm.pkh 115.4, dated 2003) indicates the interface has been stable across the 11i and R12 releases, and it remains valid in EBS 12.1.1 and 12.2.2. When troubleshooting missing dashboard data, GET_DBI_MGR_ID is a primary checkpoint: an incorrect or null manager value will suppress rows in manager-filtered DBI regions.