Search Results fii_gl_base_map_mv_p_v
Overview
FII_GL_BASE_MAP_MV_P_V is an Oracle E-Business Suite (EBS) reporting view owned by the APPS schema and delivered as part of the Financial Intelligence (FII) product family. It is a presentation-layer view defined over the materialized view FII_GL_BASE_MAP_MV, and its purpose is to expose a flattened, denormalized snapshot of General Ledger balances and transactional amounts keyed by accounting period, ledger, and Financial Intelligence dimension identifiers. In EBS 12.1.1 and 12.2.2 it supports the analytical and extract workloads used by Financial Intelligence dashboards, balances reporting, and downstream data warehouse feeds, providing a stable projection of GL fact data that abstracts the surrogate dimension keys (COMPANY_DIM_ID, COST_CENTER_DIM_ID, USER_DIM1_ID, USER_DIM2_ID) from the FII star schema.
Because the object is a view rather than a table, it carries no storage of its own; all reads are resolved against the underlying materialized view. This makes it inexpensive to expose to reporting tools while retaining the refresh characteristics of the materialized view beneath it.
Underlying Base Objects
The documented view text selects exclusively from FII_GL_BASE_MAP_MV:
- FII_GL_BASE_MAP_MV — the materialized view that physically stores the aggregated GL base map rows. All columns returned by FII_GL_BASE_MAP_MV_P_V originate from this object, with only column renaming applied at the view layer (for example, COMPANY_ID maps to COMPANY_DIM_ID, ACTUAL_G maps to PRIM_ACTUAL_G).
No other base tables are documented as referenced objects. The materialized view itself is populated from the GL balances and FII dimension mapping structures and refreshed according to the FII concurrent program schedule configured for the instance. Understanding this dependency is important: query performance, data freshness, and staleness of the view are all governed by the materialized view refresh cycle, not by the view definition.
Key Columns
The view projects the following columns, several of which are aliased relative to their source names:
- UMARKER — a marker column used by FII processing to identify or partition rows.
- TIME_ID, PERIOD_TYPE_ID — accounting time and period type keys used to place amounts into the correct GL period.
- LEDGER_ID — the ledger to which the balances belong; essential for multi-ledger and multi-organization reporting.
- BUDGET_VERSION_DATE — identifies the budget version applicable to budget-denominated rows.
- FIN_CATEGORY_ID — the Financial Intelligence category dimension.
- COMPANY_DIM_ID, COST_CENTER_DIM_ID, USER_DIM1_ID, USER_DIM2_ID — dimension surrogate keys for company, cost center, and the two user-defined dimensions.
- ACTUAL_B — the actual balance indicator.
- PRIM_ACTUAL_G, PRIM_BUDGET_G, PRIM_FORECAST_G — primary actual, budget, and forecast amounts.
- COMMITTED_AMOUNT_PRIM, OBLIGATED_AMOUNT_PRIM, OTHER_AMOUNT_PRIM, BASELINE_AMOUNT_PRIM — commitment, obligation, other, and baseline budget amounts.
- POSTED_DATE — the GL posting date associated with the row, useful for period-cutoff and audit reporting.
Common Use Cases and Queries
Typical usage centers on extracting period balances by ledger and dimension for reconciliation, budgeting, or feeding a reporting layer.
- Ledger-period extract: SELECT LEDGER_ID, TIME_ID, PRIM_ACTUAL_G, PRIM_BUDGET_G FROM APPS.FII_GL_BASE_MAP_MV_P_V WHERE LEDGER_ID = :ledger AND TIME_ID = :period;
- Dimension analysis: aggregating PRIM_ACTUAL_G by COMPANY_DIM_ID and COST_CENTER_DIM_ID to produce company/cost-center rollups.
- Budget versus forecast comparison: selecting PRIM_BUDGET_G and PRIM_FORECAST_G side by side for variance reporting.
- Commitment and obligation tracking: filtering rows where COMMITTED_AMOUNT_PRIM or OBLIGATED_AMOUNT_PRIM is non-zero.
- Posting-date audit: using POSTED_DATE to isolate transactions posted within a specified cutoff window.
Because the object is a view over a materialized view, queries should be scheduled with awareness of the refresh window to avoid reading stale balances.
-
View: FII_GL_BASE_MAP_MV_P_V
12.1.1
owner:APPS, object_type:VIEW, fnd_design_data:FII.FII_GL_BASE_MAP_MV_P_V, object_name:FII_GL_BASE_MAP_MV_P_V, status:VALID, product: FII - Financial Intelligence , implementation_dba_data: APPS.FII_GL_BASE_MAP_MV_P_V ,
-
View: FII_GL_BASE_MAP_MV_P_V
12.2.2
product: FII - Financial Intelligence (Obsolete) , implementation_dba_data: Not implemented in this database ,
-
VIEW: APPS.FII_GL_BASE_MAP_MV_P_V
12.1.1
owner:APPS, object_type:VIEW, fnd_design_data:FII.FII_GL_BASE_MAP_MV_P_V, object_name:FII_GL_BASE_MAP_MV_P_V, status:VALID,
-
TABLE: APPS.FII_GL_BASE_MAP_MV
12.1.1
owner:APPS, object_type:TABLE, fnd_design_data:FND.FII_GL_BASE_MAP_MV, object_name:FII_GL_BASE_MAP_MV, status:VALID,
-
12.1.1 DBA Data
12.1.1
-
PACKAGE BODY: APPS.FII_PSI_ENCUM_SUM_PKG
12.1.1
-
12.1.1 FND Design Data
12.1.1
-
12.2.2 FND Design Data
12.2.2
-
APPS.FII_PSI_BUD_SUM_PKG SQL Statements
12.1.1
-
APPS.FII_PSI_FUNDS_AVAIL_SUM_PKG SQL Statements
12.1.1
-
APPS.FII_PSI_ENCUM_SUM_PKG SQL Statements
12.1.1
-
PACKAGE BODY: APPS.FII_PSI_FUNDS_AVAIL_SUM_PKG
12.1.1
-
PACKAGE BODY: APPS.FII_PSI_BUD_SUM_PKG
12.1.1
-
eTRM - FII Tables and Views
12.1.1
description: This table stores the mapping of leaf nodes from pruned dimension to nodes in the child value sets ,
-
12.1.1 DBA Data
12.1.1
-
eTRM - FND Tables and Views
12.1.1
description: No longer used ,
-
eTRM - FII Tables and Views
12.1.1
description: This table stores the mapping of leaf nodes from pruned dimension to nodes in the child value sets ,
-
eTRM - FND Tables and Views
12.1.1
description: No longer used ,