Search Results fa_period_maps




Overview

FA_PERIOD_MAPS is a reference (static setup) table in the Oracle Assets (OFA) module, owned by the FA schema. It stores the mapping between fiscal quarters and the corresponding accounting period ranges within a fiscal year, allowing the Budget-To-Actual Report to resolve a quarter into its first and last periods. The table is populated once per fiscal calendar configuration and changes rarely, which makes it a lookup rather than a transactional entity.

The ETRM metadata classifies FA_PERIOD_MAPS with a Data Vault classification of "standalone," with no foreign-key relationships mined from the physical schema. From a modeling perspective, this suggests treating it as a hub-like reference dimension: the single-row-per-period-range structure carries no dependent change history in the documented columns, so it behaves more like a static hub/dimension than a link or satellite. The primary key is FA_PERIOD_MAPS_PK, defined on YEAR_LAST_PERIOD, which is the only documented unique identifier for the table.

Key Information Stored

The documented physical schema (ETRM 12.2.2) contains 10 columns. The most important are:

  • YEAR_LAST_PERIOD — the primary key column (FA_PERIOD_MAPS_PK). It identifies the last accounting period of the fiscal year and anchors the row to a specific fiscal year.
  • YEAR_FIRST_PERIOD — the first accounting period of that fiscal year. Together with YEAR_LAST_PERIOD, it defines the full year range.
  • QUARTER — the fiscal quarter number (for example, 1 through 4) that the row maps.
  • QTR_FIRST_PERIOD — the first accounting period belonging to the quarter identified in QUARTER.
  • QTR_LAST_PERIOD — the last accounting period belonging to that quarter.
  • CREATED_BY, CREATION_DATE — standard WHO columns recording the user and timestamp of row creation.
  • LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN — standard WHO audit columns recording the most recent change and the login that performed it.

YEAR_LAST_PERIOD is the surrogate/business key combination enforced by the primary key. No secondary unique index is documented, so YEAR_LAST_PERIOD is the only guaranteed unique business key candidate. The columns are almost entirely WHO/audit metadata plus the five period-mapping attributes; no descriptive name or code column exists.

Common Use Cases and Queries

The principal consumer is the Budget-To-Actual Report, which must translate a user-selected fiscal quarter into the underlying accounting period range in order to aggregate budget and actual balances. Typical usage patterns include:

  • Resolving a quarter to its period range for a given fiscal year, for example:
    SELECT quarter, qtr_first_period, qtr_last_period
    FROM   fa_period_maps
    WHERE  year_last_period = :year_last_period
    ORDER BY quarter;
  • Determining the first and last periods of an entire fiscal year:
    SELECT year_first_period, year_last_period
    FROM   fa_period_maps
    WHERE  year_last_period = :year_last_period;
  • Driving period-range filters in budget-versus-actual reconciliations by joining the resolved QTR_FIRST_PERIOD and QTR_LAST_PERIOD to FA_DEPRN_PERIODS or to general ledger period tables.
  • Validating fiscal calendar setup after a period or calendar change, by confirming that each quarter maps to contiguous, non-overlapping periods.

Because the table is static, queries are typically simple single-table lookups rather than complex joins; reports cache the values or read them once per run to avoid repeated scans.

Related Objects

The documented relationship data classifies FA_PERIOD_MAPS as standalone, with no foreign keys mined from the physical schema. The following objects are the most significant consumers or companions in practice:

  • Budget-To-Actual Report (OFA reporting component) — the documented primary consumer, which reads the period mapping to bracket quarterly comparisons.
  • FA_DEPRN_PERIODS — the Assets depreciation period table; its PERIOD_NAME and PERIOD_NUM values are the natural join targets for QTR_FIRST_PERIOD, QTR_LAST_PERIOD, YEAR_FIRST_PERIOD, and YEAR_LAST_PERIOD.
  • FA_SYSTEM_CONTROLS — holds the book and fiscal calendar context that determines which period values FA_PERIOD_MAPS rows apply to.
  • FA_BOOK_CONTROLS — defines the depreciation books whose balances the Budget-To-Actual Report aggregates over the mapped periods.
  • FA_ADDITIONS_B / FA_ADJUSTMENTS / FA_DEPRN_SUMMARY — transactional Assets tables whose period-stamped amounts are summarised across the ranges resolved from FA_PERIOD_MAPS.
  • GL_PERIODS / GL_LEDGERS — general ledger period definitions, used when budget and actual figures are reconciled at the GL level for the mapped quarters.

No foreign-key constraints link FA_PERIOD_MAPS to these objects; joins are performed on period-value columns rather than on the primary key, reflecting its role as a standalone reference table.