Search Results date_delivery_expected




Overview
Explore in AI Chat

Overview

APPS.OKL_LA_ASSET_DTLS_UV is a reporting and integration view within the Oracle E-Business Suite (EBS) Lease and Finance Management (OKL) module, part of the Enterprise Contracts and Leasing (ETRM) family of applications. In EBS 12.1.1 and 12.2.2, this view consolidates asset-related attributes from contract line tables into a single, denormalized projection that supports lease accounting, residual value analysis, and asset detail inquiries. The view is read-only by definition and exposes data drawn from the OKC contract line base and translation tables joined to the OKL lease-specific line table.

The "_UV" suffix denotes a user view, indicating that it is intended as a query and reporting interface rather than as a transactional data entry object. It is queried by lease accounting routines, asset detail forms, and custom reports that need to correlate contract header line information with lease-specific asset parameters such as residual percentages, residual values, and prescribed asset indicators.

Underlying Base Objects

The view is defined over three documented base objects:

  • OKC_K_LINES_B — the base (non-translated) contract line table, aliased CLEB. It supplies the line identifier (ID), the contract line CLE_ID, the DNZ_CHR_ID (contract header identifier), and EXCEPTION_YN.
  • OKC_K_LINES_TL — the translated contract line table, aliased CLET, filtered to CLET.LANGUAGE = USERENV('LANG') so that returned rows reflect the session language.
  • OKL_K_LINES — the OKL lease line table, aliased KLE, which holds lease-specific asset attributes.

The join predicates are CLEB.ID = CLET.ID and KLE.ID = CLEB.ID, meaning the view emits one row per contract line that has a matching lease line, restricted to the current session language. All three base objects are accessed via synonyms owned by APPS.

Key Columns

  • ID — the contract line identifier, the primary correlation key linking to OKC base tables.
  • CLE_ID — the user-facing contract line identifier.
  • DNZ_CHR_ID — the contract header identifier, used to group lines under a contract.
  • EXCEPTION_YN — a flag indicating whether the line is flagged as an exception during processing.
  • PRESCRIBED_ASSET_YN — the column of primary interest for the search term "prescribed_asset_yn." It indicates whether the asset is a "prescribed" or "non-prescribed" asset. This is significant in US lease accounting, where prescribed assets (e.g., real estate, certain equipment under Tax Reform Act rules) were historically treated as non-qualified for investment tax credit purposes. Lease processing uses this flag when evaluating accounting classification and residual treatment.
  • RESIDUAL_PERCENTAGE, RESIDUAL_VALUE, RESIDUAL_GRNTY_AMOUNT, RESIDUAL_CODE — residual position attributes for the lease line, returned as character strings via TO_CHAR.
  • RE_LEASE_YN — indicates whether the line is part of a re-lease transaction.
  • PREVIOUS_CONTRACT — reference to a prior contract in re-lease or renewal scenarios.
  • RVI_PREMIUM — the residual value insurance premium associated with the lease line.
  • DATE_DELIVERY_EXPECTED, DATE_FUNDING_EXPECTED, EXPECTED_ASSET_COST — expected funding and delivery dates and expected asset cost, all converted to character representation via TO_CHAR.

Common Use Cases and Queries

Typical uses include identifying prescribed assets for lease classification reporting, analyzing residual positions across contracts, and supporting asset detail inquiries by contract header. A representative query for prescribed asset analysis follows:

  • Prescribed asset lookup — SELECT cle_id, prescribed_asset_yn, residual_percentage, residual_value FROM apps.okl_la_asset_dtls_uv WHERE prescribed_asset_yn = 'Y';
  • Contract-level asset detail — SELECT id, dnz_chr_id, prescribed_asset_yn, expected_asset_cost FROM apps.okl_la_asset_dtls_uv WHERE dnz_chr_id = :p_chr_id;
  • Residual and re-lease analysis — SELECT cle_id, re_lease_yn, previous_contract, residual_grnty_amount FROM apps.okl_la_asset_dtls_uv WHERE re_lease_yn = 'Y';

Because date and numeric columns are returned as strings, callers must apply explicit TO_DATE or TO_NUMBER conversions where arithmetic or date comparison is required. The view is subject to the session language filter, so reports intended for multiple languages must be run under the appropriate USERENV('LANG') context.