Search Results item_cle_id




Overview
Explore in AI Chat

Overview

The view APPS.OKL_K_LINES_ITEMS_UV is a user interface (UI) view within the Oracle E-Business Suite Release 12.1.1 and 12.2.2 environment, owned by the APPS schema and associated with the OKL product family — Oracle Lease and Finance Management. Its documented purpose is to serve as the UI view for linked asset lines, specifically supporting the service and fee line pages presented to end users during contract and lease authoring.

Rather than storing data, the view flattens and renames columns drawn from the underlying contract and lease line tables so that Oracle Forms and OAF-based pages can bind a single, stable row source. It joins contract line information to line style information, lease-specific line attributes, and the item (asset) rows attached to each line, presenting a denormalized result set keyed primarily by the contract line identifier. Because it is a UI view, its column aliases follow a LINE_, ITEM_, and LS_ prefixing convention that identifies the originating logical entity.

The user search term ls_lty_code corresponds directly to a column exposed by this view: LS_LTY_CODE, derived from OKC_LINE_STYLES_B.LTY_CODE. This column identifies the line style code applied to the line, which is the primary mechanism for classifying service, fee, and other lease line types.

Underlying Base Objects

The view is defined over four documented referenced objects, all exposed to the APPS schema as synonyms:

  • OKC_K_LINES_B — the contract/lease line base table, aliased CLE, supplying the core line attributes such as status, currency, line number, start and end dates, negotiated price, and line style reference.
  • OKC_LINE_STYLES_B — the line style base table, aliased LSE, supplying the line style code (LTY_CODE) and line style identifier.
  • OKC_K_ITEMS — the contract line items table, aliased ITEM, supplying the asset/item rows linked to each line.
  • OKL_K_LINES — the OKL lease line extension table, aliased KLE, supplying lease-specific attributes such as the capitalized amount.

The join logic is: LSE.ID = CLE.LSE_ID, KLE.ID = CLE.ID, and ITEM.CLE_ID = CLE.ID combined with ITEM.DNZ_CHR_ID = CLE.DNZ_CHR_ID. This ensures that only lines with a valid line style, a matching OKL lease line extension, and their associated items are returned.

Key Columns

The projected columns fall into four logical groups:

Common Use Cases and Queries

This view is typically queried to list service or fee lines with their attached items, or to resolve the line style code for a given lease line. A representative query filtering on the line style code is:

  • SELECT LINE_ID, LINE_LINE_NUMBER, LS_LTY_CODE, LINE_CAPITAL_AMOUNT, ITEM_ID, ITEM_OBJECT1_ID1, ITEM_UOM_CODE FROM OKL_K_LINES_ITEMS_UV WHERE LS_LTY_CODE = :p_lty_code;
  • Joining to OKC_K_HEADERS_B via LINE_CHR_ID to report service and fee lines for a contract number.
  • Aggregating items per line using ITEM_NUMBER_OF_ITEMS to validate that assets are correctly attached to fee lines.
  • Filtering ITEM_EXCEPTION_YN = 'Y' to surface asset lines flagged with exceptions for review.

Because it is a UI-oriented view derived from base contract tables, it reflects committed data only and should be used for reporting and diagnostic queries rather than as an integration target.