Search Results okl_k_lines_v




Overview
Explore in AI Chat

Overview

OKL_K_LINES_V is an APPS-owned view in the Oracle Lease Management (OKL) module, a component of Oracle E-Business Suite 12.1.1 and 12.2.2. It serves as the lease-specific shadow view for the Oracle Contracts Core line tables OKC_K_LINES_B and OKC_K_LINES_TL. Where the standard Contracts Core tables store the base contract line structure common to all contract types, OKL_K_LINES_V exposes the additional attributes that apply specifically to contracts originated in Oracle Lease Management and that do not fit within the standard OKC line model. The view is documented as VALID and carries a one-to-one relationship with its underlying shadow table, making it the primary reporting and integration surface for lease-line-level detail.

Because the view joins the lease extension attributes to the contract line identity columns (ID, ROW_ID, OBJECT_VERSION_NUMBER), it allows reporting tools, concurrent programs, and external integrations to retrieve leasing-specific line data without querying the shadow table directly. This is particularly relevant for users searching on attributes such as delivered_date, which exists only in the OKL extension layer, not in the standard OKC line tables.

Underlying Base Objects

Per the ETRM metadata, OKL_K_LINES_V is defined over the base object OKL_K_LINES, accessed through a SYNONYM owned by APPS. OKL_K_LINES is the physical shadow table into which Oracle Lease Management stores attributes that extend the Oracle Contracts Core line tables OKC_K_LINES_B (the base line table) and OKC_K_LINES_TL (the translation table). The view text selects exclusively from this shadow table (aliased KLE), projecting the ROWID as ROW_ID and exposing each stored attribute column. No additional joins to OKC_K_LINES_B or OKC_K_LINES_TL are present in the documented view text; the linkage to Contracts Core is conceptual, achieved through the shared line identifier used by the OKL application layer. Consequently, the view functions as the canonical read interface for lease line extensions.

Key Columns

Common Use Cases and Queries

Typical scenarios include asset delivery tracking, residual-value and remarketing analysis, and integration feeds that must surface lease-specific line attributes to downstream systems. A representative query filtering on the searched attribute is:

  • SELECT kle_id, id, delivered_date, estimated_oec, lrv_amount FROM okl_k_lines_v WHERE delivered_date BETWEEN :p_from AND :p_to;
  • SELECT id, title_date, date_sold, date_remarketed FROM okl_k_lines_v WHERE kLE_id = :p_kle_id;
  • SELECT year_built, year_of_manufacture, occupancy, gross_square_footage FROM okl_k_lines_v WHERE prescribed_asset_yn = 'Y';

Because the view derives from a single shadow table, queries are efficient and free of join overhead, making it suitable for high-volume extracts and reporting applications.