Search Results sec_g_ytd

Overview

APPS.FII_GL_LOCAL_SNAP_F_S_V is a reporting view in the Oracle E-Business Suite Financials Intelligence (FII) schema. Its name follows the standard FII convention in which the "_S_V" suffix denotes a secured or simplified presentation layer over an underlying snapshot fact table. The view is defined over FII_GL_LOCAL_SNAP_F, the local General Ledger snapshot fact that stores pre-aggregated balances by financial dimension combination. This is not a transactional view; it is a denormalized analytical object intended for consumption by FII dashboards, discoverer workbooks, and custom GL reporting.

The view presents a flattened row per (YEAR_ID, COST_CENTER_ID, COMPANY_ID, FIN_CATEGORY_ID, LEDGER_ID, FUD1_ID, FUD2_ID) combination, exposing periodic, quarter-to-date, month-to-date, quarter-to-date, and year-to-date measures as separate columns. Its relevance to the "sec_g_ytd" search term is direct: SEC_G_YTD is the source column aliased to G_YTD in this view, representing the secured General Ledger year-to-date balance. Because column renaming strips the "SEC_" prefix in the view, users searching for SEC_G_YTD must locate the physical column in FII_GL_LOCAL_SNAP_F and treat G_YTD in the view as its logical equivalent.

Underlying Base Objects

The ETRM metadata documents a single base object: FII_GL_LOCAL_SNAP_F. No other referenced base objects are recorded, which confirms this is a thin projection rather than a join or union. The view performs a one-to-one column mapping — every exposed column corresponds to a column of the same or recognizable name in the base table. No WHERE clause, DISTINCT, GROUP BY, or aggregation is applied. Consequently, row counts and cardinality match the base snapshot table exactly, and row-level security typically applied through FII security views is preserved at the query layer.

Because the view is a pure projection, performance characteristics are dominated by the base table: partitioning on YEAR_ID or LEDGER_ID, index availability on the dimension keys, and gather statistics on FII_GL_LOCAL_SNAP_F. The view adds no cost beyond the base table scan.

Key Columns

• YEAR_ID, LEDGER_ID — period and ledger context; these keys determine the accounting calendar and set of books under which the snapshot was generated.
• COMPANY_ID, COST_CENTER_ID, FIN_CATEGORY_ID, FUD1_ID, FUD2_ID — financial dimension identifiers corresponding to balancing segment, cost center, and financial category, plus two user-defined dimensions. FUD1_ID and FUD2_ID are the view aliases of USER_DIM1_ID and USER_DIM2_ID.
• FIN_CAT_TYPE_CODE, AMOUNT_TYPE_CODE — disambiguate the category type and the amount basis (for example, actual versus budget) within the snapshot.
• G_MONTH1 … G_MONTH13, G_QTR1 … G_QTR4, G_YEAR — period, quarter, and annual General Ledger amounts. The thirteen-month column supports period 13 adjustments.
• G_MTD, G_QTD, G_YTD — month-to-date, quarter-to-date, and year-to-date General Ledger balances. G_YTD derives from SEC_G_YTD, the column identified in the user's search, and represents the cumulative secured GL balance for the fiscal year to date.
• LAST_UPDATE_DATE, LAST_UPDATED_BY, CREATION_DATE, CREATED_BY, LAST_UPDATE_LOGIN — standard WHO audit columns inherited from the base table.

Common Use Cases and Queries

The view supports GL balance reporting where year-to-date figures are required alongside period and quarter movements. A typical query retrieving secured YTD balances by company and cost center is:

• SELECT company_id, cost_center_id, year_id, G_YTD FROM apps.fii_gl_local_snap_f_s_v WHERE year_id = :year_id AND ledger_id = :ledger_id ORDER BY company_id, cost_center_id;
• SELECT fin_category_id, SUM(G_YTD) ytd_total, SUM(G_QTD) qtd_total, SUM(G_MTD) mtd_total FROM apps.fii_gl_local_snap_f_s_v WHERE year_id = :year_id GROUP BY fin_category_id;
• SELECT G_MONTH1, G_MONTH2, G_QTR1, G_YTD FROM apps.fii_gl_local_snap_f_s_v WHERE company_id = :company AND cost_center_id = :cc AND amount_type_code = 'A';

Because the view exposes G_YTD directly, it eliminates the need to reference the underlying SEC_G_YTD column and provides a stable interface for custom reports and ETRM-style extracts. Joins to dimension views such as FII_GL_COMPANY_V or FII_GL_COST_CENTER_V are common to resolve IDs to descriptive names before presentation.