Search Results get_fact_mv_name




Overview
Explore in AI Chat

Overview

The APPS.ISC_FS_TASK_BACKLOG_RPT_PKG package belongs to the Oracle E-Business Suite ETRM (Enterprise Tracking and Reporting Module) family of reporting utilities. Its name and the structure of its API indicate that it supports the generation of a Task Backlog report, a diagnostic and operational listing that surfaces open or pending tasks within the ETRM task-tracking framework. The report exposes backlog items so that operational users, dispatchers, or service managers can monitor outstanding work and prioritize resolution. The package header carries the revision identifier iscfstkbsrpts.pls 120.1 dated 2006/04/12, which places its lineage in the 11i/12.0 era; the object nevertheless remains a valid member of the APPS schema in Oracle EBS 12.1.1 and 12.2.2, where it continues to be consumed by the reporting framework.

The package is not a business entity API in the transactional sense. It is a reporting support package that supplies SQL fragments and BI (Business Intelligence) publisher query metadata to a surrounding reporting engine. It is classified as OTHER, meaning it is neither a public nor a private business API, and it carries no open-interface commitments. Instead, it is intended for internal consumption by the ETRM reporting infrastructure.

Key Procedures and Functions

Three program units are documented in the package specification:

  • GET_TBL_SQL — a procedure that constructs the table-level (summary) SQL statement for the Task Backlog report. It accepts page parameters and returns a dynamically assembled SQL string together with its query attribute metadata, which the calling reporting framework executes to produce the master block of the report.
  • GET_DTL_RPT_SQL — a procedure that builds the detail-level SQL for the same report. It follows the same parameter-and-output pattern as GET_TBL_SQL, allowing the report engine to render drill-down or detail rows that correspond to the summary rows produced by the table query.
  • GET_FACT_MV_NAME — a function returning a VARCHAR2. Given a report type, page parameters, and a dimension bitmap, it resolves and returns the name of the fact materialized view that should be queried for the requested report context. This is the entry point most likely to be referenced by users searching for get_fact_mv_name, since the function is the mechanism by which the package selects the correct aggregate/MV source at runtime.

No parameter lists are invented here; the documented signatures show that all three units align to the BIS_PMV_PAGE_PARAMETER_TBL and BIS_QUERY_ATTRIBUTES_TBL types used by the BI publisher page model.

Tables Accessed

The ETRM metadata provided does not enumerate the physical tables referenced by this package. Because the package generates SQL at runtime through GET_TBL_SQL and GET_DTL_RPT_SQL, the actual table set is determined dynamically by the source fact materialized view selected by GET_FACT_MV_NAME and by the underlying ETRM task tables. Static analysis of the package would reveal only indirect references via APPS synonyms; the metadata confirms that no direct table dependency list is published. Practically, the package reads the fact view whose name it resolves, and it is referenced by one other package, indicating a layered dependency in the ETRM reporting stack.

Usage Notes

This package is not invoked directly by end users through an Oracle Forms screen. It is called by the ETRM reporting framework, most likely a concurrent program or a BI Publisher-based page, which passes a BIS_PMV_PAGE_PARAMETER_TBL populated from user-selected report criteria. Custom code should treat GET_FACT_MV_NAME as an internal helper: it is appropriate to recognize it as the fact-view resolver for the Task Backlog report, but inappropriate to depend on its return value in customizations, since the MV naming convention is subject to change between 11i, 12.1.1, and 12.2.2. When troubleshooting missing data on the Task Backlog report, verifying that the fact MV returned by this function exists and is refreshed is a standard diagnostic step. Because the package is owned by APPS and classified as OTHER, no upgrade guarantee protects modifications; extensions should wrap, not modify, the shipped logic.