Results for “revaluation_ceiling”

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

Overview

FA_TRANSACTION_HISTORY_BOOKS_V is an APPS-owned reporting view in the Oracle E-Business Suite Fixed Assets (OFA) module. It is classified as a retrofitted object, a designation applied to views restructured during the multi-org and MOAC (Multi-Org Access Control) retrofitting effort so that transaction history can be reported consistently across operating units and asset books. The view consolidates asset book records from FA_BOOKS with their originating and reversing transaction headers from FA_TRANSACTION_HEADERS, enrichment attributes from the asset master tables, and lookup-based transaction type descriptions. It is read-only by design and is intended for inquiry, dashboard, and custom reporting use rather than transactional processing.

A key characteristic of this view is that it is defined with a UNION of two query blocks. The first block keys the row on TRANSACTION_HEADER_ID_IN, exposing the book attributes as they existed on the inbound (original) transaction. The second block keys the row on TRANSACTION_HEADER_ID_OUT, capturing the outbound (reversing or adjusting) transaction. The column KEY reflects whichever transaction header identifier is relevant for that row, allowing a single result set to represent both sides of an asset transaction lifecycle.

Underlying Base Objects

The view's SQL references the following documented base objects, all accessed through APPS synonyms: FA_ADDITIONS_B and FA_ADDITIONS_TL for asset number and description (the latter filtered by USERENV('LANG') for the session language); FA_BOOKS for cost, depreciation, and book attributes; FA_TRANSACTION_HEADERS for transaction name and type; FA_LOOKUPS_B and FA_LOOKUPS_TL for the FAXOLTRX lookup type that resolves transaction type codes into meaningful descriptions; and FND_NUMBER for canonical conversion of the asset life value. The metadata also documents FA_BOOK_CONTROLS and FA_MC_BOOKS as referenced objects, indicating that the view supports both corporate book control attributes and multiple reporting currency (MRC) book records. Group asset information is joined via outer joins to FA_ADDITIONS_B and FA_ADDITIONS_TL aliased as GADB and GADTL, driven by BK.GROUP_ASSET_ID.

Key Columns

• TRANSACTION_HEADER_ID_IN / TRANSACTION_HEADER_ID_OUT — Identifiers of the originating and reversing transaction headers; KEY carries the applicable one for the row.
• ASSET_ID, ASSET_NUMBER — Asset identifier and a concatenation of asset number and description.
• GROUP_ASSET_NUMBER — Concatenation of the parent group asset number and description, derived from GADB and GADTL; this is the column targeted by most searches using that term.
• BOOK_TYPE_CODE — The asset book in which the transaction occurred.
• TRANSACTION_TYPE — Decoded meaning of the transaction type from the FAXOLTRX lookup.
• CURRENT_COST, ORIGINAL_COST, SALVAGE_VALUE, RECOVERABLE_COST, ADJUSTED_RECOVERABLE_COST — Financial attributes of the book record at the time of the transaction.
• DEPRN_METHOD_CODE, LIFE, ADJUSTED_RATE, PRODUCTION_CAPACITY, UNIT_OF_MEASURE — Depreciation method and life; LIFE is computed by truncating LIFE_IN_MONTHS into a years.months value via FND_NUMBER.CANONICAL_TO_NUMBER.
• PRORATE_CONVENTION_CODE, PRORATE_DATE, DATE_PLACED_IN_SERVICE, DEPRECIATE_FLAG, BONUS_RULE — Proration and depreciation start attributes.
• CEILING_NAME, REVALUATION_CEILING — Revaluation ceiling references.
• COMMENTS — Populated from TH.TRANSACTION_NAME.

Common Use Cases and Queries

The primary use case is transaction history reporting that requires the group asset context — for example, identifying all book transactions belonging to assets within a given group asset, or reconciling adjustments and reversals across a book. A typical query filtering on the searched column is:

SELECT asset_number, group_asset_number, book_type_code, transaction_type, current_cost, date_placed_in_service FROM apps.fa_transaction_history_books_v WHERE group_asset_number LIKE 'CORP%' AND book_type_code = 'CORP' ORDER BY asset_number;

Because the outbound block keys on TRANSACTION_HEADER_ID_OUT, analysts can also isolate reversals by comparing KEY against TRANSACTION_HEADER_ID_IN. Additional practical scenarios include auditing depreciation method and life changes over an asset's life, verifying prorate conventions applied at transaction time, and feeding downstream ETL or reconciliation reports where both the asset and its parent group asset must be displayed. Report authors should apply an operating unit or book type filter, since the view returns rows across all books accessible to the session.