Results for “cost_of_removal”

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

Overview

FA_RETIREMENT_ADJUSTMENTS_V is a reporting view owned by the APPS schema in Oracle E-Business Suite, belonging to the Oracle Assets (OFA) product family. It consolidates the financial adjustments generated when an asset retirement transaction is processed, presenting the two principal retirement-related amounts side by side: the proceeds received on disposal and the cost incurred to remove the asset. The view answers a recurring operational question — commonly searched as cost_of_removal — by exposing the removal cost adjustment alongside the corresponding proceeds of sale for each retirement transaction header.

Because retirement accounting in Oracle Assets is not stored as a single denormalized record, the monetary components of a retirement are written as separate rows in the FA_ADJUSTMENTS table, distinguished by ADJUSTMENT_TYPE. This view performs the pivot implicitly through self-joins, delivering one row per retirement transaction with the components resolved into named columns. It is therefore positioned as a convenience layer for reporting, ad-hoc inquiry, and downstream integration, sparing the consumer from replicating the multi-join logic against the base adjustments table.

Underlying Base Objects

The view is defined over two documented base objects, both referenced through APPS synonyms:

• FA_TRANSACTION_HEADERS — aliased TH, supplying the transaction header identifier, the asset identifier, the book, and the transaction type. This is the driving table of the query and provides the grain of one row per retirement transaction header.
• FA_ADJUSTMENTS — referenced twice via self-joins, aliased POS and COR. The POS instance is restricted to ADJUSTMENT_TYPE = 'PROCEEDS CLR'; the COR instance is restricted to ADJUSTMENT_TYPE = 'REMOVALCOST CLR'.

The join predicate matches on TRANSACTION_HEADER_ID across all three references. Consequently, a transaction header is returned only when both a proceeds-clearing adjustment and a removal-cost-clearing adjustment exist for it; retirements lacking either component are excluded by the inner-join semantics. Both adjustments are drawn from the same asset and book implicitly, since the header carries those attributes.

Key Columns

• TRANSACTION_HEADER_ID — Identifier of the retirement transaction header; the join key and effective primary identifier for a returned row.
• BOOK_TYPE_CODE — The depreciation book in which the retirement was recorded, such as the corporate or tax book.
• ASSET_ID — The retired asset's identifier, used to join to FA_ASSETS for descriptive attributes such as asset number and description.
• TRANSACTION_TYPE_CODE — The retirement transaction type, indicating the nature of the disposal.
• PROCEEDS_OF_SALE — The adjustment amount sourced from the FA_ADJUSTMENTS row of type 'PROCEEDS CLR', representing the proceeds realized on the retirement.
• COST_OF_REMOVAL — The adjustment amount sourced from the FA_ADJUSTMENTS row of type 'REMOVALCOST CLR', representing the cost incurred to remove the asset. This is the column most directly associated with the search term cost_of_removal.

Common Use Cases and Queries

Typical scenarios include reconciliation of retirement gains and losses, analysis of net retirement cost by book, and feeds into fixed asset reporting or data warehouse staging. A basic query returns the retirement economics per asset:

• SELECT transaction_header_id, book_type_code, asset_id, transaction_type_code, proceeds_of_sale, cost_of_removal FROM apps.fa_retirement_adjustments_v;
• Filtering by book: WHERE book_type_code = :book;
• Net position: SELECT asset_id, proceeds_of_sale - cost_of_removal AS net_retirement FROM apps.fa_retirement_adjustments_v;
• Joining to FA_ASSETS on asset_id to obtain asset_number and description for reporting.

Because the view is read-only and built from base tables, standard APPLSYS/APPS security applies. It is intended for inquiry and extraction rather than transactional processing.