Results for “reserve_retired”

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

Overview

FA_RETIREMENTS_MRC_V is a reporting view owned by the APPS schema in the Oracle E-Business Suite Oracle Assets (OFA) module. It exposes retirement transaction data from a multi-reporting-currency (MRC) perspective, allowing retirement records to be queried across multiple sets of books. The view is classified as "Retrofitted," indicating it was adapted to conform to the multi-currency architecture introduced with multiple reporting currencies rather than the older MRC-only model.

In EBS 12.1.1 and 12.2.2, the view functions as a filtered access layer over the underlying retirement table. Its defining characteristic is a row-level security predicate driven by the session context: the WHERE clause restricts output to the set of books identified in the client information string. Specifically, the view filters on SET_OF_BOOKS_ID, matching it to the value encoded within USERENV('CLIENT_INFO'). This design ensures that queries against the view return only retirement data for the currently active reporting set of books, supporting both reporting and integration scenarios that must respect the multi-currency book context.

Underlying Base Objects

Per the documented ETRM metadata, the view is defined over the synonym FA_MC_RETIREMENTS, which in turn resolves to the FA_MC_RETIREMENTS base object in the APPS schema. The view text selects from FA_MC_RETIREMENTS (aliased FMCR) and projects a comprehensive list of retirement attributes. No joins to other tables are present in the documented definition; the view is a straight projection with a single filter predicate.

The filtering mechanism relies on USERENV('CLIENT_INFO'), extracting a ten-character substring starting at position 45 and converting it to a number. This pattern is the standard EBS MRC mechanism by which the application sets the reporting context. If the client information is not set or cannot be parsed, the NVL fallback of -1 yields no rows, effectively return

ing an empty result set. This behavior is important when troubleshooting integrations that do not initialize the client context correctly.

Key Columns

• SET_OF_BOOKS_ID — Identifies the reporting set of books; the primary filtering column.
• RETIREMENT_ID — Primary identifier for the retirement transaction.
• ASSET_ID — The asset being retired.
• BOOK_TYPE_CODE — The asset book associated with the retirement.
• DATE_RETIRED / DATE_EFFECTIVE — Retirement and accounting effective dates.
• COST_RETIRED, NBV_RETIRED, UNITS — Financial and unit quantities retired.
• PROCEEDS_OF_SALE, COST_OF_REMOVAL, GAIN_LOSS_AMOUNT, GAIN_LOSS_TYPE_CODE — Proceeds, removal costs, and resulting gain or loss details.
• TRADE_IN_ASSET_ID — The asset identifier used when the retirement is structured as a trade-in; central to the searched term.
• RETIREMENT_TYPE_CODE, SOLD_TO, REFERENCE_NUM — Classification and descriptive attributes of the retirement.
• STL_METHOD_CODE, STL_LIFE_IN_MONTHS, STL_DEPRN_AMOUNT — Salvage-to-loss / short-term-life related values.
• REVAL_RESERVE_RETIRED, UNREVALUED_COST_RETIRED, BONUS_RESERVE_RETIRED, RESERVE_RETIRED, EOFY_RESERVE — Reserve balances affected by the retirement.
• ATTRIBUTE1–15, ATTRIBUTE_CATEGORY_CODE — Descriptive flexfield columns for client extensions.

Common Use Cases and Queries

The view is typically used in custom reports and integration extracts that must return retirement data for a specific reporting book, including trade-in scenarios. A representative query is:

SELECT retirement_id, asset_id, trade_in_asset_id, date_retired, cost_retired, proceeds_of_sale, gain_loss_amount FROM apps.fa_retirements_mrc_v WHERE book_type_code = :book;

Because filtering is governed by the MRC client context, callers must ensure the reporting set of books is correctly initialized before executing the query. To locate trade-in retirements specifically, a filter such as WHERE trade_in_asset_id IS NOT NULL is applied. Typical uses include reconciliation of retirement activity, reporting of gains and losses by book, and feeding downstream systems that must respect multi-currency book segregation.