Search Results bis_pmv_time_levels_pvt




Overview

BIS_PMV_TIME_LEVELS_PVT is an internal, private PL/SQL package body owned by the APPS schema within Oracle E-Business Suite. The PVT suffix indicates that it belongs to the private layer of the Oracle Application Framework API stack: it implements the low-level logic that is exposed to callers only indirectly through a corresponding public wrapper, BIS_PMV_TIME_LEVELS_PUB. Its functional domain is the Oracle Balanced Scorecard / Performance Management Viewer (PMV) time-intelligence engine, which resolves time-level hierarchies, working calendars, and "as-of" dates used to render period-over-period and nested-pattern comparisons across dashboards, reports, and KPIs.

The package encapsulates the date arithmetic that the PMV framework requires but that would be unsafe to embed directly in every reporting component: translating a requested time level into a concrete date range, walking backwards to the previous comparable period, and determining the applicable reporting start date against the BIS common calendar. In Oracle EBS 12.1.1 and 12.2.2 the object remains VALID and is distributed wherever the BIS (Business Intelligence System) product family is installed.

Key Procedures and Functions

The ETRM metadata documents nine callable units within this package body. No parameter lists are published and none are inferred here.

  • GET_TIME_LEVEL_INFO — Returns metadata describing a requested time level, providing the labelling and boundaries the PMV engine uses to group data by period, quarter, or year.
  • GET_PREVIOUS_TIME_LEVEL_VALUE — Resolves the value of the immediately preceding time level, supporting prior-period and period-over-period comparison columns.
  • GET_PREVIOUS_ASOF_DATE — Calculates the prior as-of date required when a dashboard is asked to compare a current snapshot against an earlier one.
  • GET_BIS_COMMON_START_DATE — Establishes the baseline start date of the BIS common calendar, the anchor from which the remaining date computations derive.
  • GET_REPORT_START_DATE — Determines the effective start date for a given report or scorecard rendering, honouring the reporting calendar rather than the raw system date.
  • GET_TIME_PARAMETER_RECORD — Retrieves the time parameter record that governs the current session's time-level behaviour.
  • GET_COMPUTED_DATES — Produces the derived start and end dates for the requested time level; the central date-arithmetic routine of the package.
  • GET_NESTED_PATTERN — Builds the nested time pattern used when multiple time levels are displayed together, such as year within quarter within month.
  • GET_POPLIST_DATES — Returns the date list that populates a time-level poplist or selection control in the user interface.

Tables Accessed

The dependency section records no direct table references; all persistent data is reached indirectly. The package depends on BIS_PMV_PARAMETERS_PVT, its sibling parameter-resolution package, for the time parameters that drive date calculation. It also depends on the standard Oracle Application Framework API and messaging infrastructure, FND_API and FND_MSG_PUB, for consistent error handling and message retrieval, and on SYS.STANDARD for the PL/SQL language foundation. Views and tables exposed through APPS synonyms supply the underlying time-level and calendar data at runtime.

Usage Notes

BIS_PMV_TIME_LEVELS_PVT is not referenced by any other database object directly, and it is not intended to be called by customer code. It is invoked by the PMV public API layer and, through it, by the Balanced Scorecard dashboards, performance management reports, and concurrent programs that schedule scorecard refreshes. Four other packages depend on it. Its private status means a custom extension should target BIS_PMV_TIME_LEVELS_PUB instead; direct calls into the _PVT layer are unsupported and may be broken by patching. Because the package is validated and depends only on standard EBS foundation objects, behaviour is consistent across 12.1.1 and 12.2.2, with the Online Patching editioning model of 12.2.2 requiring no change to how the package is invoked.