Search Results expected_asset_cost




Overview
Explore in AI Chat

Overview

OKL_LA_ASSET_DTLS_UV is an APPS-owned database view within the Oracle E-Business Suite Lease and Finance Management (OKL) module. It is documented as the "User Interface view for asset details page," meaning it serves as the data source backing a specific Lease Management application screen where users review and maintain asset-level lease information. In EBS 12.1.1 and 12.2.2, the OKL schema manages lease contracts, contract lines, and the associated financial and asset attributes of leased equipment. This view abstracts the multi-table join required to present that information into a single queryable object.

Because it is a view rather than a base table, OKL_LA_ASSET_DTLS_UV exposes no independently stored data; every query resolves live against the underlying contract line tables. This makes it valuable for reporting and integration scenarios that must reflect current contract data without the complexity of reconstructing the join logic. The metadata confirms Status: VALID, indicating the object is compiled and available in the documented environment.

Underlying Base Objects

The view is defined over three referenced base objects, accessed through synonyms: OKC_K_LINES_B, OKC_K_LINES_TL, and OKL_K_LINES. OKC_K_LINES_B and OKC_K_LINES_TL belong to the Oracle Contracts (OKC) core, where OKC_K_LINES_B holds the base contract line records and OKC_K_LINES_TL holds the translatable (language-specific) line text. OKL_K_LINES is the OKL extension table that stores lease-specific attributes keyed to the same line identifier.

The join condition links all three on the line ID: CLEB.ID = CLET.ID, KLE.ID = CLEB.ID, with CLET.LANGUAGE filtered by USERENV('LANG') to return only the text row matching the session language. This design is characteristic of EBS contract data, where the base and translation tables are kept separate. The view therefore inherits the security and partitioning behaviour of the underlying tables rather than introducing its own.

Key Columns

The view exposes fifteen columns. ID, CLE_ID, and DNZ_CHR_ID are identifiers linking to the contract line, the contract, and the related contract header or character context. EXCEPTION_YN flags exceptions on the line. Several columns concern residual value handling, which is central to lease accounting:

Common Use Cases and Queries

The primary use case is reporting on lease asset residual terms. A typical query retrieves residual details for contract lines:

  • Listing all lines with a specific residual code: SELECT ID, CLE_ID, RESIDUAL_CODE, RESIDUAL_PERCENTAGE, RESIDUAL_VALUE FROM OKL_LA_ASSET_DTLS_UV WHERE RESIDUAL_CODE = :code;
  • Auditing guaranteed residual amounts: SELECT PREVIOUS_CONTRACT, RESIDUAL_GRNTY_AMOUNT FROM OKL_LA_ASSET_DTLS_UV WHERE RESIDUAL_GRNTY_AMOUNT IS NOT NULL;
  • Identifying re-leased assets: SELECT CLE_ID, RE_LEASE_YN, PREVIOUS_CONTRACT FROM OKL_LA_ASSET_DTLS_UV WHERE RE_LEASE_YN = 'Y';
  • Tracking expected funding and delivery schedules using DATE_FUNDING_EXPECTED and DATE_DELIVERY_EXPECTED.

Because numeric and date columns are cast to character, report filters and joins on those columns require explicit conversion. Users should also be aware that results reflect only the row matching the session language in OKC_K_LINES_TL.