Results for “gain_loss_amount”

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

Overview

OKL_LKE_REQ_ASSET_UV is a supplementary Oracle EBS view owned by the APPS schema within the OKL (Leasing and Finance Management) product family. Its documented purpose is to simplify user interface coding by consolidating retirement and asset-return data from Oracle Assets and Oracle Contracts into a single, denormalized result set. The view supports the Like-Kind Exchange (LKE) retirement workflow, where fixed assets associated with a lease contract are retired and subsequently matched against replacement assets. It exposes retirement attributes such as DATE_RETIRED, PROCEEDS_OF_SALE, and GAIN_LOSS_AMOUNT, and blends them with contract-line and asset-return context so that LKE screens and concurrent programs can retrieve all required fields without issuing multi-table joins directly. Because it references the OKL_LIKE_KIND_EXCHANGE_PVT package, the view also incorporates PL/SQL-derived balances for sale proceeds and deferred gains, ensuring that the displayed values reflect the current exchange treatment rather than raw FA_RETIREMENTS figures alone.

Underlying Base Objects

The view is defined over a join of nine base objects. From Oracle Assets it draws on FA_BOOKS (book assignment, original cost, and transaction status), FA_ADDITIONS_B (asset identity and number), FA_BOOK_CONTROLS (tax book class and effective dating), and FA_RETIREMENTS (retirement date, proceeds, and gain/loss). From Oracle Contracts it uses OKC_K_ITEMS (the OKX_ASSET object reference), OKC_K_LINES_B (the fixed-asset lease line), and OKC_LINE_STYLES_B (restricting to the FIXED_ASSET line style). From OKL it uses OKL_ASSET_RETURNS_ALL_B to filter to like-kind returns and OKL_SYS_ACCT_OPTS to apply the LKE_HOLD_DAYS system option. The OKL_LIKE_KIND_EXCHANGE_PVT package supplies the GET_BALANCE_SALE_PROCEEDS and GET_DEFERRED_GAIN functions referenced in the select list. All tables are accessed through APPS synonyms.

Key Columns

• REQ_ASSET_ID and REQ_ASSET_NUMBER — identifier and display number of the retired asset candidates.
• BOOK_TYPE_CODE — the tax book associated with the FA_BOOKS row.
• ASSET_CATEGORY_ID — the asset category used for accounting classification.
• ORIGINAL_COST — original cost from FA_BOOKS.
• DATE_RETIRED — the retirement date from FA_RETIREMENTS, the primary filter attribute for recent-retirement lookups.
• PROCEEDS_OF_SALE — proceeds recorded on the retirement.
• GAIN_LOSS_AMOUNT — gain or loss recorded on the retirement.
• BALANCE_SALE_PROCEEDS and BALANCE_GAIN_LOSS — package-derived values with a fallback to the raw retirement figures.
• MATCH_AMOUNT — a constant zero placeholder used by the UI for matching logic.

Common Use Cases and Queries

The most common use case, and the one implied by the searched term date_retired, is identifying assets retired within the LKE hold window so they can be matched to replacement assets. The view already restricts to processed retirements in tax books where DATE_RETIRED falls between SYSDATE minus OKL_SYS_ACCT_OPTS.LKE_HOLD_DAYS and SYSDATE, so callers need only add their own asset or contract predicates.

Retrieve recently retired like-kind assets with their proceeds and gains:

SELECT req_asset_id, req_asset_number, book_type_code, original_cost, date_retired, proceeds_of_sale, gain_loss_amount
FROM okl_lke_req_asset_uv;

Locate retirement data for a specific asset:

SELECT req_asset_number, date_retired, balance_sale_proceeds, balance_gain_loss
FROM okl_lke_req_asset_uv
WHERE req_asset_id = :p_asset_id;

Because the view returns APPS-owned rows filtered by hold days, it is typically consumed by LKE setup screens and matching concurrent programs rather than by ad hoc reporting, and it should be treated as read-only reference data.