Search Results item_uom_code




Overview
Explore in AI Chat

Overview

APPS.OKL_K_LINES_ITEMS_UV is a reporting and integration view in Oracle EBS that joins contract line information with the individual items attached to those lines within the Oracle Lease and Finance Management (OKL) and Oracle Contracts (OKC) data model. The view presents a flattened, denormalized projection that combines line-level attributes from OKC_K_LINES_B with item-level attributes from OKC_K_ITEMS, enriched by line style and lease-specific line data. Its primary purpose is to expose item details — including unit of measure, quantities, capital amounts, and object identifiers — alongside the contract line context needed for downstream reporting, extracts, and interface programs.

The view is particularly relevant to users searching on item_uom_code, since the underlying OKC_K_ITEMS.UOM_CODE column is exposed through the view as ITEM_UOM_CODE, allowing the unit of measure assigned to each contract item to be queried in a single select without additional joins.

Underlying Base Objects

The view is defined over four documented base objects, all referenced through APPS synonyms:

  • OKC_K_LINES_B — the contract line header table, aliased CLE.
  • OKC_K_ITEMS — the contract line items table, aliased ITEM.
  • OKC_LINE_STYLES_B — the line style definitions, aliased LSE.
  • OKL_K_LINES — the lease-specific line extension table, aliased KLE.

Joins are driven by 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. The DNZ_CHR_ID predicate is significant in the EBS contracts schema: it correlates the item and line to the same effective-dated change request context, ensuring that items are returned for the correct version of the line rather than across all historical revisions.

Key Columns

The view exposes two logical column groups. The line-level columns carry the LINE_ prefix and include LINE_ID, LINE_CLE_ID, LINE_STS_CODE, LINE_CURRENCY_CODE, LINE_NUMBER, LINE_LSE_ID, LINE_START_DATE, LINE_END_DATE, LINE_PRICE_NEGOTIATED, LINE_DNZ_CHR_ID, and LINE_CHR_ID. LINE_CAPITAL_AMOUNT is sourced from OKL_K_LINES and is specific to lease lines.

The item-level columns carry the ITEM_ prefix and include ITEM_ID, ITEM_CLE_ID, ITEM_OBJECT1_ID1 and ITEM_OBJECT1_ID2 (the flexible object identifier pair, typically referencing inventory item and organization), ITEM_JTOT_OBJECT1_CODE, ITEM_UOM_CODE, ITEM_EXCEPTION_YN, ITEM_NUMBER_OF_ITEMS, ITEM_CHR_ID, and ITEM_DNZ_CHR_ID. A literal space is projected as ITEM_NAME, meaning the item description is not resolved by this view and must be obtained separately, for example from MTL_SYSTEM_ITEMS_B using ITEM_OBJECT1_ID1. LS_LTY_CODE and LS_ID expose the line style code and identifier.

Common Use Cases and Queries

Typical uses include lease item extracts, unit of measure validation reports, and reconciliation of negotiated line prices against item capital amounts. The view is commonly queried when the requirement is to list every item on a lease or contract line together with its UOM, quantity, and effective-dated change request context.

For example, to retrieve items and their UOM for a given contract line:

  • SELECT line_number, item_object1_id1, item_uom_code, item_number_of_items, item_capital_amount FROM okl_k_lines_items_uv WHERE line_id = :p_line_id;
  • SELECT line_number, item_id, item_uom_code, item_exception_yn FROM okl_k_lines_items_uv WHERE line_dnz_chr_id = :p_dnz_chr_id ORDER BY line_number, item_id;

Because ITEM_NAME is returned as a space, reports requiring a description should join to the inventory item master on ITEM_OBJECT1_ID1. Consumers should also apply an appropriate filter on LINE_STS_CODE or ITEM_EXCEPTION_YN when only active or exception-bearing lines are of interest.