Search Results ibe_bi_pmv_util_pvt




Overview
Explore in AI Chat

Overview

IBE_BI_PMV_UTIL_PVT is a private utility package in the Oracle E-Business Suite iStore (IBE) business intelligence module. The "PMV" naming convention associates it with page metadata views, the personalization and analytics framework used to render structured, aggregated content on iStore storefront pages and dashboards. The package body encapsulates date arithmetic and currency resolution logic required by the business intelligence reporting layer, supplying period boundaries, comparison dates, and record-type identifiers that drive period-over-period metrics such as percentage change calculations.

The package is classified as PVT (private) under the APPS schema, indicating it is not a published public API. Its header revision, $Header: IBEVBIUTILB.pls 120.5 2011/07/28, confirms it was last modified in the 12.1.x code line and remains present in 12.2.2. The body is predominantly a stub implementation: most functions return NULL, and GET_CURR_CODE returns the literal string 'xxx'. This pattern is characteristic of seeded placeholder packages whose signatures are retained for compilation and dependency stability while the substantive implementation resides elsewhere or was deferred.

Key Procedures and Functions

  • GET_CURR_CODE — Resolves a currency code used to label monetary values in business intelligence views. The user search term "get_curr_code" maps directly to this function. It accepts an identifier and a site identifier and returns a currency code as VARCHAR2. In the shipped body it returns the placeholder value 'xxx'.
  • GET_RECORD_TYPE_ID — Returns a numeric identifier corresponding to a supplied period type. This identifier is used to categorize or join records in the period metadata layer. The shipped body returns NULL.
  • GET_PREV_DATE — Derives the prior comparison date for a given as-of date, period type, and comparison type. This value is required for calculating percentage change between the current and preceding period. The shipped body returns NULL.
  • ENT_YR_SPAN — Computes the enterprise year timespan and sequence number for a supplied as-of date, providing the temporal window used in annual aggregated analytics.
  • ENT_QTR_SPAN — Derives enterprise quarter boundaries, including current, previous, and midpoint start dates along with current and prior year values and the resulting timespan.
  • ENT_PRD_SPAN — Provides equivalent enterprise period span derivation at the accounting or reporting period level.
  • WEEK_SPAN — Calculates weekly span boundaries, returning current and prior week start dates plus two additional preceding-period anchors and a timespan value.

All procedures above are declared with NOCOPY OUT parameters and, in the documented body, execute no logic (NULL).

Tables Accessed

The documented ETRM metadata lists no tables referenced through APPS synonyms. Consistent with the stub implementation, the shipped package body performs no SQL against database tables; it is signature-only scaffolding. Any table access associated with its production behavior is not captured in the available documentation.

Usage Notes

No other packages reference IBE_BI_PMV_UTIL_PVT according to the documentation, and it is not surfaced through a public API. Because it is a private utility, invocation is limited to internal IBE business intelligence components, typically lightweight JSP or region-driven calls within the iStore page metadata view framework. Customizations that depend on period comparison logic should treat the shipped functions as placeholders: GET_CURR_CODE returns a hardcoded value and the span routines return no data, so any development relying on real currency or date-span resolution must implement or override the logic rather than call the seeded code directly.