Search Results web_html_call

Overview

BIS_BIA_RSG_PAGE_STATUS_V is an Oracle E-Business Suite database view owned by the APPS schema and registered against the FND — Application Object Library product family. It is part of the Oracle Business Intelligence System (BIS) infrastructure that underpins the Daily Business Intelligence (DBI) and Management Reporting components embedded throughout EBS 12.1.1 and 12.2.2. The view is a reporting and navigation bridge: it maps the physical artefacts that make up the BIS reporting experience — Functional Administrator-registered pages and reports — to the menu functions through which users launch them. Its status is VALID, indicating that it has been compiled successfully against its underlying objects and can be queried reliably by concurrent programs, OAF pages, and diagnostic scripts.

Rather than storing transactional business data, the view exposes the function-to-object relationship that the EBS security and navigation layers require. Because it depends on the FND function metadata, the view reflects the same definitions that appear in the Menus and Functions forms, and is therefore sensitive to product installation and language patch levels.

Underlying Base Objects

The view is defined with a compound UNION of two correlated SELECT statements, both of which draw on the same two source objects:

• FND_FORM_FUNCTIONS_VL — a translated view over the FND function definitions (FND_FORM_FUNCTIONS and FND_FORM_FUNCTIONS_TL). It supplies the function ID, the user-facing function name, the function type, and the WEB_HTML_CALL expression that determines where the function navigates.
• BIS_OBJ_PROPERTIES — the BIS object registry that holds metadata about every BIS artefact (pages, reports, and their properties). The OBJECT_NAME column is joined to the function through the helper API BIS_IMPL_DEV_PKG.GET_FUNCTION_BY_PAGE, and OBJECT_TYPE distinguishes pages from reports.

The first branch of the UNION selects function rows whose WEB_HTML_CALL contains BIS_COMPONENT_PAGE&AKREGIONAPPLICATIONID=191, i.e. functions that launch BIS component pages owned by that specific AK region application. The second branch captures functions of type WWW or JSP whose WEB_HTML_CALL points to BISVIEWER.SHOWREPORT or the OA.jsp BISREPORTPG path, thereby identifying report-launching functions. The two branches are combined with DISTINCT and ordered by USER_FUNCTION_NAME.

Key Columns

• ID (F.FUNCTION_NAME) — the internal, unique function key. This is the value stored in menu entries and used by FND security functions such as FND_FUNCTION.
• VALUE (F.USER_FUNCTION_NAME) — the translatable, user-visible label of the function as it appears in menus and the Navigator.
• TYPE (OBJECT_TYPE) — the BIS object type, primarily PAGE or REPORT, indicating which class of BIS artefact the row represents.

Common Use Cases and Queries

Typical uses include auditing which BIS pages and reports are reachable from the current function registry, troubleshooting broken DBI links, and reconciling BIS development deployments with FND metadata. The following query lists all report-type functions:

SELECT id, value, type
FROM   apps.bis_bia_rsg_page_status_v
WHERE  type = 'REPORT'
ORDER  BY value;

A targeted lookup validates that a known page function is still registered:

SELECT id, value, type
FROM   apps.bis_bia_rsg_page_status_v
WHERE  UPPER(value) LIKE '%DAILY%';

Because the result set is DISTINCT and ordered by function name, the view is also convenient for populating LOVs or building administrative reports that compare BIS object properties with the functions exposed to end users.