Search Results review_chart_render




Overview

The APPS.BIS_GRAPH_REGION_HTML_FORMS package is a PL/SQL specification component within the Oracle E-Business Suite Business Intelligence System (BIS) module, commonly associated with the Oracle Balanced Scorecard and related graphical reporting features. Its core business function is to generate the HTML forms that allow users to enter and store the parameters required for a chart — referenced in the header as a "PHP Chart" — that is rendered within the EBS environment. In the Oracle EBS 12.1.1 and 12.2.2 releases, this package serves as the server-side engine for presenting parameter-entry regions in the HTML-based chart framework, bridging Oracle Database PL/SQL with the web-tier HTML output utilities. The package is declared with AUTHID CURRENT_USER, meaning that its procedures execute with the privileges of the invoking user and resolve object references through the current schema, which is significant for a package that queries responsibility and menu-function data on behalf of the logged-in user.

Key Procedures and Functions

The documented interface exposes three callable units, with REVIEW_CHART_RENDER being the entry point that users most commonly encounter when their interest concerns chart rendering review:

  • REVIEW_CHART_RENDER — The primary rendering routine. It is responsible for producing the HTML output associated with reviewing and rendering a chart region, including the parameter-entry form described in the package header. This is the procedure most directly connected to the chart display workflow.
  • GET_GRAPH_TITLE — A function that returns the graph title value stored in the package-level variable g_graph_title (declared as varchar2(200)). It provides the calling form or rendering context with the chart's configured title.
  • HASFUNCTIONACCESS — A security-oriented function that evaluates whether the current user has access to a given function. This aligns with the package history noting additions (29-May-2001, 03-Jul-2001) related to function-access checks and accessible-function lists, indicating integration with the EBS function security model defined in the FND tables.

Tables Accessed

The package operates against several core EBS foundation tables and a BIS-specific table, all accessed through APPS synonyms:

  • FND_FORM_FUNCTIONS — Provides function definition data, including the web HTML call and argument columns, used to determine how a chart-related function is invoked from the web interface.
  • FND_MENU_ENTRIES — Supplies menu entry prompts and hierarchy, supporting the accessible-function list retrieval logic.
  • FND_RESPONSIBILITY — Used to resolve responsibility names, IDs, and application IDs, forming the basis of the responsibility record type (t_resp_rec) that drives user-specific rendering behavior.
  • BIS_USER_TREND_PLUGS — A BIS-specific table, likely storing user-defined chart or trend plug configurations that influence parameter presentation.
  • HTF and HTP — The standard Oracle HTML generation utilities, used to write the HTML that comprises the chart parameter-entry and review forms.

Usage Notes

This package is typically invoked in the context of EBS HTML-based chart or scorecard pages, where a form region calls REVIEW_CHART_RENDER to output the parameter-entry interface and render the resulting graph. Because AUTHID CURRENT_USER is specified, invocation must occur under a session where the necessary FND and BIS synonyms are visible. The responsibility and function-access utilities reflect tight coupling to the EBS security model, so the package is expected to be driven by the logged-in user's responsibility rather than by a privileged batch context. Its purpose is display-oriented rather than data-mutating, so it is not suited to concurrent program execution. Customizations should avoid modifying the specification directly; extension is best performed through wrapper packages or by leveraging the accessible-function and function-access checks already exposed.