Search Results user_dim2_id




Overview
Explore in AI Chat

Overview

FII_GL_BASE_MAP_MV_S_V is a secured (row-level security enabled) view owned by the APPS schema in Oracle E-Business Suite releases 12.1.1 and 12.2.2. It belongs to the FII – Financial Intelligence product, the component within Oracle EBS that supplies the dimensional staging layer for financial reporting, budgeting, and forecasting. The view exposes General Ledger balance data already mapped to the FII analytic dimensions — time, period type, ledger, budget version, financial category, company, cost center, and two user-defined dimensions — together with the raw measure columns ACTUAL_B, SEC_ACTUAL_G, SEC_BUDGET_G, and SEC_FORECAST_G. Because the underlying object is a materialized view, the FII_GL_BASE_MAP_MV_S_V presents precomputed, pre-aggregated balances rather than querying the GL interface tables directly, which gives reporting and extraction processes a consistent, high-performance read point.

The "_S_" naming convention denotes that this is the security-applied form of the base object FII_GL_BASE_MAP_MV. Application of Oracle row-level security means users see only the ledger, company, and cost center combinations authorized for their FII responsibility, a critical control when financial intelligence data is exposed to distributed business users.

Underlying Base Objects

The view text documents a single referenced base object: FII_GL_BASE_MAP_MV, the FII General Ledger base mapping materialized view. The view is a thin projection — it selects a defined column list from that materialized view without joins, unions, or additional filtering logic. Row filtering is applied through the security policies associated with the "_S_V" secured view rather than through SQL predicates in the view definition itself.

The base materialized view is refreshed on the FII program schedule, so data currency in FII_GL_BASE_MAP_MV_S_V is governed by the most recent successful refresh of FII_GL_BASE_MAP_MV, typically driven by a concurrent program or request set in the Financial Intelligence module. Because the view is read-only and declared VALID, no compilation or recompilation of the view is required after standard patching.

Key Columns

  • UMARKER — Internal marker column used by the FII materialized view to track or partition logical record sets.
  • TIME_ID — Foreign key to the FII time dimension; identifies the accounting period or reporting period context.
  • PERIOD_TYPE_ID — Identifies the period type (for example, month, quarter, or year) used to interpret TIME_ID.
  • LEDGER_ID — The GL ledger from which the balances originate.
  • BUDGET_VERSION_DATE — The budget version effective date used to qualify budget amounts.
  • FIN_CATEGORY_ID — Financial category (actual, budget, forecast, or similar classification).
  • COMPANY_DIM_ID / COST_CENTER_DIM_ID — Company and cost center dimension members in the FII model; the reported column aliases COMPANY_ID and COST_CENTER_ID map to these.
  • USER_DIM1_ID / USER_DIM2_ID — Two configurable user-defined dimensions, exposed in the view output as FUD1_ID and FUD2_ID.
  • ACTUAL_B — Actual balance flag or indicator, exposed in the column list as ACTUAL_G as well.
  • SEC_ACTUAL_G / SEC_BUDGET_G / SEC_FORECAST_G — Secured actual, budget, and forecast measure amounts for the dimensional combination.
  • POSTED_DATE — The date on which the underlying GL balance was posted; users searching for "posted_date" will find this column exposed directly by the view and can use it for period cutoff, aging, and reconciliation analysis.

Common Use Cases and Queries

Typical uses include loading an FII reporting fact layer, reconciling FII actuals to GL balances, and extracting budget-versus-actual comparisons filtered by posting date.

Retrieve actual, budget, and forecast measures for a ledger and period:

SELECT ledger_id, time_id, company_id, cost_center_id,
       sec_actual_g, sec_budget_g, sec_forecast_g
FROM   apps.fii_gl_base_map_mv_s_v
WHERE  ledger_id = :ledger_id
AND    time_id = :time_id;

Analyze balances by posting date within a period:

SELECT posted_date, SUM(sec_actual_g) actual_amt
FROM   apps.fii_gl_base_map_mv_s_v
WHERE  ledger_id = :ledger_id
AND    time_id = :time_id
GROUP BY posted_date
ORDER BY posted_date;

Because the view applies FII security, the query returns only the ledgers, companies, and cost centers permitted for the session's FII responsibility, so extraction programs must run under a responsibility with appropriate data access to avoid incomplete results.