Search Results fabv_depreciations




Overview

FABV_DEPRECIATIONS is a read-only view owned by the APPS schema in Oracle E-Business Suite Assets (OFA). It is documented in ETRM as a retrofitted object, meaning it was introduced or carried forward to preserve compatibility across the 12.1.1 and 12.2.2 code lines. The view presents depreciation detail information at the distribution level, exposing the periodic depreciation amounts, year-to-date balances, cost, reserves, and revaluation-related depreciation figures recorded against each asset distribution.

Its principal role is to provide a simplified, stable projection of the FA_DEPRN_DETAIL table for reporting and integration purposes. Because the view is defined with the WITH READ ONLY clause, it cannot be used for DML and is intended strictly for query access. Report developers, custom concurrent programs, and interface extracts referencing depreciation expense — including the revaluation depreciation expense column surfaced by searches such as "reval_deprn_expense" — can rely on this view as a consistent access point without depending directly on the underlying detail table's full column set.

Underlying Base Objects

The view is defined over a single documented base object: FA_DEPRN_DETAIL, referenced through its APPS synonym. The view text selects from that table and applies no joins, aggregations, or filters, so every row in FABV_DEPRECIATIONS corresponds one-to-one with a row in FA_DEPRN_DETAIL. The WITH READ ONLY qualifier enforces query-only behavior at the database level.

FA_DEPRN_DETAIL stores depreciation and adjusting entries generated by the Depreciation Run process for each asset distribution and accounting period. Because the view inherits this grain, it carries one record per asset, book, period, and distribution combination as recorded in the detail table. Users should note that the view exposes a curated subset of columns rather than the complete FA_DEPRN_DETAIL structure.

Key Columns

  • ASSET_ID — Identifier of the asset to which the depreciation row belongs; joins to FA_ADDITIONS.
  • BOOK_TYPE_CODE — The depreciation book (for example, a corporate or tax book) in which the entry was generated.
  • PERIOD_COUNTER — Identifier of the accounting period; joins to FA_CALENDAR_PERIODS or FA_DEPRN_PERIODS.
  • DISTRIBUTION_ID — Identifier of the asset distribution charged with the depreciation amount.
  • DEPRN_RUN_DATE — Date on which the depreciation run produced the row.
  • DEPRN_AMOUNT — Depreciation expense charged for the period.
  • YTD_DEPRN — Year-to-date depreciation for the asset.
  • DEPRN_RESERVE — Accumulated depreciation reserve; the column list in the metadata also reflects the accumulated depreciation concept.
  • COST — Asset cost basis associated with the distribution.
  • DEPRN_ADJUSTMENT_AMOUNT — Adjustment amount applied to depreciation.
  • REVAL_DEPRN_EXPENSE — Depreciation expense attributable to revaluation, matching the term "reval_deprn_expense" used in the search.
  • REVAL_RESERVE — Revaluation reserve balance.
  • YTD_REVAL_DEPRN_EXPENSE — Year-to-date revaluation depreciation expense.

Common Use Cases and Queries

The view supports depreciation expense reporting, reconciliation of depreciation runs, and extract programs feeding general ledger or external reporting. A typical query lists period depreciation and revaluation depreciation for a book and period:

  • SELECT asset_id, book_type_code, deprn_run_date, deprn_amount, ytd_deprn, reval_deprn_expense, ytd_reval_deprn_expense FROM fabv_depreciations WHERE book_type_code = :p_book AND period_counter = :p_period;
  • SELECT distribution_id, SUM(deprn_amount), SUM(reval_deprn_expense) FROM fabv_depreciations WHERE asset_id = :p_asset GROUP BY distribution_id;
  • SELECT a.asset_number, d.deprn_amount, d.deprn_reserve, d.reval_reserve FROM fabv_depreciations d, fa_additions a WHERE d.asset_id = a.asset_id AND d.book_type_code = :p_book;

Because the view is read-only and unfiltered, performance depends on indexes on FA_DEPRN_DETAIL; query predicates on BOOK_TYPE_CODE, PERIOD_COUNTER, and ASSET_ID are recommended for efficient access.