Search Results get_fnd_profile_value




Overview

The APPS.BIS_PMF_PORTLET_UTIL package is a utility package within the Oracle E-Business Suite Business Intelligence System (BIS) module, specifically supporting the Performance Management Framework (PMF) portlet infrastructure. Its primary business function is to provide shared helper logic for rendering, formatting, and managing portlet content that displays performance indicators and measures to end users. In EBS 12.1.1 and 12.2.2, this package underpins the display layer of PMF portlets surfaced through the Oracle Applications Framework (OAF) and the portal infrastructure, ensuring that measure values, currency symbols, scaling factors, and region attributes are consistently formatted and presented.

The package header reveals extensive support for auto-scaling of numeric values (thousands, millions, billions, trillions), currency indicator formatting, and region-level attribute handling. It also manages user-specific and customization-aware behavior, such as detecting demonstration rows, authorized content, and customized portlet rows.

Key Procedures and Functions

The 32 documented procedures and functions fall into several functional categories:

These routines are consumed internally by the portlet rendering logic and are not intended as a public API for external callers.

Tables Accessed

The package references the following tables through APPS synonyms, driving its read and write behavior:

Usage Notes

BIS_PMF_PORTLET_UTIL is invoked indirectly rather than through direct user interaction. It is called by two other packages in the PMF portlet stack during portlet page generation, typically triggered when a user opens a PMF dashboard or portal page in EBS. In 12.1.1 and 12.2.2 the package operates within the OAF and portal runtime, applying NLS-aware number and currency formatting (as indicated by the auto-scaling constants and thousand/million symbol messages). Because it is classified as a utility package with no documented public API contract, customizations should avoid direct calls and instead rely on the supported portlet configuration mechanisms.