Search Results fa_fiscal_year_pk

Overview

FA_FISCAL_YEAR is a reference table in the Oracle Assets (OFA) module of Oracle E-Business Suite, owned by the FA schema. It defines the range of dates associated with every fiscal year recognized by the Assets application, providing the calendar backbone against which depreciation, amortization, and period-based asset reporting are calculated. Each row describes a single fiscal year for a given asset book or set of books context, binding together a numeric year identifier, a descriptive name, and its opening and closing dates. In ETRM 12.2.2 the table is documented as VALID with 26 physical columns.

Heuristic Data Vault classification mined from the foreign key structure identifies this object as hub-leaning. In a Data Vault model this table would most naturally be modeled as a hub capturing the business concept of a fiscal year, with the numeric year and descriptive year name forming the natural business key. It is a low-volatility reference entity, so satellite attributes such as dates and descriptive flexfield values would be carried in a dependent satellite rather than in the hub itself.

Key Information Stored

The most significant attributes stored in FA_FISCAL_YEAR include:

• FISCAL_YEAR — the numeric identifier of the fiscal year (for example, 2024). This column participates in both the primary key and the unique business-key candidates.
• FISCAL_YEAR_NAME — the descriptive label applied to the fiscal year. It also participates in the primary key and the unique indexes.
• START_DATE and END_DATE — the opening and closing dates that bound the fiscal year for depreciation and period purposes. START_DATE and END_DATE participate in unique index FA_FISCAL_YEAR_U2.
• MID_YEAR_DATE — a mid-year reference date sometimes used for prorated depreciation calculations.
• ATTRIBUTE_CATEGORY_CODE and ATTRIBUTE1 through ATTRIBUTE15 — the standard descriptive flexfield (DFF) segment columns that let implementers extend the table without structural change.
• CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN — the standard EBS who-column audit trail.

The primary key is FA_FISCAL_YEAR_PK, defined over (FISCAL_YEAR, FISCAL_YEAR_NAME). Two unique indexes act as business-key candidates: FA_FISCAL_YEAR_U1 (FISCAL_YEAR_NAME, FISCAL_YEAR) and FA_FISCAL_YEAR_U2 (FISCAL_YEAR_NAME, START_DATE, END_DATE). The latter enforces that no two rows share the same name and date span.

Common Use Cases and Queries

The table is most frequently joined to asset book controls to identify the currently open fiscal year for an asset book. A typical reporting query resolves the current year and its date boundaries:

• Listing valid fiscal years for a given range — SELECT FISCAL_YEAR, FISCAL_YEAR_NAME, START_DATE, END_DATE FROM FA.FA_FISCAL_YEAR WHERE FISCAL_YEAR BETWEEN :from_year AND :to_year ORDER BY FISCAL_YEAR;
• Resolving the current fiscal year for a book — SELECT f.FISCAL_YEAR, f.FISCAL_YEAR_NAME, f.START_DATE, f.END_DATE FROM FA.FA_FISCAL_YEAR f, FA.FA_BOOK_CONTROLS b WHERE f.FISCAL_YEAR = b.CURRENT_FISCAL_YEAR;
• Validating date ranges when posting depreciation or adjusting asset periods.
• Driving depreciation projection reports and year-over-year asset roll-forwards.

Because the year range and names are static once defined, the table is commonly cached or extracted into reporting datamarts for period-to-date and year-to-date asset analysis.

Related Objects

The dominant documented relationship is with FA_BOOK_CONTROLS, the table that stores per-book setup and control values. FA_BOOK_CONTROLS.CURRENT_FISCAL_YEAR references FA_FISCAL_YEAR, allowing each asset book to nominate the fiscal year currently being processed; this FK column is the principal join path between the two tables. Downstream, depreciation and period-close processes in Oracle Assets (and reporting views built over them) rely on the year boundaries held here, so FA_FISCAL_YEAR indirectly supports FA_DEPRN_SUMMARY, FA_DEPRN_PERIODS, and related asset transaction tables when period logic is evaluated.