Search Results get_period_start_date

Overview

The PL/SQL package body APPS.HRI_OLTP_DISC_TIME is a time-dimension utility within the Oracle E-Business Suite Human Resources Intelligence (HRMSI/HRI) schema. Its business purpose is to determine the calendar boundaries of discrete reporting periods in which any supplied date falls. Specifically, it resolves the start and end dates for period types such as YEAR, SEMIYEAR, QUARTERYEAR, BIMONTH, and MONTH.

This functionality is fundamental to Oracle Daily Business Intelligence and HRMSI reporting, where analytical queries must aggregate transactional facts into consistent time buckets. Rather than embedding date arithmetic in individual reports, the HRI layer centralizes period logic in this package. The package is classified as OTHER (not a formal public API), and the header comment (hriodtim.pkb 115.1) indicates a stable, long-standing component shipped with the EBS 11i and 12.x code lines, including 12.1.1 and 12.2.2.

Notably, HRI_OLTP_DISC_TIME acts purely as a thin wrapper. It delegates all substantive computation to the underlying package HRI_BPL_TIME, which contains the core period-derivation logic. This layered design separates the discovery/OLTP-facing entry point from the base-period-logic implementation.

Key Procedures and Functions

• GET_PERIOD_START_DATE — For a given input date and period type, returns the start date of the period in which that date lies. It is a wrapper for GET_PERIOD_START_DATE in HRI_BPL_TIME. The function declares no preconditions. On success it returns the computed period start date; on failure (any exception) it returns the original input start date unchanged, ensuring a safe, non-null result for downstream processing.
• GET_PERIOD_END_DATE — For a given input date and period type, returns the end date of the period in which that date lies. It is a wrapper for GET_PERIOD_END_DATE in HRI_BPL_TIME. It follows the identical defensive pattern: on success it returns the period end date, and on failure it returns the input end date.

Both functions accept a date and a VARCHAR2 period code, and both return a DATE. The exception handler (WHEN OTHERS) reflects a deliberate design choice: period resolution must never fail hard within a reporting context, so the input date is returned by default.

Tables Accessed

Per the documented ETRM metadata, this package references no tables directly through APPS synonyms. All data access, if any, is encapsulated within the delegated call to HRI_BPL_TIME. The wrapper itself performs only in-memory date arithmetic and function invocation, so no direct SQL against HR or time-dimension tables is attributed to it. This absence of a table footprint is consistent with its role as a pure computational utility rather than a data-access layer.

Usage Notes

HRI_OLTP_DISC_TIME is typically invoked from HRMSI and Daily Business Intelligence reporting logic, and may also be called from custom PL/SQL that needs consistent EBS period boundaries. Because it is classified as a non-public utility, it should be treated as an internal implementation detail. Developers in 12.1.1 or 12.2.2 who require period boundary calculations are generally advised to call the same underlying HRI_BPL_TIME function directly, or to verify that HRI_OLTP_DISC_TIME remains present and unchanged after patching. No other packages reference it, so its consumers are outside the documented dependency graph, most likely reporting engines and ad hoc code.