Search Results okl_like_kind_exchange_v




Overview
Explore in AI Chat

Overview

OKL_LIKE_KIND_EXCHANGE_V is an Oracle E-Business Suite (EBS) 12.1.1 / 12.2.2 reporting view owned by the APPS schema and delivered as part of the OKL – Leasing and Finance Management product family. Its stated purpose is to retrieve the data necessary for performing a Like Kind Exchange (LKE) — a U.S. tax-deferred transaction under IRC Section 1031 in which a leased or financed asset is exchanged for a replacement asset of like kind without immediate recognition of gain. For lessors and lessees managing portfolios in Oracle Lease Management, the view consolidates asset-level attributes from Oracle Assets (FA) with contract and line information from Oracle Contracts (OKC) and Oracle Lease Management (OKL). It exists primarily as a read-only data source for LKE reporting, tax processing, and downstream integration, and it does not itself perform the exchange transaction.

Underlying Base Objects

The view is defined over the following documented base objects (all exposed to APPS as synonyms): FA_ADDITIONS_B, FA_ADDITIONS_TL, FA_BOOKS, FA_BOOK_CONTROLS, FA_RETIREMENTS, OKC_K_ITEMS, OKC_K_LINES_B, OKC_LINE_STYLES_B, OKL_ASSET_RETURNS_ALL_B, and OKL_SYS_ACCT_OPTS. The FA tables supply the asset master, descriptive, and depreciation book data; FA_BOOK_CONTROLS provides the book class, organization, and set of books context. OKC_K_ITEMS, OKC_K_LINES_B, and OKC_LINE_STYLES_B link the asset to its contract line and line style, while OKL_ASSET_RETURNS_ALL_B and OKL_SYS_ACCT_OPTS supply lease-specific return and accounting option information. FA_RETIREMENTS contributes retirement cost, units, and net book value (NBV) information relevant to the disposed or exchanged asset. In practice, this means the view is a multi-table join centered on the FA asset and book records, extended by the leasing contract and accounting relationships that identify which assets qualify for LKE treatment.

Key Columns

Columns are drawn from FA_ADDITIONS (aliased FAD), FA_BOOKS (FAB), FA_BOOK_CONTROLS (FBC), the descriptive table (FADTL), and FA_RETIREMENTS (FAR). Identity and classification columns include ASSET_ID, ASSET_NUMBER, TAG_NUMBER, SERIAL_NUMBER, MANUFACTURER_NAME, MODEL_NUMBER, ASSET_TYPE, ASSET_CATEGORY_ID, and ASSET_KEY_CCID. The PARENT_ASSET_ID column — the term the user searched — identifies the parent asset when the record represents a component or subcomponent, enabling reconstruction of asset hierarchies for grouped exchanges. Tax and property attributes include PROPERTY_TYPE_CODE, PROPERTY_1245_1250_CODE, OWNED_LEASED, NEW_USED, IN_USE_FLAG, and INVENTORIAL. Book and depreciation columns include BOOK_TYPE_CODE, BOOK_CLASS, SET_OF_BOOKS_ID, ORG_ID, DATE_PLACED_IN_SERVICE, DEPRN_METHOD_CODE, LIFE_IN_MONTHS, COST, ADJUSTED_COST, ORIGINAL_COST, RECOVERABLE_COST, SALVAGE_VALUE, PERCENT_SALVAGE_VALUE, PRORATE_CONVENTION_CODE, DEPRECIATE_FLAG, BASIC_RATE, ADJUSTED_RATE, BONUS_RULE, CEILING_NAME, PRODUCTION_CAPACITY, UNIT_OF_MEASURE, REVAL_CEILING, UNREVALUED_COST, SHORT_FISCAL_YEAR_FLAG, CONVERSION_DATE, ORIGINAL_DEPRN_START_DATE, and GROUP_ASSET_ID. Retirement columns include COST_RETIRED, UNITS, NBV_RETIRED, and GAIN_LOSS_AMOUNT. LEASE_ID links the asset back to its lease record.

Common Use Cases and Queries

Typical scenarios include identifying assets eligible for LKE treatment, reconciling NBV and gain/loss amounts prior to exchange, and tracing component assets through PARENT_ASSET_ID to their parent asset. A representative query is:

  • SELECT asset_number, tag_number, parent_asset_id, book_type_code, cost, adjusted_cost, nbv_retired, gain_loss_amount FROM apps.okl_like_kind_exchange_v WHERE lease_id = :lease_id ORDER BY asset_number;
  • SELECT asset_id, asset_number, parent_asset_id, property_1245_1250_code, owned_leased, new_used FROM apps.okl_like_kind_exchange_v WHERE parent_asset_id IS NOT NULL;
  • SELECT book_type_code, SUM(adjusted_cost) adjusted_cost, SUM(nbv_retired) nbv_retired FROM apps.okl_like_kind_exchange_v GROUP BY book_type_code;

Because the view joins Oracle Assets and Oracle Contracts data, queries should be filtered by ORG_ID or SET_OF_BOOKS_ID to respect multi-organization security, and results should be validated against the FA and OKC base tables when used for tax reporting.