Search Results fa_fiscal_year_u2




Overview
Explore in AI Chat

Overview

FA.FA_FISCAL_YEAR is a foundational setup and reference table in the Oracle E-Business Suite Fixed Assets (FA) module. It stores the fiscal calendar definitions that Oracle Assets uses to drive depreciation, period-end processing, and financial reporting across one or more asset books. Each row represents a named fiscal year within a given calendar, binding a fiscal year number to a concrete start date, end date, and mid-year convention date.

In Oracle EBS 12.1.1 and 12.2.2 the table is owned by the FA schema and carries the FND Design Data identifier OFA.FA_FISCAL_YEAR. It resides in the APPS_TS_TX_DATA tablespace with a PCT Free of 10, while its unique indexes are held in APPS_TS_TX_IDX. The table is heavily consumed by depreciation engines, period-close routines, and reporting queries.

From a heuristic Data Vault modeling perspective, this object leans toward a hub. The fiscal year is a durable business concept referenced by downstream transactional tables, and the table exposes stable business keys rather than mutable transactional attributes. It serves as a reference point that other facts and satellites join back to.

Key Information Stored

The table contains 26 documented columns. The most operationally significant are:

The declared primary key is FA_FISCAL_YEAR_PK (FISCAL_YEAR, FISCAL_YEAR_NAME). Two additional unique indexes act as business-key candidates: FA_FISCAL_YEAR_U1 (FISCAL_YEAR_NAME, FISCAL_YEAR) — the index named in the user's search — and FA_FISCAL_YEAR_U2 (FISCAL_YEAR_NAME, START_DATE, END_DATE). The U1 index effectively enforces uniqueness of the name-to-number pairing, while U2 guarantees that a fiscal year name cannot map to overlapping date ranges.

Common Use Cases and Queries

Typical scenarios include resolving a book's currently open fiscal year, validating date ranges during period setup, and driving depreciation reporting. Because the table is small and static, full scans are inexpensive.

To retrieve the calendar definition for a specific year, the following pattern applies:

  • SELECT fiscal_year_name, fiscal_year, start_date, end_date, mid_year_date FROM fa.fa_fiscal_year WHERE fiscal_year_name = :name;
  • Joining to books to resolve the active fiscal year: SELECT bc.book_name, fy.fiscal_year_name, fy.start_date, fy.end_date FROM fa.fa_book_controls bc JOIN fa.fa_fiscal_year fy ON bc.current_fiscal_year = fy.fiscal_year;
  • Validating depreciation period boundaries by comparing transaction dates against START_DATE and END_DATE.
  • Reporting the DFF attributes by filtering on ATTRIBUTE_CATEGORY_CODE.

Related Objects

The principal referential relationship flows into this hub from the book controls table:

  • FA.FA_BOOK_CONTROLS – References FA_FISCAL_YEAR through the foreign key CURRENT_FISCAL_YEAR, which points to FA.FA_FISCAL_YEAR.FISCAL_YEAR. This link identifies the fiscal year currently open for each asset book.
  • FA.FA_DEPRN_PERIODS – Period definitions align with fiscal year boundaries and are commonly joined when reconciling periods to years.
  • FA.FA_BOOK_CONTROLS (repeated via the period relationship) and the APPS.FA_FISCAL_YEAR synonym expose the same calendar to application-level SQL in the APPS schema.

No other database objects reference FA.FA_FISCAL_YEAR through declared foreign keys, and the table itself references no other object, confirming its role as a stable reference hub at the top of the Fixed Assets dependency chain.