Search Results fa_mc_books_summary




Overview

FA_MC_BOOKS_SUMMARY is an Oracle Assets (OFA) table owned by the FA schema. It stores financial and depreciation information at the asset level, and it is the multi-currency (MC) counterpart to the primary FA_BOOKS table. Whereas FA_BOOKS maintains the reporting-currency depreciation ledger, FA_MC_BOOKS_SUMMARY maintains the corresponding converted balances required when an asset is held in a book whose currency differs from the functional or primary ledger currency. Each row represents the state of one asset, in one depreciation book, for one accounting period.

In the documented ETRM 12.2.2 physical schema the table exposes 104 columns, reflecting the breadth of cost, depreciation, revaluation, impairment, bonus, and production data that Assets tracks per asset book. The heuristic Data Vault classification mined from its foreign-key structure is standalone, meaning the model suggests treating this object as neither a pure hub, link, nor satellite in a Data Vault build; it behaves as a self-contained transactional summary keyed on asset and period. The table is status VALID and remains an active, supported dependency of the OFA - Assets product across Oracle EBS 12.1.1 and 12.2.2.

Key Information Stored

The table's unique index, FA_MC_BOOKS_SUMMARY_U1, defines its business-key candidate as the composite of SET_OF_BOOKS_ID, ASSET_ID, BOOK_TYPE_CODE, PERIOD_COUNTER, and TRANSACTION_HEADER_ID_OUT. This composite is the practical access path for one asset's position in one book for one period, following a given transaction.

Among the most significant columns are:

Common Use Cases and Queries

The table is primarily consumed during period close, depreciation processing, and reporting routines that must present asset balances in a currency other than the primary book currency. Typical scenarios include reconciling converted cost and accumulated depreciation to the general ledger, validating multi-currency roll-forward of reserves, and reporting revaluation and impairment in the reporting currency.

A representative query pattern retrieves one asset's current-period converted position:

  • SELECT asset_id, book_type_code, period_counter, cost, adjusted_cost, ytd_deprn, deprn_reserve, reval_reserve FROM fa_mc_books_summary WHERE set_of_books_id = :sobid AND asset_id = :asset_id AND book_type_code = :book AND period_counter = :pc;

Roll-forward and reconciliation reporting groups by period and book:

  • SELECT period_counter, SUM(accounted_deprn) period_expense, SUM(deprn_reserve) reserve FROM ... GROUP BY period_counter;

Join predicates typically align the business key to FA_BOOKS to compare primary-currency and reporting-currency balances for the same asset, book, and period.

Related Objects

The documented foreign keys establish these direct relationships:

  • FA_GROUP_ASSETS — referenced via FA_MC_BOOKS_SUMMARY.GROUP_ASSET_ID → FA_GROUP_ASSETS, linking the summary row to its group asset member context.
  • FA_SUPER_GROUPS — referenced via FA_MC_BOOKS_SUMMARY.SUPER_GROUP_ID → FA_SUPER_GROUPS, tying the row to a super-group construct used in group-asset depreciation.

Closely coupled objects that share the same business key include FA_BOOKS (primary-currency depreciation ledger), FA_ADDITIONS_B and FA_ADDITIONS_TL (asset descriptive data), FA_DEPRN_SUMMARY (depreciation summary), FA_DEPRN_DETAIL, FA_TRANSACTION_HEADERS (referenced through the transaction header identifiers), and FA_BOOK_CONTROLS (book period status). Together these objects support asset-level currency conversion and period-close validation in Oracle Assets.