Search Results prim_g_month13

Overview

APPS.FII_GL_LOCAL_SNAP_F_P_V is a public synonym view owned by the APPS schema in Oracle E-Business Suite Release 12.1.1 and 12.2.2. It belongs to the Financial Intelligence (FII) product family and is registered under FND Design Data as FII.FII_GL_LOCAL_SNAP_F_P_V. The view exposes General Ledger snapshot fact data in a denormalized, period-oriented layout, presenting pre-aggregated balances across monthly, quarterly, and year-to-date dimensions alongside a set of general-ledger dimension identifiers. Its role is to serve as a stable reporting and integration surface over the FII GL local snapshot fact table, allowing external queries, analytic tools, and FII internal programs to read snapshot amounts without directly accessing the underlying fact table.

The "_P_V" suffix indicates a documented public view, while the "LOCAL_SNAP" naming reflects that the data is derived from locally stored snapshot fact records. The view metadata carries the standard Oracle warning that the object is for Oracle Internal Use Only and is not supported for direct customer access except from standard Oracle Applications programs. Any direct querying should therefore be treated as read-only and understood to be outside Oracle's support boundary.

Underlying Base Objects

The documented dependency list is explicit and minimal: APPS.FII_GL_LOCAL_SNAP_F_P_V references APPS.FII_GL_LOCAL_SNAP_F. That base table is the GL local snapshot fact table in the FII schema, and it is the sole documented underlying object. The view does not introduce joins to other tables; it projects and renames the fact columns into the analytical layout described below.

The metadata further states that this view is not referenced by any database object. In other words, it sits at the top of its dependency chain — nothing in the documented ETRM dependency graph depends on it, so it functions purely as a terminal read interface for external consumers rather than as an intermediate object in a larger view hierarchy. Because the underlying fact table is the only documented base object, any change to the structure or population of FII_GL_LOCAL_SNAP_F directly affects the shape and content of this view.

Key Columns

The view exposes a set of dimension identifiers, a period balance matrix, audit columns, and an amount classification code:

• Dimension keys: YEAR_ID, COST_CENTER_ID, COMPANY_ID, FIN_CATEGORY_ID, FUD1_ID, FUD2_ID, and LEDGER_ID are NUMBER(15) identifiers that establish the analytical grain of each snapshot row. LEDGER_ID ties the row to a specific ledger, while FUD1_ID and FUD2_ID correspond to flexfield usage dimension slots.
• Classification: FIN_CAT_TYPE_CODE (VARCHAR2(30)) classifies the financial category type, and AMOUNT_TYPE_CODE indicates the amount type represented by the row.
• Monthly balances: G_MONTH1 through G_MONTH13 are NUMBER columns holding period balances; the thirteenth slot accommodates the thirteenth accounting period used for adjustments in Oracle GL.
• Quarterly balances: G_QTR1 through G_QTR4 aggregate the monthly values into four fiscal quarters. This is the group referenced by the search term "g_qtr1," a quarterly balance column often cited when building period comparison or trend reports.
• Aggregate totals: G_YEAR holds the full-year balance, while G_MTD, G_QTD, and G_YTD provide month-to-date, quarter-to-date, and year-to-date rollups respectively.
• Audit columns: LAST_UPDATE_DATE, LAST_UPDATED_BY, CREATION_DATE, CREATED_BY, and LAST_UPDATE_LOGIN follow the standard Oracle Applications who-column convention.

Common Use Cases and Queries

The primary use case is reporting and analysis of GL snapshot balances by ledger, company, cost center, and financial category across time periods. A typical query selects a specific ledger and year and compares quarterly performance:

• Quarterly analysis: SELECT LEDGER_ID, YEAR_ID, G_QTR1, G_QTR2, G_QTR3, G_QTR4, G_YEAR FROM APPS.FII_GL_LOCAL_SNAP_F_P_V WHERE YEAR_ID = :year_id AND LEDGER_ID = :ledger_id;
• Year-to-date extraction: SELECT COMPANY_ID, COST_CENTER_ID, G_YTD, AMOUNT_TYPE_CODE FROM APPS.FII_GL_LOCAL_SNAP_F_P_V WHERE FIN_CAT_TYPE_CODE = :cat_type AND YEAR_ID = :year_id;
• Monthly trend: selecting G_MONTH1 through G_MONTH13 for a given dimension combination to build a month-by-month trend line.

Because the object is documented as Oracle Internal Use Only and is not referenced by other database objects, these queries should be used for read-only analytical and integration purposes, with awareness that the view is not supported for direct customer access except through standard Oracle Applications programs.