Search Results fa_calendar_types_u1

Overview

FA.FA_CALENDAR_TYPES is a foundational reference table in the Oracle E-Business Suite Fixed Assets (FA) module. It defines the depreciation calendars available to an organization, establishing the fiscal structure — number of periods per fiscal year, period naming conventions, and fiscal year naming — against which asset depreciation is calculated and posted. Because depreciation in Oracle Assets is period-driven, every depreciation book must resolve to a calendar type, and every generated calendar period traces back to the parent calendar definition held here.

The ETRM relationship metadata classifies this object as hub-leaning under a heuristic Data Vault model. This is appropriate: FA_CALENDAR_TYPES carries a stable, naturally unique business key (CALENDAR_TYPE) with relatively few descriptive attributes and serves as the anchor referenced by multiple downstream objects. In Data Vault terms it behaves as a hub, with FA_CALENDAR_PERIODS acting as the satellite holding the time-varying period detail.

Key Information Stored

The table holds 26 columns. The most significant are:

• CALENDAR_TYPE — VARCHAR2(15), the primary key (FA_CALENDAR_TYPES_PK) and the unique business-key candidate enforced by index FA_CALENDAR_TYPES_U1. It is the short code that books and periods reference.
• DESCRIPTION — VARCHAR2(40), the user-facing name of the calendar.
• PERIOD_SUFFIX_TYPE — governs how period names are suffixed (for example, numeric or month-based).
• NUMBER_PER_FISCAL_YEAR — the count of accounting periods in each fiscal year, the core driver of the depreciation schedule.
• FISCAL_YEAR_NAME — VARCHAR2(30), the label applied to the fiscal year.
• LAST_UPDATE_DATE, LAST_UPDATED_BY, CREATION_DATE, CREATED_BY, LAST_UPDATE_LOGIN — standard EBS WHO columns capturing audit and concurrency information.
• ATTRIBUTE_CATEGORY_CODE and ATTRIBUTE1–ATTRIBUTE15 — the standard EBS flexfield/descriptive attribute set for extensibility.

Note that CALENDAR_TYPE is both the primary key and the sole unique index column, so no separate surrogate key exists; the business key and physical key coincide.

Common Use Cases and Queries

The primary practical use is discovering which depreciation calendars exist and their period structure, typically to validate book setup or to drive period-generation logic. A common reporting query joins this table to FA_BOOK_CONTROLS to confirm which calendar each book uses for depreciation and proration:

• Book-to-calendar validation: join FA_BOOK_CONTROLS on DEPRN_CALENDAR and PRORATE_CALENDAR to CALENDAR_TYPE to verify consistent calendar assignment across books.
• Period enumeration: join FA_CALENDAR_PERIODS on CALENDAR_TYPE to list all periods for a given calendar.
• Fiscal structure audit: select CALENDAR_TYPE, NUMBER_PER_FISCAL_YEAR, and FISCAL_YEAR_NAME to confirm the number of periods configured per year.

A representative join pattern: SELECT b.book_type_code, c.calendar_type, c.number_per_fiscal_year FROM fa_book_controls b, fa_calendar_types c WHERE b.deprn_calendar = c.calendar_type;

Related Objects

• FA_BOOK_CONTROLS — references FA_CALENDAR_TYPES twice, via DEPRN_CALENDAR (depreciation calendar) and PRORATE_CALENDAR (proration calendar).
• FA_CALENDAR_PERIODS — the child table holding individual periods, joined on CALENDAR_TYPE.
• FA_CALENDAR_TYPES (APPS synonym) — the APPS-layer synonym exposing the FA table to application code and reports.

Because FA_BOOK_CONTROLS and FA_CALENDAR_PERIODS both depend on this hub, changes to a calendar type propagate into book depreciation behavior and period definitions, making FA_CALENDAR_TYPES a controlled reference object that should be modified only through supported Oracle Assets setup procedures.