Results for “fii_debug_mode”

50+ results




Overview
Explore in AI Chat

AI-generated from documented ETRM metadata — verify critical details on the linked pages.

Overview

FII_AP_MV_REFRESH is an Oracle E-Business Suite package body owned by the APPS schema that supports the Oracle Daily Business Intelligence (DBI) / Enterprise Performance Foundation (FII) reporting layer for Payables. Its core responsibility is to refresh the set of materialized views that hold pre-aggregated Accounts Payable data used by DBI Payables dashboards and analytics. Rather than querying base AP transaction tables directly, these dashboards rely on the summary tables maintained by this package, so the package effectively controls how current the reported AP metrics are.

At the top of the body the package declares a package-level debug flag, g_debug_flag, initialized from the profile option FII_DEBUG_MODE. This is the value users most often search for when troubleshooting the package: setting the FII_DEBUG_MODE profile to Y causes each processing phase to be written to the debug log through FII_UTIL.put_line. The header comment ($Header: FIIAPMVB.pls 115.1 2003/08/05 ...) shows the file has been stable for many years and is shared across the FII product line.

Key Procedures and Functions

Only one procedure is documented in the ETRM metadata:

  • AP_REFRESH — The main entry point. It accepts an error buffer and a return code (both IN OUT NOCOPY VARCHAR2 parameters, following the standard EBS concurrent-program calling convention). Internally it initializes logging via FII_UTIL.initialize, determines the degree of parallelism from BIS_COMMON_PARAMETERS.GET_DEGREE_OF_PARALLELISM(), and then issues a DBMS_MVIEW.REFRESH call against the AP materialized view group. It tracks progress by assigning values to the package variable g_phase (for example, "Refreshing AP MV tables - 1" and "- 2") and emitting those phase markers to the log when debug mode is enabled.

Tables Accessed

The only referenced object documented is the PL/SQL built-in package DBMS_MVIEW, invoked as:

No base AP tables are read or written directly by this package body; all data movement occurs inside the database refresh of the materialized views themselves. Supporting profile options such as BIS_DEBUG_LOG_DIRECTORY control where log and output files are written, and a default directory (/sqlcom/log) is used when the profile is not maintained.

Usage Notes

FII_AP_MV_REFRESH is designed to be run as a scheduled concurrent program rather than interactively. It is typically submitted as part of the DBI Payables data refresh cycle, often from a request set or via the Oracle Applications Manager scheduler at a cadence matching the organization's reporting latency requirements (for example, nightly).

  • Because the interface follows the standard (Errbuf, Retcode) pattern, it can be registered as a concurrent executable and monitored through the standard Concurrent Manager request log.
  • Diagnostic output is controlled by the FII_DEBUG_MODE profile option. When set to Y, phase messages are written to FII_AP_MV_REFRESH.log; the companion output file is FII_AP_MV_REFRESH.out.
  • Parallelism is inherited from the global DBI parameter returned by BIS_COMMON_PARAMETERS.GET_DEGREE_OF_PARALLELISM(); a returned value of 1 is normalized to 0, meaning no parallel refresh.
  • The package is referenced by zero other packages, confirming it is a leaf-level utility invoked directly by the concurrent manager or by custom scheduling code.