Search Results bis_pmf_get_dimlevels_pvt




Overview
Explore in AI Chat

Overview

APPS.BIS_PMF_GET_DIMLEVELS_PVT is a private PL/SQL package body belonging to the Oracle E-Business Suite (EBS) Business Intelligence System (BIS) and Performance Management Framework (PMF) components. It resides in the APPS schema and carries a status of VALID in both release 12.1.1 and 12.2.2 environments. The package is classified as a Private (PVT) API, meaning it is not intended for direct invocation by external or customer-developed code; instead it is consumed internally by its corresponding public API, BIS_PMF_GET_DIMLEVELS_PUB, which is listed among its dependencies.

The central business purpose of this package is the resolution of dimensional level metadata for analytical and reporting queries. In the BIS/PMF architecture, dimensions (for example, Time, Product, Customer) are organized into levels (Year, Quarter, Month), and reporting tools must translate a requested dimensional hierarchy into the correct SQL constructs, source columns, and value sets. BIS_PMF_GET_DIMLEVELS_PVT encapsulates that logic, producing select strings and dimension level value data used to construct balanced scorecard and performance management queries. It is a supporting, low-level utility whose output feeds higher-level public framework routines.

Key Procedures and Functions

The ETRM metadata documents eleven procedures and functions within this package body. The principal documented routines include:

  • GET_DIMLEVEL_SELECT_STRING — Builds a SQL SELECT string for a requested dimension level, forming the query fragment used by consuming report logic.
  • ISACCOUNTING_FLEXFIELD — Evaluates whether a given dimension level corresponds to an accounting flexfield, allowing the package to apply the appropriate key flexfield handling.
  • GET_EDW_SELECT_STRING — Produces a select string oriented to the Enterprise Data Warehouse (EDW) source, distinguishing warehouse-based extraction from operational sources.
  • GET_BIS_SELECT_STRING — Produces a select string oriented to the native BIS source structures.
  • GET_DIMLEVEL_VALUES_DATA — Retrieves the actual dimension level value data used to populate or validate dimensional hierarchies.
  • GET_DIMLEVEL_SELECT_WRAP — Wraps the generated select strings (typically with row limiting or grouping constructs) so they can be embedded as subqueries.
  • GET_DIM_LEVEL_SOURCE — Determines the physical source of a dimension level, resolving which table or view supplies the level's data.

Parameter lists are not enumerated in the available metadata and should be confirmed from the package specification before any custom use.

Tables Accessed

The package references several base and framework tables through APPS synonyms:

  • BIS_DIMENSIONS — Master definition of analytical dimensions.
  • BIS_LEVELS / BIS_LEVELS_VL — Level definitions and their translatable (VL) descriptions belonging to each dimension.
  • BSC_KPIS_B — Balanced Scorecard KPI definitions, associating measures with dimensional levels.
  • BSC_SYS_DIM_LEVELS_B / BSC_SYS_DIM_LEVELS_VL — System dimension level definitions and their translated names.
  • BSC_SYS_DIM_LEVEL_RELS — Relationships between system dimension levels, used to resolve hierarchical ordering.
  • AK_REGIONS — Oracle AK (Application Kit) region metadata, used to identify regional context for reporting.
  • PLITBLM — The standard PL/SQL integer table type used for in-memory collections during processing.

These tables supply the dimension, level, KPI, and hierarchy metadata required to generate correct SQL and value data.

Usage Notes

Because BIS_PMF_GET_DIMLEVELS_PVT is a PVT (private) package, it is not a supported integration point. It is invoked indirectly through the public wrapper BIS_PMF_GET_DIMLEVELS_PUB, and it in turn relies on other framework packages including BIS_UTILITIES_PVT, BSC_DIMENSION_LEVELS_PUB, BSC_UTILITY, BIS_PMF_QUERY_ATTRIBUTES, FND_API, FND_MESSAGE, and FND_MSG_PUB. The ETRM metadata records that the package is not referenced by any database object directly, though eight other packages depend on it.

Typical invocation paths are Balanced Scorecard and PMF reporting pages, concurrent programs that generate dimension-level queries, and internal framework calls that translate user-selected dimension levels into executable SQL. Custom developers requiring similar functionality should call the PUBLIC API rather than this private body, and should never modify the package, as changes may be overwritten by Oracle patches. Any diagnostic work should focus on dependency objects listed above and on the PL/SQL call stack captured during failure.