Results for “match_amount”

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

Overview

OKL_TRX_ASSETS_LKE_UV is a supplementary database view owned by the APPS schema within the Oracle E-Business Suite Release 12.1.1 / 12.2.2 environment. It belongs to the OKL product family — Oracle Leasing and Finance Management — and is documented as a valid object whose primary purpose is to simplify user interface coding. Rather than embedding complex multi-table joins directly into form or OAF page logic, the view consolidates Like-Kind Exchange (LKE) asset transaction data into a single, denormalized result set that application code can query directly.

The view is specifically oriented around Like-Kind Exchange processing, a tax-driven transaction type in which a relinquished asset is exchanged for a replacement asset, with gain or loss deferred under applicable tax rules. Because the underlying data spans transaction tables, tax asset tables, and Fixed Assets book controls, the view abstracts that complexity into a business-friendly representation. Selecting orig_sale_proceeds — a common search term for this object — retrieves the ORIG_SALE_PROCEEDS column, which surfaces the original proceeds of sale recorded against the relinquished asset in the LKE structure.

Underlying Base Objects

The view is defined over six documented base objects. Three are OKL leasing objects: the OKL_TRX_ASSETS synonym (aliased TRX), the OKL_LIKE_KIND_EXCHANGE_V view (aliased LKE), and the OKL_TXL_ASSETS_B synonym (aliased TXL). Two are Fixed Assets objects: FA_ADDITIONS_B (used twice, aliased FAD1 and FAD2) and FA_BOOK_CONTROLS (aliased FAB). The view also calls the OKL_LIKE_KIND_EXCHANGE_PVT package through three PL/SQL functions, which compute match amounts, remaining sale proceeds, and deferred gain or loss at query time.

Joins bind the transaction to its associated LKE asset record on asset ID, link the transaction to the TXL asset table on transaction ID, and resolve replacement and LKE asset descriptions through separate FA_ADDITIONS_B instances on replacement asset ID and LKE asset ID respectively. The final predicate restricts results to tax books by matching the LKE book type to FA_BOOK_CONTROLS.BOOK_TYPE_CODE and filtering on BOOK_CLASS = 'TAX'.

Key Columns

• RELINQUISHED_ASSET_ID / RELINQUISHED_ASSET_NUMBER — Identifies the asset being given up in the exchange, derived from TRX.REQ_ASSET_ID and the LKE asset number.
• ASSET_CATEGORY_ID / BOOK_TYPE_CODE — The asset category and the tax book context for the exchange.
• ORIG_SALE_PROCEEDS — Mapped from LKE.PROCEEDS_OF_SALE; the original sale proceeds recorded for the relinquished asset. This is the column returned when users search for orig_sale_proceeds.
• ORIG_GAIN_LOSS — Mapped from LKE.GAIN_LOSS_AMOUNT; the original gain or loss on the transaction.
• TOTAL_MATCH_AMOUNT, BALANCE_SALE_PROCEEDS, BALANCE_GAIN_LOSS — Computed at runtime through OKL_LIKE_KIND_EXCHANGE_PVT, providing matched totals and remaining balances.
• REPLACEMENT_ASSET_NUMBER / LKE_ASSET_NUMBER / MATCH_AMOUNT — Identify the replacement asset, the LKE asset, and the matched amount from the TXL asset table.
• TRANSACTION_DATE — The date the transaction occurred, from TRX.DATE_TRANS_OCCURRED.

Common Use Cases and Queries

The view is typically queried to support LKE transaction inquiry screens, tax reporting extracts, and reconciliation of deferred gain balances. A representative query retrieving original sale proceeds and deferred balances for a given transaction is:

SELECT relinquished_asset_number,
       book_type_code,
       orig_sale_proceeds,
       orig_gain_loss,
       balance_sale_proceeds,
       balance_gain_loss
FROM   apps.okl_trx_assets_lke_uv
WHERE  relinquished_asset_id = :req_asset_id;

Because the balance columns invoke packaged functions, performance-sensitive reporting should filter on the asset ID or transaction date before invoking the computed columns. The view remains the preferred access path for UI development because it encapsulates the LKE join logic and tax-book restriction, ensuring consistent results across forms, OAF pages, and downstream reports.