Search Results fii_gl_sum_mv

Overview

FII_GL_SUM_V1 is an internal database view belonging to the FII (Financial Intelligence) product family within Oracle E-Business Suite. The ETRM metadata explicitly classifies the owning product as "FII - Financial Intelligence (Obsolete)," and the object description is recorded simply as "Internal View." These two facts govern the interpretation of everything that follows: the view was designed for consumption by FII application code rather than as a supported, documented interface for external reporting, and it is no longer an actively maintained artifact in the Oracle EBS 12.1.1 / 12.2.2 stack.

The view's purpose is to expose summarized General Ledger data aggregated along a financial reporting dimension. It projects rows from an underlying materialized view, FII_GL_SUM_MV, presenting time, period type, financial item, manager, line of business, cost center, person, and group identifiers alongside four numeric measures: actual, primary actual, primary budget, and primary forecast. In effect, it is a thin compatibility or abstraction layer over the materialized view, giving FII code a stable relational name without querying the materialized view directly.

Underlying Base Objects

The view text is unambiguous: FII_GL_SUM_V1 is defined over a single object, FII_GL_SUM_MV, a materialized view. It selects eleven key and attribute columns and four additive balance measures, with no joins, unions, filters, or aggregations of its own. The 12.2.2 ETRM metadata records no other referenced base objects.

Because the projection source is a materialized view, FII_GL_SUM_V1 carries the refresh characteristics of that underlying object. Data currency depends entirely on the refresh schedule configured for FII_GL_SUM_MV; the wrapper view neither triggers nor constrains a refresh. The ETRM record notes "Not implemented in this database" for the implementation/DBA data, indicating the object is absent from the reference environment in which the documentation was generated, consistent with its obsolete status.

Key Columns

The ETRM documentation lists the following columns. Minor discrepancies between the column list and the view text are noted where they occur in the metadata.

• TIME_ID — Identifier for the accounting or reporting time dimension, used to slice balances by period.
• PERIOD_TYPE_ID — Identifies the period type (for example, month, quarter, or year) associated with the time element.
• FIN_ITEM — The financial statement line item or account dimension value being reported.
• MANAGER_ID — Identifier of the manager responsible for the reported balances.
• LINE_OF_BUSINESS — The line-of-business segment used to partition financial results; this is the column most directly relevant to the searched term.
• COST_CENTER_ORG_ID — Organization identifier for the cost center associated with the row.
• NAME — Descriptive name attribute, typically for the person or organization context.
• PERSON_ID — Identifier of the person associated with the row.
• GID — Group identifier used for internal grouping or partitioning.
• ACTUAL_B — Actual balance flag or indicator, exposed in the view text.
• PRIM_ACTUAL_G — Primary actual amount; the view text aliases the underlying ACTUAL_G column to this name.
• PRIM_BUDGET_G — Primary budget amount, mapped from BUDGET_G.
• PRIM_FORECAST_G — Primary forecast amount, mapped from FORECAST_G.

The metadata's column list names ACTUAL_G, BUDGET_G, and FORECAST_G directly, whereas the view text selects them under the PRIM_* aliases. Consumers should verify which naming convention applies in their specific instance.

Common Use Cases and Queries

Because the object is obsolete and marked as an internal view, supported use is limited to legacy FII reporting and diagnostics on installations where FII was previously deployed. Typical diagnostic access filters on line of business or financial item:

• Retrieving summarized actuals, budget, and forecast by line of business and period for a given cost center.
• Reconciling FII-extracted balances against the General Ledger for the same line-of-business segment.
• Investigating refresh currency of the underlying materialized view when report totals appear stale.

A representative query is:

SELECT line_of_business, period_type_id, fin_item, SUM(prim_actual_g) actual_amt, SUM(prim_budget_g) budget_amt, SUM(prim_forecast_g) forecast_amt FROM fii_gl_sum_v1 WHERE time_id = :p_time_id GROUP BY line_of_business, period_type_id, fin_item ORDER BY line_of_business, fin_item;

For current implementations, equivalent results should be obtained from supported GL summary objects or the applicable financial reporting schema. FII_GL_SUM_V1 should be treated as a legacy artifact and referenced only with explicit acknowledgement of its obsolete status.