Search Results g_month1

Overview

FII_GL_LOCAL_SNAP_F_S_V is a reporting view owned by the APPS schema in Oracle E-Business Suite, classified under the FII (Financial Intelligence) product family. It is a thin projection layer defined over the FII_GL_LOCAL_SNAP_F base table, exposing general ledger period-balance snapshot data in a denormalized form suitable for analytic and reporting consumption. The view preserves all source columns but renames a small number of them for presentation purposes: the USER_DIM1_ID and USER_DIM2_ID columns from the base table are surfaced as FUD1_ID and FUD2_ID, and the SEC_G_MONTHn, SEC_G_QTRn, SEC_G_YEAR, SEC_G_MTD, SEC_G_QTD and SEC_G_YTD columns are re-projected as G_MONTH1 through G_MONTH13, G_QTR1 through G_QTR4, G_YEAR, G_MTD, G_QTD and G_YTD respectively. Because the transformation is purely a column alias exercise, the view carries no independent business logic and inherits the update characteristics and row granularity of FII_GL_LOCAL_SNAP_F. In a 12.1.1 or 12.2.2 environment the view serves as the canonical read interface for Financial Intelligence snapshot balances, shielding downstream reports, Discoverer workbooks, and custom concurrent programs from the physical naming of the base table.

Underlying Base Objects

The single documented base object is the table FII_GL_LOCAL_SNAP_F. No other referenced objects are documented in the ETRM metadata, and the view text contains no joins, unions, or aggregations. Each row in the view therefore corresponds one-to-one with a row in FII_GL_LOCAL_SNAP_F. The view is declared VALID and resides in the APPS schema alongside its base table, which is consistent with the standard Oracle EBS convention that FII fact-style tables are queried through companion views to provide a stable column interface. The "F_S" suffix in the name follows the FII naming pattern denoting a fact snapshot, while the trailing "_V" confirms the object is a view. The YEAR_ID column, which is the identifier the user searched for, is passed through unchanged from the base table and forms part of the natural grain of the snapshot along with the cost center, company, financial category, user dimensions, ledger, and amount type.

Key Columns

• YEAR_ID — Identifies the fiscal or calendar year to which the snapshot row belongs. This is the primary period key used to scope queries by year and is the column most relevant to the user's search term.
• COST_CENTER_ID, COMPANY_ID, FIN_CATEGORY_ID — Organizational and financial-category dimension keys that define the account structure of the balance.
• FUD1_ID, FUD2_ID — The two user-defined dimension keys, aliased from USER_DIM1_ID and USER_DIM2_ID.
• LEDGER_ID — The ledger against which the snapshot balance was captured, enabling multi-ledger reporting.
• FIN_CAT_TYPE_CODE — Classifies the financial category type of the row.
• G_MONTH1 through G_MONTH13 — Period balance columns for each of the thirteen accounting periods in a fiscal year.
• G_QTR1 through G_QTR4 — Quarterly balance columns.
• G_YEAR, G_MTD, G_QTD, G_YTD — Annual, month-to-date, quarter-to-date, and year-to-date aggregate balances.
• AMOUNT_TYPE_CODE — Distinguishes the measure semantics of the balance, for example actual versus budget.
• LAST_UPDATE_DATE, LAST_UPDATED_BY, CREATION_DATE, CREATED_BY, LAST_UPDATE_LOGIN — Standard EBS WHO columns for audit and change tracking.

Common Use Cases and Queries

The view is typically consumed by financial analysts and report developers who need period-banded balances without performing pivot logic in SQL. A frequent pattern is to filter by YEAR_ID and LEDGER_ID and read the monthly columns directly. For example:

SELECT year_id, ledger_id, cost_center_id, company_id, g_month1, g_month2, g_month3, g_ytd FROM apps.fii_gl_local_snap_f_s_v WHERE year_id = :p_year AND ledger_id = :p_ledger;

Because the grain includes multiple dimension keys, aggregation to a summary level is usually required before presentation:

SELECT year_id, company_id, SUM(g_ytd) ytd_total FROM apps.fii_gl_local_snap_f_s_v WHERE year_id = :p_year GROUP BY year_id, company_id;

Other common scenarios include reconciliation of Financial Intelligence snapshot figures against GL period balances, extraction feeds into a data warehouse where the G_MTD, G_QTD, and G_YTD columns map directly to loading targets, and parameterized concurrent programs that select a specific AMOUNT_TYPE_CODE to separate actual from budget or encumbrance results. When joining, note that FUD1_ID and FUD2_ID are aliased names; any existing code written against the base table's USER_DIM1_ID and USER_DIM2_ID names must be adjusted when switching to this view.