Results for “fa_books_bas”

AI-generated from documented ETRM metadata — verify critical details on the linked pages.

Overview

FA_FINANCIAL_INQUIRY_COST_V is a seeded Oracle E-Business Suite view owned by the APPS schema and delivered as part of the Oracle Assets (OFA) product family. Its documented description is "Financial Cost History," and it is a VALID object in both the 12.1.1 and 12.2.2 releases. The view serves as the data source behind the Financial Inquiry cost-history functionality in Oracle Assets, exposing the sequence of cost adjustments applied to an asset within a given depreciation book.

The view consolidates transaction header information, book cost balances, depreciation and calendar periods, lookup meanings, and transaction references into a single denormalized result set. Because the view is defined as a UNION ALL of two symmetric SELECT statements, it covers both the corporate book path (using FA_BOOKS) and the reporting/multiple-reporting-currency path (using FA_MC_BOOKS). This makes it suitable for inquiry screens, custom reports, reconciliation extracts, and integration interfaces that need a chronological view of an asset's cost movements.

Underlying Base Objects

The documented base objects referenced by the view are all synonyms in the APPS schema:

• FA_ADDITIONS_B — asset master records; supplies ASSET_NUMBER.
• FA_BOOKS — the corporate book cost balances; the primary driver of the corporate branch.
• FA_BOOKS_BAS — the previous book balance, outer-joined to detect cost changes between transactions.
• FA_MC_BOOKS — multiple reporting currency book balances; drives the UNION ALL branch.
• FA_BOOK_CONTROLS — book definition and depreciation calendar linkage.
• FA_CALENDAR_PERIODS — fiscal calendar periods used to derive the effective period name.
• FA_DEPRN_PERIODS — depreciation periods with open/close dates.
• FA_LOOKUPS — decode table for transaction type meanings (lookup type FAXOLTRX).
• FA_TRANSACTION_HEADERS — transaction header records, including DATE_EFFECTIVE.
• FA_TRX_REFERENCES — cross-reference to source transactions.

The joins link each cost transaction to its asset, book, depreciation period, and transaction header, with a self-referential outer join to the previous book balance to filter out rows where the cost has not changed.

Key Columns

• TRANSACTION_HEADER_ID_IN — identifier of the cost transaction header.
• ASSET_ID / ASSET_NUMBER — asset identifier and user-facing asset number.
• BOOK_TYPE_CODE — depreciation book in which the cost change occurred.
• TRANSACTION_TYPE — decoded meaning of the transaction type (from FAXOLTRX lookups).
• PERIOD_ENTERED — depreciation period in which the transaction was entered.
• PERIOD_EFFECTIVE — calendar period matching the transaction's DATE_EFFECTIVE.
• DATE_EFFECTIVE — the effective date of the cost transaction, central to date_effective searches.
• TRANSACTION_DATE_ENTERED — the date the transaction was entered into the system.
• CURRENT_COST — cost balance resulting from the transaction.
• FISCAL_YEAR — fiscal year associated with the entered period.
• SOB_ID — set of books identifier.
• TRX_REFERENCE_ID / TRX_REFERENCE_TYPE — cross-reference to the originating transaction.

Common Use Cases and Queries

Typical uses include rebuilding the cost history for an asset in a report, reconciling cost adjustments between the corporate book and reporting books, and feeding downstream interfaces. A common query filters by asset number and effective date range:

• SELECT asset_number, book_type_code, transaction_type, period_effective, date_effective, current_cost FROM fa_financial_inquiry_cost_v WHERE asset_number = :asset_number AND date_effective BETWEEN :from_date AND :to_date ORDER BY date_effective;
• SELECT book_type_code, fiscal_year, SUM(current_cost) FROM fa_financial_inquiry_cost_v WHERE sob_id = :sob_id GROUP BY book_type_code, fiscal_year;
• SELECT transaction_type, COUNT(*) FROM fa_financial_inquiry_cost_v WHERE asset_id = :asset_id GROUP BY transaction_type;

Because the view applies the NVL(BKPREV.COST, BK.COST-1) != BK.COST filter, only transactions that actually changed cost are returned, which is generally the desired behavior for cost-history reporting.