Search Results fii_time_year




Overview
Explore in AI Chat

Overview

FII_TIME_YEAR is a reference (setup) table in the FII — Financial Intelligence product family of Oracle E-Business Suite, holding the definition of the fiscal or reporting years used by the Financial Intelligence applications. Within the EBS data model it functions as a low-volume, slowly changing dimension that anchors time-based analysis: each row describes a single year, its display name, the calendar boundaries that define it, and a pointer to the immediately preceding year. Because FII components — including the Financial Statement Generator (FSG), Financial Analyzer, and the reconciliation and consolidation engines — reason about periods and comparative columns, a clean, contiguous definition of years is a prerequisite for correct period-over-period reporting.

The documented physical schema for release 12.1.1 shows the table owned by the FII schema with ten columns and a single unique index, FII_TIME_YEAR_U1, defined on YEAR_ID. Heuristic Data Vault classification mined from the foreign-key structure marks this object as standalone. In Data Vault terms it would therefore be modeled as a hub (or, if treated as a pure code/reference list, a small reference satellite), since it carries its own business key and depends on no parent entity. Note that although the FK metadata records a reference from FII_TIME_YEAR.YEAR_ID to JAI_FA_AST_YEARS, the uniqueness of YEAR_ID and the descriptive content of the other columns are consistent with FII_TIME_YEAR acting as the source of truth for year definitions rather than as a dependent child.

Key Information Stored

Ten columns are documented. The most significant are:

  • YEAR_ID — the surrogate primary key and the only business-key candidate, enforced by unique index FII_TIME_YEAR_U1. All child tables and FII reporting logic join on this value.
  • NAME — the human-readable year label (for example the fiscal year designation) presented in reports and list-of-values.
  • START_DATE and END_DATE — the inclusive calendar boundaries of the year. These drive date-range filtering, period mapping, and the determination of whether a transaction falls inside a given reporting year.
  • PRIOR_YEAR_ID — a self-referencing pointer to the previous year's YEAR_ID. This is the mechanism by which the table supports comparative reporting and rolling analysis without hard-coding year sequences.
  • CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN — the standard EBS who-column audit set, used for change tracking, data-pump validation, and audit reporting.

The combination of START_DATE, END_DATE, and PRIOR_YEAR_ID distinguishes this table from a trivial lookup: it encodes an ordered chronology, so integrity of these three columns is essential.

Common Use Cases and Queries

Typical scenarios include resolving a year label from an identifier, listing all defined years in sequence, and joining year boundaries to transactional data to assign a reporting year.

  • Year lookup: SELECT name, start_date, end_date FROM fii.fii_time_year WHERE year_id = :p_year_id;
  • Chronological listing: SELECT year_id, name, start_date, end_date FROM fii.fii_time_year ORDER BY start_date;
  • Comparative (prior-year) reporting: SELECT c.year_id, c.name, p.name AS prior_name FROM fii.fii_time_year c, fii.fii_time_year p WHERE c.prior_year_id = p.year_id;
  • Mapping a transaction date to its year: SELECT y.year_id, y.name FROM fii.fii_time_year y WHERE :txn_date BETWEEN y.start_date AND y.end_date;

Reporting use cases center on FSG and Financial Intelligence dashboards that require year-to-date and prior-year comparative columns, and on reconciliation processes that must determine whether a balance snapshot belongs to the current fiscal year. A common data-quality check is to verify chronological continuity — every year except the earliest should have a PRIOR_YEAR_ID pointing to a row whose END_DATE immediately precedes its START_DATE.

Related Objects

The FK metadata documents one outbound reference from FII_TIME_YEAR.YEAR_ID to JAI_FA_AST_YEARS, tying FII year definitions to the Oracle Assets year table used by the JAI (India Localization) asset components. Significant related objects include:

  • JAI_FA_AST_YEARS — joined on YEAR_ID; supplies the asset-side year context.
  • FII_TIME_PERIOD (and other FII time/period reference tables) — period definitions that roll up to a YEAR_ID via the same key.
  • FII_TIME_YEAR_U1 — the unique index enforcing the YEAR_ID business key.
  • FII reporting views and FSG report definitions — consume YEAR_ID, NAME, START_DATE, and END_DATE for column and row set generation.
  • FII balance, reconciliation, and consolidation fact tables — reference YEAR_ID when storing or aggregating period results by year.

Because the object is classified as standalone, it is best treated as a reference dimension: load it first during implementations and data migrations, then validate uniqueness on YEAR_ID and the integrity of the PRIOR_YEAR_ID chain before dependent FII objects are populated.