Search Results kle_fin




Overview
Explore in AI Chat

Overview

OKL_OR_ASSET_INFO_UV is an APPS-owned database view that presents asset-level financial and descriptive information for lease and contract lines managed within the Oracle E-Business Suite 12.1.1 and 12.2.2 environments, specifically under the ETRM (Enterprise Tax, Lease, and Revenue Management) lease management modules. The suffix "UV" denotes a "User View," a naming convention Oracle commonly applies to views intended for end-user querying and external integration rather than for the internal processing logic of the application. The view consolidates columns drawn from the transactional contract header line tables and the lease-specific line extension table, joining header-level contract data with detail-level asset attributes. Its principal role is to expose a flattened, easily consumable projection of asset information such as asset numbers, descriptions, residual values, delivery and funding expectations, and descriptive (DDF) attributes, so that reporting tools, custom concurrent programs, and inbound/outbound integrations can retrieve this data without reconstructing the multi-table join themselves. Because it is defined over existing synonym-backed base tables, it reflects the transactional state of lease and contract lines at query time.

Underlying Base Objects

The view is defined over three documented base objects, all referenced through APPS synonyms: OKC_K_LINES_B, OKC_K_LINES_TL, and OKL_K_LINES. OKC_K_LINES_B is the base (language-independent) contracts line table; the alias CLEB_FIN in the view text is sourced from this table, supplying columns such as ID, DNZ_CHR_ID, and EXCEPTION_YN. OKC_K_LINES_TL is the translation table that holds language-specific line text, providing the line NAME and ITEM_DESCRIPTION through the alias CLET_FIN. OKL_K_LINES is the lease-specific extension of the contract line, aliased KLE_FIN, and it contributes residual percentage, prescribed asset flag, residual value, re-lease flag, previous contract reference, residual guarantee amount, residual code, RVI premium, expected delivery and funding dates, expected asset cost, and the DFF attribute columns. The join is an equality chain linking cleb_fin.id to clet_fin.id, clet_fin.id to kle_fin.id, and filtering the translation row by USERENV('LANG') so that only the current session language's text is returned.

Key Columns

The view exposes several categories of columns. Identification columns include CLEV_FIN_ID (the line identifier), DNZ_CHR_ID (the contract header/chr identifier), and CLET_FIN.NAME exposed as ASSET_NUMBER along with ITEM_DESCRIPTION. Financial and residual columns include RESIDUAL_PERCENTAGE, RESIDUAL_VALUE, RESIDUAL_GRNTY_AMOUNT, RESIDUAL_CODE, RVI_PREMIUM, and EXPECTED_ASSET_COST. Lifecycle and planning columns include DATE_DELIVERY_EXPECTED, DATE_FUNDING_EXPECTED, PRESCRIBED_ASSET_YN, RE_LEASE_YN, PREVIOUS_CONTRACT, and EXCEPTION_YN. A large set of ATTRIBUTE_CATEGORY and ATTRIBUTE1 through ATTRIBUTE15 columns exposes descriptive flexfield content. The remaining columns in the select list (for example CLEV_MODEL_ID, INVENTORY_ITEM_ID, INVENTORY_ORG_ID, NUMBER_OF_ITEMS, PRICE_UNIT, INVENTORY_ITEM_NAME, CLEV_FA_ID, MODEL_NUMBER, YEAR_BUILT, FA_LOCATION_ID, FA_LOCATION_NAME, MANUFACTURER_NAME, ASSET_KEY_ID, ASSET_KEY_NAME, CLEV_IB_ID, PARTY_SITE_USE_ID, PARTY_SITE_NAME, and ASSET_ID) are projected as TO_CHAR(NULL) placeholders, meaning they are defined structurally but return null in this view definition and are reserved for downstream extension or alternate views. Users searching the term "clet_fin" are referencing the alias applied to OKC_K_LINES_TL, which supplies ASSET_NUMBER and ITEM_DESCRIPTION.

Common Use Cases and Queries

Typical uses include lease asset reporting, residual value analysis, and extracting contract-line asset attributes for integration. A representative query follows:

  • SELECT clev_fin_id, dnz_chr_id, asset_number, item_description, residual_percentage, residual_value FROM apps.okl_or_asset_info_uv WHERE residual_percentage IS NOT NULL;
  • Locating lease lines by contract header: SELECT asset_number, expected_asset_cost, date_funding_expected FROM apps.okl_or_asset_info_uv WHERE dnz_chr_id = :p_chr_id;
  • Reporting prescribed assets: SELECT asset_number, prescribed_asset_yn, re_lease_yn FROM apps.okl_or_asset_info_uv WHERE prescribed_asset_yn = 'Y';
  • Filtering by DFF attribute: SELECT asset_number, attribute1, attribute_category FROM apps.okl_or_asset_info_uv WHERE attribute1 = :p_value;

Because the view performs the language-restricted join internally, developers do not need to add the language predicate themselves, simplifying report and interface logic.