Results for “fy_end_date”

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

Overview

FA_RETIREMENTS_V is a reporting and integration view owned by the APPS schema in Oracle E-Business Suite, belonging to the OFA (Oracle Assets) product family. Its documented description is "Asset Retirement Information." The view consolidates retirement transaction data from the FA_RETIREMENTS base table and enriches it with descriptive attributes drawn from asset, book, transaction header, fiscal year, and history tables. In EBS 12.1.1 and 12.2.2 this view is commonly used by external reporting tools, custom concurrent programs, and integration interfaces that require a denormalized, read-only representation of asset retirements without the overhead of joining multiple base tables manually. Because retirements drive gain/loss calculations, cost of removal, proceeds of sale, and reserve adjustments, the view is a frequent target for reconciliation and audit reporting.

Underlying Base Objects

The view is defined over the following documented referenced objects, all exposed as synonyms in APPS:

• FA_RETIREMENTS — the primary driver table containing retirement header and detail records. The view selects RET.* columns directly from this table.
• FA_ADDITIONS_B and FA_ADDITIONS_TL — provide the asset number and description, including for trade-in assets.
• FA_ASSET_HISTORY — supplies the historical units (CURRENT_UNITS) associated with the asset.
• FA_BOOKS — contributes the book cost context.
• FA_BOOK_CONTROLS — provides the current fiscal year and fiscal year name.
• FA_FISCAL_YEAR — supplies the fiscal year start and end dates.
• FA_TRANSACTION_HEADERS — joins on the transaction header to return the transaction name and descriptive flexfield (DFF) attributes.

The view aliases FA_RETIREMENTS columns with the RET_ prefix to avoid naming collisions with similarly named columns sourced from the joined tables.

Key Columns

Because the user searched for reserve_retired, the most relevant column is REVAL_RESERVE_RETIRED, which represents the revaluation reserve amount retired in the transaction. It sits alongside UNREVALUED_COST_RETIRED and NBV_RETIRED, together capturing the retirement's effect on the reserve and net book value. Other material columns include RETIREMENT_ID and ASSET_ID (primary identifiers), BOOK_TYPE_CODE, DATE_RETIRED and DATE_EFFECTIVE, COST_RETIRED and NBV_RETIRED, COST_OF_REMOVAL, PROCEEDS_OF_SALE, GAIN_LOSS_AMOUNT and GAIN_LOSS_TYPE_CODE, RETIREMENT_TYPE_CODE, ITC_RECAPTURED and ITC_RECAPTURE_ID, REFERENCE_NUM, SOLD_TO, TRADE_IN_ASSET_ID, and the STL_* columns used for short-term (Section 179-style) depreciation recapture. The view also exposes RET.ATTRIBUTE1 through RET.ATTRIBUTE15 and RET.ATTRIBUTE_CATEGORY_CODE for retirement-level DFFs, plus TH.ATTRIBUTE1 through TH.ATTRIBUTE15 and TH.ATTRIBUTE_CATEGORY_CODE for transaction header DFFs. Enrichment columns include ASSET_NUMBER, COST, CURRENT_UNITS, TRADE_IN_ASSET_NUMBER, TRADE_IN_ASSET_DESC, TRANSACTION_NAME, CURRENT_FISCAL_YEAR, FISCAL_YEAR_NAME, FY_START_DATE, and FY_END_DATE.

Common Use Cases and Queries

Typical uses include reconciling retired cost and reserve to the general ledger, validating gain/loss postings, and feeding downstream data warehouses. A representative query filtering on the reserve amount searched is:

• SELECT retirement_id, asset_number, book_type_code, date_retired, cost_retired, nbv_retired, reval_reserve_retired, unrevlaued_cost_retired, gain_loss_amount FROM fa_retirements_v WHERE reval_reserve_retired IS NOT NULL AND book_type_code = :book;
• SELECT asset_number, transaction_name, current_fiscal_year, proceeds_of_sale, sold_to FROM fa_retirements_v WHERE date_retired BETWEEN :start_date AND :end_date;
• SELECT book_type_code, gain_loss_type_code, SUM(gain_loss_amount) FROM fa_retirements_v GROUP BY book_type_code, gain_loss_type_code;

Note: the column name is spelled REVAL_RESERVE_RETIRED in the view definition. Confirm the exact spelling against the installed view text in the target release, as snippets truncate at TH.INVO and the full join predicates should be verified in the database.