Search Results bis_component_page

Overview

APPS.BIS_BIA_RSG_PAGE_STATUS_V is a reporting and integration view within the Oracle Business Intelligence System (BIS) component of Oracle E-Business Suite. It exposes a consolidated list of Oracle EBS functions that are associated with BIS component pages and BIS reports, and it is the object typically resolved when a user searches for the term bis_component_page. In practice the view serves as a bridge between the EBS function registry (FND_FORM_FUNCTIONS) and the BIS object property repository (BIS_OBJ_PROPERTIES), allowing administrators and integrators to enumerate which function names correspond to a given BIS page or report entry point. The view is documented for both EBS 12.1.1 and 12.2.2, and its definition was captured in the ETRM repository under the 12.2.2 metadata set. Because it is a view rather than a table, it introduces no physical storage of its own and derives all of its content dynamically at query time.

Underlying Base Objects

The ETRM metadata documents no base objects explicitly, but the view text itself reveals that it is defined over two underlying sources: FND_FORM_FUNCTIONS_VL (aliased F) and BIS_OBJ_PROPERTIES (aliased O). The view text also invokes the PL/SQL function BIS_IMPL_DEV_PKG.GET_FUNCTION_BY_PAGE, which resolves a page object name to its owning function name. Two UNION-style branches are combined:

• A PAGE branch that joins FND_FORM_FUNCTIONS_VL to BIS_OBJ_PROPERTIES where the function's WEB_HTML_CALL contains the literal BIS_COMPONENT_PAGE concatenated with &AKREGIONAPPLICATIONID=191, the joined object is of type PAGE, and the function returned by BIS_IMPL_DEV_PKG.GET_FUNCTION_BY_PAGE matches the function name.
• A REPORT branch that selects function and object records where the object type is WWW or JSP and the WEB_HTML_CALL contains either BISVIEWER.SHOWREPORT or the OA.jsp path /oracle/apps/bis/report/webui/BISReportPG, again matching function name to object name for REPORT-type objects.

The final result set is ordered by USER_FUNCTION_NAME and deduplicated using DISTINCT.

Key Columns

• ID — sourced from F.FUNCTION_NAME. This is the internal function identifier used by the EBS function security and menu framework.
• VALUE — sourced from F.USER_FUNCTION_NAME. This is the user-facing label for the function, and it is the column used to order the output.
• TYPE — sourced from O.OBJECT_TYPE, and restricted by the WHERE clauses to the literal values PAGE, WWW, or JSP. It distinguishes component-page entries from report entries.

These three columns effectively form a lookup list suitable for populating LOVs, menu-driven navigation, or diagnostic reports.

Common Use Cases and Queries

Typical applications of this view include troubleshooting BIS page/function mismatches, auditing which functions are wired to BIS component pages, and generating picklists for report or page selection in custom concurrent programs. A representative query follows:

• SELECT id, value, type FROM apps.bis_bia_rsg_page_status_v ORDER BY value;
• SELECT value FROM apps.bis_bia_rsg_page_status_v WHERE type = 'PAGE';
• Join with FND_FORM_FUNCTIONS_VL on ID to retrieve additional function metadata such as parameters or form associations.

Because the PAGE branch requires the literal application identifier 191 in the WEB_HTML_CALL string, only functions registered against that region application are returned; sites with customized or renumbered region applications may need to adjust expectations accordingly. Queries should be executed with the APPS schema context, as the view is owned by APPS.