Results for “date_terminated”

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

Overview

The view OKL_LA_RELEASE_ASSETS_UV is an Oracle E-Business Suite database object owned by the APPS schema and defined within the OKL – Leasing and Finance Management product family. Its documented purpose is to serve as the user interface view underpinning the "re-lease assets" list of values (LOV) page. In operational terms, it exposes the set of assets that have been returned and are eligible to be placed back onto a lease contract, allowing the leasing application to present a filtered, user-friendly selection list during re-lease processing.

The object is a VIEW rather than a base table, meaning it holds no data of its own. It is a read-only construct that joins Asset Management data with Oracle Contracts (OKC) core structures and inventory master data. Because its role is tightly coupled to the OKL re-lease workflow, it is most frequently accessed through the application's forms and OAF pages rather than queried directly by end users. Its validity status is VALID, confirming it compiles against the underlying synonyms in supported releases such as 12.1.1 and 12.2.2.

Underlying Base Objects

The view is defined over a combination of Fixed Assets, Oracle Contracts, inventory, and OKL-specific tables, all referenced through APPS synonyms:

• Fixed Assets: FA_ADDITIONS_B, FA_ADDITIONS_TL, FA_BOOKS, FA_BOOK_CONTROLS, and FA_DEPRN_SUMMARY. These supply asset identification, descriptive text, book assignment, and depreciation context. The presence of FA_DEPRN_SUMMARY indicates the view depends on depreciation records to establish asset cost or net book value indirectly through the OKL_AM_UTIL_PVT package call.
• Oracle Contracts (OKC): OKC_K_HEADERS_B, OKC_K_ITEMS, OKC_K_LINES_B, OKC_K_LINES_TL, OKC_LINE_STYLES_B, OKC_STATUSES_B, and OKC_SUBCLASS_TOP_LINE. These provide the contractual line and item structures that link an asset or inventory item to a lease.
• Inventory: MTL_SYSTEM_ITEMS_TL, supplying item descriptions and organization identifiers.
• OKL-specific: OKL_ASSET_RETURNS_B and the package OKL_AM_UTIL_PVT. The asset returns table is central, as the view filters on asset return records with a re-lease status, and the utilty package computes the net book value of the returned asset.

In the 12.2.2 ETRM metadata the base object list is explicit and confirms that FA_DEPRN_SUMMARY is a documented synonym-level dependency, which is directly relevant to users investigating the relationship between depreciation data and re-lease eligibility.

Key Columns

• ASSET_NUMBER – The human-readable Fixed Assets asset number.
• ASSET_ID – The internal asset identifier derived from the contract item's object reference.
• CURRENT_UNITS – The current units associated with the asset.
• ASSET_DESCRIPTION and ITEM_DESCRIPTION – Descriptive text for the asset and the inventory item respectively.
• INVENTORY_ITEM_ID and ORGANIZATION_ID – Inventory master identifiers for the associated item.
• COST – The net book value, computed via OKL_AM_UTIL_PVT.GET_FA_NBV, tying back to FA_DEPRN_SUMMARY-derived data.
• DATE_TERMINATED – The termination or end date determined from the lease line's end date and termination date, truncated to date precision.

Common Use Cases and Queries

Typical usage includes populating the re-lease LOV, verifying which returned assets remain eligible, and auditing the link between a returned asset and its originating lease line.

SELECT asset_number,
       asset_id,
       asset_description,
       cost,
       date_terminated
  FROM apps.okl_la_release_assets_uv
 WHERE asset_number LIKE :p_asset_num||'%';

A second scenario joins the view to OKL_ASSET_RETURNS_B to confirm return status, while a third aggregates by organization to gauge re-lease inventory. Because the view references FA_DEPRN_SUMMARY and the NBV utility package, any reconciliation against depreciation balances should be performed with awareness of book and period context.