Results for “forecast_g”

AI-generated from documented ETRM metadata — verify critical details on the linked pages.

Overview

The view FII_GL_TREND_SUM_MV_S_V belongs to the Oracle EBS FII – Financial Intelligence product family, a module that Oracle has designated as Obsolete. In ETRM 12.1.1 and 12.2.2, this object is documented as a reporting/analytics view intended to expose summarized General Ledger (GL) trend data for financial intelligence dashboards and analytical reporting. Its naming convention — the _MV_S_V suffix — indicates that it is a "view over a materialized view," specifically a secured or synonym-based view layered on top of the underlying materialized view FII_GL_TREND_SUM_MV. The _S_ segment conventionally signals a secured view, meaning row-level security or organization-based filtering may be applied through the view layer rather than directly against the base materialized view.

The view presents pre-aggregated GL balances organized along a financial dimensional model — time, period type, company, cost center, and financial category — with separate measures for actual, budget, and forecast amounts. This design supports trend analysis across accounting periods, which is the central purpose of the FII GL Trend functionality. The documentation explicitly records that the view is "Not implemented in this database," confirming that on the environment captured by the ETRM extract, the object is defined in the data dictionary or in Oracle's delivered metadata but is absent from the physical schema.

Underlying Base Objects

According to the documented view text, FII_GL_TREND_SUM_MV_S_V is defined as a direct projection over a single base object:

• FII_GL_TREND_SUM_MV — the materialized view that carries the physical, pre-aggregated GL trend data. The view selects its columns without joins, filters, or aggregation, acting as a presentation and security wrapper.

No additional base tables, dimensions, or lookup objects are documented as referenced. The ETRM metadata records the referenced base objects as "none documented," which is consistent with a view whose only dependency is the materialized view named in its definition. Because the underlying materialized view is itself derived from GL balances and FII dimensional structures, the trend data originates from the GL schema, but that lineage is indirect and not exposed through this view's own definition.

Key Columns

The view exposes a dimensional key set together with a set of financial measures. Notable columns include:

• TIME_ID — the accounting time/period key used to sequence trend data.
• PERIOD_TYPE_ID — identifies the period type (for example, month, quarter, or year) applied to the trend.
• BUDGET_VERSION_DATE — the budget version reference that qualifies budget measures.
• PARENT_COMPANY_DIM_ID / COMPANY_DIM_ID — the company dimension and its parent, supporting hierarchical roll-ups. The column list also documents PARENT_COMPANY_ID and COMPANY_ID as exposed attributes.
• PARENT_COST_CENTER_DIM_ID / COST_CENTER_DIM_ID — cost center dimension keys for organizational analysis.
• PARENT_FIN_CATEGORY_DIM_ID / FIN_CATEGORY_DIM_ID — financial category dimension keys for line-item classification.
• TOP_NODE_FIN_CAT_TYPE — the top-node financial category type, used to classify the highest level of the financial category hierarchy.
• ACTUAL_B, SEC_ACTUAL_G, SEC_BUDGET_G, SEC_FORECAST_G — the measure columns in the view text, with corresponding documented column names ACTUAL_B, ACTUAL_G, BUDGET_G, FORECAST_G. The _B suffix denotes a base (stored) measure value, while the _G suffix denotes a generated or derived measure, typically calculated from the base amount using a formula or security rule.

Common Use Cases and Queries

This view is intended for financial trend and variance reporting within FII. Typical use cases include period-over-period actual versus budget comparison, forecast tracking, and hierarchical roll-up of balances by company, cost center, and financial category. Because the object is marked obsolete and not implemented, queries are primarily of interest for upgrade assessment, impact analysis, or custom reporting that historically referenced FII GL Trend data.

A representative query that retrieves trend measures for a given period type and company follows:

• SELECT time_id, period_type_id, company_dim_id, cost_center_dim_id, fin_category_dim_id, actual_b, budget_g, forecast_g FROM fii_gl_trend_sum_mv_s_v WHERE period_type_id = :period_type AND company_dim_id = :company ORDER BY time_id;
• To analyze actual versus budget variance: SELECT time_id, fin_category_dim_id, (actual_b - budget_g) AS variance FROM fii_gl_trend_sum_mv_s_v WHERE budget_version_date = :version_date ORDER BY time_id;
• For hierarchical roll-up by parent: SELECT parent_company_dim_id, parent_cost_center_dim_id, SUM(actual_b) FROM fii_gl_trend_sum_mv_s_v GROUP BY parent_company_dim_id, parent_cost_center_dim_id;

Because the documentation states the view is not implemented in the database, these queries will not execute successfully on such an environment; they serve as reference patterns for environments where the object was deployed.