Search Results bis_mv_refresh




Overview
Explore in AI Chat

Overview

The concurrent program BIS_MV_REFRESH is delivered as part of the Oracle Applications BIS product family, which provides the business intelligence infrastructure that underpins daily business intelligence (DBI) and related analytical reporting in Oracle E-Business Suite. Its user-facing name is the BIS Materialized View Refresh Program. The program exists to refresh the materialized views (MVs) that store pre-aggregated summary data used by BIS and DBI dashboards, thereby keeping summary figures synchronized with the underlying transaction and accounting tables in the transactional modules.

According to the ETRM metadata, the program is enabled (Yes) and is documented as being "Used by Request Set Generater internally." This indicates that it is generally invoked not by end users directly but programmatically as a member of generated request sets. It is an internal, infrastructure-oriented program whose principal purpose is the maintenance of the BIS materialized view layer.

Execution Details

The concurrent program metadata records the following execution attributes:

  • Execution Method: PL/SQL Stored Procedure
  • Argument Method: Standard
  • Executable: BIS_MV_REFRESH
  • Execution File Name: bis_mv_refresh.refresh
  • Subroutine Name: (not specified)
  • Product: BIS - Applications BIS
  • Enabled: Yes

The executable's user-facing description is "Executable for BIS MV Refresh Program," consistent with a PL/SQL entry point that accepts standard arguments and performs MV refresh logic against the database.

How to Run

Because the program is a standard concurrent program, it may be submitted through the Submit Requests form or the concurrent manager's request submission interface (SRS). However, the documentation explicitly states that it is used internally by the Request Set Generator, so the normal submission path is through the request sets that the Generator creates rather than manual submission.

The documented request set arguments reveal the parameter structure. Arguments are supplied through descriptive flexfield segments ATTRIBUTE1 and ATTRIBUTE2, each defaulting to $SRS$.BIS_MV_REFRESH. ATTRIBUTE1 defaults to the value YCInitial Refresh, and surviving ATTRIBUTE2 values reference specific materialized views, including:

Users who must run the program manually typically supply the target materialized view name through ATTRIBUTE2 and the refresh mode through ATTRIBUTE1. Because the parameters are descriptive flexfield-based, their display and interpretation depend on the request set definition rather than a fixed parameter list.

Related Objects

The program operates on the BIS/DBI materialized view layer. Objects commonly associated with it include the summary materialized views named in its arguments — FII_AR_REV_SUM_MV, FII_GL_MGMT_PRD_MV, and FII_GL_BASE_MV — which aggregate receivables revenue and general ledger balances respectively. It is also closely coupled with the Request Set Generator and the request sets it produces, and with the DBI summary and reporting components that consume the refreshed views. Administrative attention should focus on refresh scheduling, because MV staleness directly affects the accuracy of BIS dashboards. As always, refer to the current ETRM documentation for the authoritative configuration in a given release, as 12.1.1 and 12.2.2 installations may exhibit minor metadata differences.