Search Results fii_gl_rev_prod

Overview

FII_GL_REV_PROD is a PL/SQL package owned by the APPS schema in Oracle E-Business Suite, documented in ETRM for release 12.1.1 and applicable to 12.2.2. Its name and signature place it within the Oracle Financial Intelligence (FII) family of reporting packages, which underpin the Financials Intelligence and General Ledger analysis dashboards delivered through the Oracle Daily Business Intelligence (DBI) and BIS (Business Intelligence System) infrastructure. The package exists to supply revenue-by-product reporting logic to the BIS/PMV runtime rather than to perform transactional processing. It is declared with AUTHID CURRENT_USER, meaning its SQL executes under the privileges of the invoking user and resolves unqualified object names against that user's schema — a deliberate design choice for reporting packages that must obey the calling session's security context and any row-level or organization-level access restrictions established by the reporting framework.

The package header carries the revision marker $Header: FIIGLRPS.pls 115.4 2003/12/26, identifying it as a long-standing component that has remained stable across the 11i-to-R12 lifecycle.

Key Procedures and Functions

ETRM documents a single public program unit for this package:

• GET_REV_BY_PROD — the package's sole documented procedure. Its parameter signature follows the standard BIS_PMV pattern: it accepts a page parameter table (p_page_parameter_tbl) as input, and returns a SQL statement string along with a query attributes collection (rev_by_prod_sql and rev_by_prod_output) as output parameters. In the Oracle BIS/PMV architecture this pattern is used to build report SQL dynamically at runtime: the page parameter table carries the dashboard's user-selected filters (period, ledger, organization, product, and similar criteria), and the procedure returns a fully formed query together with the column metadata and formatting attributes the PMV engine requires to render the result set. The procedure name indicates its specific purpose: aggregating general ledger revenue amounts by product for financial reporting.

Both output parameters are declared NOCOPY, an optimization that passes the large SQL string and attribute collection back to the caller by reference, avoiding the memory overhead of copying these structures. No private helper procedures or functions are exposed in the documented header.

Tables Accessed

The ETRM extract for this object lists no directly referenced tables, which is consistent with its design: the procedure constructs and returns a SQL text rather than executing queries itself. Because the package is declared AUTHID CURRENT_USER and exists purely to generate SQL, the actual table access occurs when the caller — the BIS/PMV execution engine — subsequently parses and runs the returned statement. Based on the package's stated function, the generated SQL targets general ledger revenue and product-dimension data, along with the standard FII/BIS reporting views and materialized structures that the Financials Intelligence product uses to aggregate GL balances. Determining which physical objects are touched therefore requires inspecting the dynamically built SQL at runtime rather than the package body's static dependencies.

Usage Notes

FII_GL_REV_PROD is not intended for direct invocation by end users, forms, or concurrent programs. It is an internal integration point between the Financials Intelligence reporting layer and the PMV/BIS page rendering framework. The PMV engine calls GET_REV_BY_PROD when a user opens or refreshes the corresponding revenue-by-product dashboard region, passing the current page parameter context and receiving back the query and its attributes. ETRM records that no other packages reference this one, confirming that its callers are external to the PL/SQL package layer — namely the BIS/PMV runtime. Customizations should avoid modifying the package body, since the returned SQL must match the column and attribute contract expected by the PMV metadata; extending or overriding the report is more safely accomplished through the standard BI Publisher or DBI customization mechanisms. Because the code has been stable since 2003 and relies on BIS-prefixed types, upgrades to 12.2.2 should be assessed for compatibility with the newer BI Publisher-based reporting stack that supersedes the original PMV engine.