Search Results bis_trend_plug




Overview
Explore in AI Chat

Overview

APPS.BIS_TREND_PLUG is an Oracle E-Business Suite PL/SQL package that forms part of the Business Intelligence System (BIS) / Daily Business Intelligence infrastructure. It is compiled with AUTHID CURRENT_USER and resides in the APPS schema, with the header BISTRNDS.pls at version 120.1. Its central business function is to render and manage the embedded trend graphs, portlets, and report links that appear on Oracle EBS dashboards and self-service pages. The package takes a report function URL, resolves the underlying report output, and returns HTML markup suitable for inline display within a portlet region. In addition, it handles portlet lifecycle operations — showing, personalizing, and persisting user-specific portlet settings — and manages related-link navigation from within portlet content. Although the package is marked "noship" in its header, its procedures are referenced by other EBS packages and are known to ETRM with an API classification of OTHER.

Key Procedures and Functions

The package exposes nineteen documented procedures. The procedure most directly associated with the search term is GET_GRAPH_FROM_URL, which accepts a trend type and a report function URL and returns the resulting HTML image markup (x_img_html) for embedding in a portlet. SHOW renders a portlet given optional session, plug, and display-name identifiers, with a delete flag. SETTABLESTYLES applies the standard table styling used by portlet output. VIEW_REPORT_FROM_PORTLET launches a report from a portlet region, resolving region code, function name, schedule, page, object type, and responsibility. SHOWPORTLETSTATUS reports whether a portlet's underlying report is available together with its last update date.

CUSTOMIZEPORTLET persists portlet personalization settings (responsibility, session, region, function, user, plug, schedule, file, schedule override, and display options) for a given user. INITIALISERLPORTLET initializes a related-links portlet and returns its plug identifier. INVOKEBISRUNFUNCTION and INVOKERFFUNCTION execute the function associated with a BIS or report request. CHECKUSERCUSTOMIZERLPORTLET verifies whether a given user has customized the portlet and CHECKANDSETRL performs the corresponding related-link setup check. Supporting lookup procedures include GETRESPINFO, GETFUNCTIONID, GETFUNCTIONNAME, and GETUSERFUNCTIONNAME. Navigation helpers include PROCESSLINKEDPAGE, LAUNCHLINKEDPAGE, PROCESSPAGEFROMREPORT, and LAUNCHPAGEFROMREPORT, which resolve and open linked destination pages associated with a portlet or report.

Tables Accessed

The package reads and writes several EBS repository tables through APPS synonyms. ICX_PORTLET_CUSTOMIZATIONS and ICX_PAGE_PLUGS_S store per-user portlet personalization and page plug definitions. BIS_SCHEDULER and BIS_SCHEDULE_PREFERENCES hold the schedule definitions and user scheduling preferences that determine when a portlet report is refreshed. BIS_CUSTOM_RELATED_LINKS stores the related-link configuration rendered by the related-links portlet. FND_FORM_FUNCTIONS, FND_FORM_FUNCTIONS_TL, and FND_RESPONSIBILITY are consulted to resolve function names, translated descriptions, and responsibility context for a given portlet. FND_LOBS is used to retrieve stored file/lob content referenced by the portlet. DUAL, HTP, PLITBLM, and UTL_HTTP are utility objects: HTP for HTML generation, PLITBLM for PL/SQL table buffering, and UTL_HTTP for outbound HTTP calls made when fetching graph or report content from a URL.

Usage Notes

BIS_TREND_PLUG is invoked internally by the Oracle EBS Dashboard and Daily Business Intelligence portlet framework rather than being called directly from a form or concurrent program. Typical invocation paths are the portlet rendering engine, which calls SHOW and GET_GRAPH_FROM_URL to build the visible dashboard content, and the portlet personalization page, which calls CUSTOMIZEPORTLET and CHECKUSERCUSTOMIZERLPORTLET to persist user preferences. Report launch and related-link navigation are driven by VIEW_REPORT_FROM_PORTLET, PROCESSLINKEDPAGE, and LAUNCHLINKEDPAGE. Because the package is compiled AUTHID CURRENT_USER and is referenced by at least two other packages, customizations should treat it as an internal, unsupported API. Developers writing custom portlets or diagnosing missing trend graphs should verify that the report function URL passed to GET_GRAPH_FROM_URL resolves correctly, that the schedule records exist in BIS_SCHEDULER and BIS_SCHEDULE_PREFERENCES, and that UTL_HTTP access is permitted from the database.