Search Results get_graph_image
Overview
APPS.BSC_PORTLET_GRAPH is a PL/SQL package belonging to the Oracle Balanced Scorecard (BSC) module of Oracle E-Business Suite. In EBS 12.1.1 and 12.2.2, it is responsible for rendering KPI (Key Performance Indicator) graph portlets inside the BSC dashboard and for managing the underlying graph images, plug configuration, access privileges, and per-user customizations associated with those portlets. The package is declared with AUTHID CURRENT_USER, meaning its SQL executes under the privileges of the invoking schema rather than the defining schema, which is typical of APPS-owned utilities that must respect the caller's security context when evaluating responsibility- and user-level access.
Functionally, the package bridges the BSC front-end JSP/HTML layer with the database repository of graph definitions. It generates URLs for tabs and KPI graphs, extracts and stores graph images, retrieves and persists customization settings, and aligns HTML fragments returned over HTTP so that portlet output renders consistently within the portal frame.
Key Procedures and Functions
- PLUG — Registers or removes a portlet plug, optionally assigning a display name and flagging that a plug is being deleted.
- SHOW_ERR — Renders an error message to the portlet, using a content management URL, an inquiry string, and an optional display name.
- HAS_ACCESS — Boolean check that determines whether the current user is authorized to view a given plug.
- RE_ALIGN_HTML_PIECES — Reformats an array of HTML fragments obtained via UTL_HTTP so the pieces can be reassembled into valid markup.
- DRAW_KPI_GRAPH — Produces the KPI graph for a plug, taking content and target URLs, session and plug identifiers, and a display name.
- LAUNCH_BSCKPI_JSP — Initiates the Balanced Scorecard KPI JSP for a session and plug.
- GET_TAB_URL / GET_KPI_URL — Overloaded functions that build tab and KPI navigation URLs, either from an encrypted plug identifier plus cookie value or from numeric session and plug identifiers.
- GET_PLUGINFO_PARAMS — Returns the parameter string describing plug information for a responsibility, session, and plug.
- GET_PORTLET_KPIGRAPH_URL — Constructs the URL for a portlet KPI graph using session, plug, tab, KPI, and responsibility identifiers.
- GET_CUSTOMIZED_KPIGRAPH_URL — Builds a KPI graph URL that reflects a user's customization state, display name, and whether the graph has never been customized.
- GET_CUSTOMIZED_DATA_PRIVATE / SET_CUSTOMIZED_DATA_PRIVATE — Retrieve and persist the private customization record for a session and plug, exposing the responsibility identifier as an OUT parameter on retrieval.
- GET_CUSTOMIZATION / SET_CUSTOMIZATION — Read and write the customization settings governing how a portlet's graph is displayed.
- GET_GRAPH_IMAGE — The function matching the user's search term; retrieves the stored graph image associated with a KPI graph definition so it can be delivered to the portlet.
- SAVE_GRAPHKEY — Persists a graph key, linking a generated graph back to its defining record.
Tables Accessed
The package reads and writes BSC_KPI_GRAPHS (graph definitions), BSC_SYS_IMAGES and BSC_SYS_IMAGE_ID_S (image storage and sequence), BSC_TAB_INDICATORS (tab-to-KPI associations), BSC_USER_KPIGRAPH_PLUGS (user plug instances), BSC_USER_KPI_ACCESS and BSC_USER_TAB_ACCESS (access control), FND_RESPONSIBILITY (responsibility validation), and ICX_PAGE_PLUGS (portal plug registry). Utility objects include UTL_HTTP (fetching remote HTML), HTP and PLITBLM and UTL_RAW (HTML output, PL/SQL tables, and raw image handling).
Usage Notes
BSC_PORTLET_GRAPH is invoked server-side through the Balanced Scorecard dashboard and portal pages rather than directly by end users. It is not referenced by any other packaged API in the documented metadata, so its callers are limited to BSC JSP pages, portal region renderers, and custom extensions. Custom code may call GET_GRAPH_IMAGE or SAVE_GRAPHKEY to manipulate graph images programmatically, while GET_TAB_URL and GET_KPI_URL support custom navigation components. Because access decisions flow through HAS_ACCESS and the BSC access tables, callers must execute the package in a session where the authenticated EBS user and responsibility are established.