Search Results bis_pmv_util




Overview
Explore in AI Chat

Overview

APPS.BIS_PMV_UTIL is a utility package body within the Oracle E-Business Suite Business Intelligence System (BIS) product family. It supports the Oracle EBS Daily Business Intelligence (DBI) and embedded analytics framework, specifically the rendering and lifecycle management of portal regions and Performance Management Viewer (PMV) components. The package acts as a shared service layer that resolves metadata about regions, responsibilities, menus, users, and portal customizations, and it prepares HTML and formatted content for display in the EBS HTML-based user interface.

Because it is a utility package, BIS_PMV_UTIL does not expose business transactions. Instead, it provides reusable primitives consumed by higher-level reporting, portal, and dashboard packages. Its classification as a UTIL object confirms that its role is to abstract common lookups — region rendering, date handling, portal identification, encoding, and hierarchical attribute resolution — away from the calling code. In Oracle EBS 12.1.1 and 12.2.2, the package remains valid in the APPS schema and is a foundational dependency for the DBI and portal rendering stack.

Key Procedures and Functions

The documented interface contains forty procedures and functions, of which the following representative members illustrate the package's scope:

  • READFNDLOBS — Reads large object content stored in the FND_LOBS repository, supporting portal and report assets.
  • SORTATTRIBUTECODE — Produces a sortable code for an attribute, enabling deterministic ordering of dimensions and attributes in reports.
  • GETCURRENTDATETIME / GETICXCURRENTDATETIME — Return the current database and ICX session date/time values, used to timestamp reports and portal content.
  • RETRIEVE_DATA — A general-purpose retrieval routine for portal and report metadata.
  • GETAPPENDTITLE / GETREPORTTITLE — Resolve formatted display titles for reports and appended region headings.
  • GETHIERARCHYELEMENTID — Returns the hierarchy element identifier used by DBI dimensional structures.
  • GETDIMENSIONFORATTRIBUTE / GETATTRIBUTEFORDIMENSION — Translate between DBI dimension names and their attributes.
  • ENCODE / DECODE1 — Encode and decode portal page and region parameters for URL and HTML handling.
  • GETREPORTREGION — Retrieves the region definition associated with a report.
  • GETFORMATTEDDATE — Formats dates according to the session or application date format.
  • GETPARAMETERVALUE — Extracts a named parameter value from the calling context.
  • GETDEFAULTRESPONSIBILITY — Returns the default responsibility for a user, supporting navigation and portal personalization.
  • STALE_PORTLET — Marks a portlet as needing refresh after underlying data changes.
  • UPDATE_PORTLETS_BYPAGE — Refreshes or updates portlets associated with a given portal page.
  • GET_RENDER_TYPE — Determines how a region or portlet should be rendered.
  • GETPORTALPAGEID — Resolves the identifier of the current portal page.

Tables Accessed

BIS_PMV_UTIL reads and writes a defined set of EBS foundation and portal tables through APPS synonyms. Region metadata is drawn from AK_REGIONS and AK_REGION_ITEMS. Menu and responsibility security information comes from FND_MENUS, FND_MENU_ENTRIES, FND_RESPONSIBILITY, FND_RESP_FUNCTIONS, FND_FORM_FUNCTIONS, and FND_USER_RESP_GROUPS. Portal configuration and personalization data are read from ICX_PORTLET and ICX_PORTLET_CUSTOMIZATIONS. Large object content is accessed through FND_LOBS, application lookups from FND_APPLICATION_VL, and user identity from FND_USER. Java Deployment Repository metadata (JDR_ATTRIBUTES, JDR_COMPONENTS, JDR_PATHS) supports rendering of Java-based regions. DBMS_LOB and DBMS_SQL are invoked programmatically rather than as tables.

Usage Notes

BIS_PMV_UTIL is invoked indirectly by the DBI portal and PMV rendering stack, including packages such as BIS_GRAPH_REGION_HTML_FORMS, BIS_REPORT_UTIL_PVT, BIS_SUBMIT_REQUESTSET, and BISVIEWER. Because it is referenced by sixteen other packages and references no external business APIs, it should be treated as internal infrastructure. Customizations should not modify it directly; extensions should call its documented procedures from custom portal or reporting code. It operates within the Oracle EBS 12.1.1 and 12.2.2 online HTML framework and requires a valid APPS schema and ICX session context.