Search Results fa_calendar_types




Overview
Explore in AI Chat

Overview

FA_CALENDAR_TYPES is a reference table in the Oracle Assets (OFA) module of Oracle E-Business Suite, owned by the FA schema. It stores general calendar information that governs how depreciation and proration periods are structured within the fixed asset application. Each row in this table defines a distinct calendar type—such as a monthly or quarterly depreciation calendar—that can subsequently be assigned to one or more asset books. Because depreciation processing is fundamentally calendar-driven, this table occupies a foundational position in the Assets data model: it is defined once and referenced repeatedly by book definitions and period definitions throughout the asset lifecycle.

From a Data Vault modeling perspective, the mined foreign-key structure classifies this object as hub-leaning. In practical terms, FA_CALENDAR_TYPES acts as a stable business entity whose business key, CALENDAR_TYPE, is referenced by dependent tables rather than being a purely transactional or descriptive record. Its defining attributes change infrequently, reinforcing its role as a durable reference dimension for the Assets module.

Key Information Stored

The physical schema documents 26 columns. Among the most significant are the following:

  • CALENDAR_TYPE — the primary key (FA_CALENDAR_TYPES_PK) and the business-key candidate, also enforced by the unique index FA_CALENDAR_TYPES_U1. It identifies the calendar and is the column referenced by all foreign keys that depend on this table.
  • DESCRIPTION — a descriptive name for the calendar type, used in list-of-values and reporting output.
  • PERIOD_SUFFIX_TYPE — controls the naming suffix applied to generated period names within the calendar.
  • NUMBER_PER_FISCAL_YEAR — the number of accounting periods contained in each fiscal year for the calendar, a key driver of depreciation period generation.
  • FISCAL_YEAR_NAME — the name assigned to the fiscal year associated with the calendar.
  • ATTRIBUTE_CATEGORY_CODE and ATTRIBUTE1 through ATTRIBUTE15 — the standard Oracle EBS descriptive flexfield (DFF) columns, providing extensible, customer-defined attributes for the calendar type.
  • LAST_UPDATE_DATE, LAST_UPDATED_BY, CREATED_BY, CREATION_DATE, LAST_UPDATE_LOGIN — standard audit columns capturing who created and last modified each record and when.

The primary key is a natural business key (CALENDAR_TYPE) rather than a system-generated surrogate, and the unique index confirms it is the single identifying attribute. The remaining columns are descriptive and audit attributes subordinate to that key.

Common Use Cases and Queries

Typical applications include identifying all calendars available for book setup, determining how many periods a fiscal year contains, and validating that period definitions exist for a given calendar before depreciation is run. A common reporting query joins calendar types to books:

  • List all calendar types with their descriptions and period counts: SELECT calendar_type, description, number_per_fiscal_year FROM fa_calendar_types ORDER BY calendar_type;
  • Find books using a specific depreciation calendar: SELECT b.book_name, b.deprn_calendar, b.prorate_calendar FROM fa_book_controls b, fa_calendar_types c WHERE b.deprn_calendar = c.calendar_type AND c.calendar_type = :calendar_type;
  • Confirm periods defined for a calendar: SELECT p.calendar_type, p.period_num, p.start_date, p.end_date FROM fa_calendar_periods p WHERE p.calendar_type = :calendar_type ORDER BY p.period_num;

These patterns support depreciation forecasting, book audits, and period-close validation, all of which depend on a correctly defined calendar structure.

Related Objects

  • FA_CALENDAR_PERIODS — stores the individual accounting periods belonging to each calendar; joined via FA_CALENDAR_PERIODS.CALENDAR_TYPE = FA_CALENDAR_TYPES.CALENDAR_TYPE.
  • FA_BOOK_CONTROLS — the asset book definition table, which references this table twice: through FA_BOOK_CONTROLS.DEPRN_CALENDAR and FA_BOOK_CONTROLS.PRORATE_CALENDAR. This makes it the most significant dependent object, supplying both depreciation and proration calendars per book.
  • FA_BOOK_CONTROLS (proration) — the same table via the PRORATE_CALENDAR foreign key, essential for mid-period proration calculations.
  • FA_CALENDAR_TYPES_PK / FA_CALENDAR_TYPES_U1 — the primary-key constraint and unique index that enforce the CALENDAR_TYPE business key and are referenced by the foreign keys above.

Together these objects form the calendar backbone that drives depreciation scheduling across all asset books in Oracle Assets.