Search Results baseline_amount_prim

Overview

FII_GL_TREND_SUM_MV_P_V is an Oracle E-Business Suite view owned by the APPS schema and registered as a VALID object within the FII (Financial Intelligence) product family. It is a thin projection view defined directly over the materialized view FII_GL_TREND_SUM_MV, exposing a curated subset of the materialized view's columns under a presentation-oriented name (the "_P_V" suffix denoting a presentation view). Its role is to supply the Financial Intelligence trending and summarization dashboards with pre-aggregated General Ledger balances and budget, forecast, commitment, obligation, and other encumbrance-style amounts, keyed by time, period type, budget version, and a hierarchy of company, cost center, and financial category dimensions.

Because the underlying object is materialized, the view is intended for read-heavy analytical reporting rather than transactional access. The view does not perform additional transformation; it simply renames a subset of the materialized columns (e.g., PARENT_COMPANY_DIM_ID to PARENT_COMPANY_ID, PRIM_ACTUAL_G to ACTUAL_G) to the naming conventions expected by the presentation layer.

Underlying Base Objects

The single documented base object is the materialized view FII_GL_TREND_SUM_MV, referenced in the view text as the sole FROM source. No other base tables are documented in the ETRM metadata, and the view performs no joins, unions, or aggregation of its own — it is a straight SELECT of named columns from the materialized view. The relationship is therefore one of pure delegation: the materialized view performs the heavy aggregation over GL fact data, and this view surfaces a presentation-ready column set for the Financial Intelligence reporting layer.

Key Columns

• TIME_ID, PERIOD_TYPE_ID: Time and period-type keys used to align the summarized amounts to the reporting calendar.
• BUDGET_VERSION_DATE: Identifies the budget version applicable to the summarized row.
• COMPANY_DIM_ID, COST_CENTER_DIM_ID, FIN_CATEGORY_DIM_ID: Dimension identifiers for the reporting entity hierarchy, with corresponding PARENT_* columns allowing rollup to a higher level in the company, cost center, and financial category hierarchies.
• TOP_NODE_FIN_CAT_TYPE: The column the user searched for. It carries the top-node classification of the financial category, allowing reports to group financial categories by their top-level type.
• ACTUAL_B, PRIM_ACTUAL_G: Actual balance/amount indicators and the primary actual amount.
• PRIM_BUDGET_G, PRIM_FORECAST_G: Primary budget and forecast amounts.
• COMMITTED_AMOUNT_PRIM, OBLIGATED_AMOUNT_PRIM, OTHER_AMOUNT_PRIM, BASELINE_AMOUNT_PRIM: Commitment, obligation, other, and baseline amounts used for encumbrance and budget-variance reporting.

Common Use Cases and Queries

Typical usage involves trend analysis, budget-versus-actual comparisons, and rollup reporting by financial category, company, or cost center. A representative query grouping by the top-node financial category type is:

• Trend by financial category type: SELECT top_node_fin_cat_type, time_id, SUM(prim_actual_g) actual, SUM(prim_budget_g) budget FROM fii_gl_trend_sum_mv_p_v GROUP BY top_node_fin_cat_type, time_id;
• Company rollup: SELECT parent_company_id, SUM(actual_g), SUM(budget_g) FROM fii_gl_trend_sum_mv_p_v GROUP BY parent_company_id;
• Budget versus actual variance: SELECT fin_category_dim_id, prim_budget_g - prim_actual_g variance FROM fii_gl_trend_sum_mv_p_v WHERE budget_version_date = :p_version;
• Commitment/obligation view: SELECT company_dim_id, committed_amount_prim, obligated_amount_prim FROM fii_gl_trend_sum_mv_p_v WHERE time_id = :p_time_id;

Because the data is sourced from a materialized view, query performance is favorable for these aggregation patterns, and refresh schedules of FII_GL_TREND_SUM_MV govern data currency.