Results for “fii_time_year_u1”

AI-generated from documented ETRM metadata — verify critical details on the linked pages.

Overview

FII.FII_TIME_YEAR is a reference (lookup) table in the Oracle E-Business Suite FII schema that defines the set of fiscal or calendar years used by the FII (Financial Intelligence / Enterprise Performance Foundation) time dimension. Each row describes one year through a surrogate identifier, a display name, and an explicit start and end date, together with an optional pointer to the preceding year. In Oracle EBS 12.1.1 and 12.2.2 the table is stored in the APPS_TS_SUMMARY tablespace with a PCTFREE of 10, indicating it is treated as a compact, slowly changing reference object rather than a high-volume transactional table.

Within the EBS data model the table functions as a foundational dimension for time-based analytics, budgeting, forecasting, and period-to-period comparisons performed by the FII/EPF reporting stack. From a Data Vault modeling perspective, the mined FK structure classifies FII_TIME_YEAR as a standalone object. It is best understood as a reference or hub-style entity for the year grain: it carries its own surrogate key, holds descriptive attributes, and does not depend on a parent table, although its YEAR_ID participates in a documented foreign key relationship to JAI_FA_AST_YEARS.

Key Information Stored

The table contains ten documented columns. The most significant are:

• YEAR_ID (NUMBER) — the surrogate primary key and the single unique business-key candidate, enforced by the unique index FII_TIME_YEAR_U1 on APPS_TS_SUMMARY. This is the value joined by all dependent FII objects.
• NAME (VARCHAR2(100)) — the display name of the year, used in user-facing reports and list-of-values queries.
• START_DATE (DATE) — the first day of the year represented by the row.
• END_DATE (DATE) — the last day of the year represented by the row. Together with START_DATE, this defines the date range against which fact records are resolved.
• PRIOR_YEAR_ID (NUMBER) — a self-referencing pointer to the preceding year, enabling year-over-year comparisons and rolling hierarchies without date arithmetic.
• CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN — standard WHO columns that record the audit trail for row creation and maintenance, with CREATED_BY and LAST_UPDATED_BY referencing FND_USER.USER_ID and LAST_UPDATE_LOGIN referencing FND_LOGINS.LOGIN_ID.

The primary key YEAR_ID should not be confused with the human-readable NAME; only YEAR_ID is documented as unique.

Common Use Cases and Queries

The most frequent use is resolving a year identifier to its display name and date boundaries when building FII/EPF reports. A typical lookup joins YEAR_ID from a fact or interface table to this table:

• Populating a year prompt or list of values using NAME ordered by START_DATE.
• Determining whether a transaction date falls within a given year by comparing it to START_DATE and END_DATE.
• Building prior-year comparisons by self-joining on PRIOR_YEAR_ID, for example SELECT c.NAME current_year, p.NAME prior_year FROM FII.FII_TIME_YEAR c, FII.FII_TIME_YEAR p WHERE c.PRIOR_YEAR_ID = p.YEAR_ID.
• Auditing reference data changes through CREATION_DATE, LAST_UPDATE_DATE, and LAST_UPDATED_BY.

As the metadata warns, this object is marked Oracle Internal Use Only and should be accessed only through standard Oracle Applications programs rather than direct SQL in production.

Related Objects

• JAI_FA_AST_YEARS — referenced by FII.FII_TIME_YEAR.YEAR_ID per the documented foreign key, linking FII year definitions to fixed asset year records.
• FND_USER — parent of CREATED_BY and LAST_UPDATED_BY.
• FND_LOGINS — parent of LAST_UPDATE_LOGIN.
• APPS.FII_TIME_YEAR — the APPS synonym through which application code references this table.
• FII fact and dimension objects that store YEAR_ID as a foreign key to FII_TIME_YEAR for time-grain reporting.