Search Results fin_category_dim_id




Overview

APPS.FII_GL_TREND_SUM_MV_P_V is a reporting view in the Oracle E-Business Suite Financial Intelligence (FII) product family. It presents a flattened, business-friendly projection of the materialized view FII_GL_TREND_SUM_MV, exposing summarized General Ledger trend data organized by time, period type, budget version, and a layered set of financial dimensions (company, cost center, and financial category). The "_P_V" suffix conventionally denotes a "public" presentation view, indicating that the object is intended for direct consumption by reports, dashboards, and analytical queries rather than for internal ETL processing.

The view plays a supporting role in GL trend analysis and budgetary reporting. By surfacing both primary (functional currency) and secondary ("prim") amount columns alongside a baseline figure, it enables period-over-period comparisons of actuals, budgets, forecasts, commitments, obligations, and other encumbrances. The user search term "committed_amount_prim" corresponds directly to one of the view's exposed columns, COMMITTED_AMOUNT_PRIM, which reports committed amounts in the primary ledger currency.

Underlying Base Objects

The view is defined over a single base object: the materialized view FII_GL_TREND_SUM_MV. The ETRM metadata for this view lists no additional referenced objects beyond that materialized view, meaning all dimensional and measure columns are inherited directly from FII_GL_TREND_SUM_MV without joins, unions, or derived expressions in the view definition itself. The view essentially acts as a column-selective pass-through over the materialized view, which itself aggregates GL balances and encumbrance data at a summarized grain.

Because the underlying object is a materialized view, the data available through this view reflects the refresh schedule configured for FII_GL_TREND_SUM_MV. Reporting consumers should be aware that the "SUM" grain means individual journal lines and encumbrance detail are already collapsed; the view is designed for aggregate trend reporting rather than transactional drill-down.

Key Columns

Common Use Cases and Queries

Typical scenarios include trend reporting on commitments versus budget, budget-versus-actual variance analysis by cost center, and multi-period encumbrance dashboards. A representative query filtering on the user's search term might read:

  • Aggregating committed spend by period: SELECT time_id, SUM(committed_amount_prim) FROM apps.fii_gl_trend_sum_mv_p_v GROUP BY time_id ORDER BY time_id;
  • Variance reporting: SELECT company_dim_id, cost_center_dim_id, SUM(prim_budget_g) budget, SUM(prim_actual_g) actual, SUM(committed_amount_prim) committed FROM apps.fii_gl_trend_sum_mv_p_v GROUP BY company_dim_id, cost_center_dim_id;
  • Encumbrance composition across commitment, obligation, and other categories for a given financial category and period.

Because the view is a thin projection of a materialized view, query performance is generally strong for aggregate reporting, and the view is well suited to being consumed by BI Publisher reports, OBIEE repositories, and custom FII dashboards.