Search Results okl_la_add_items_uv




Overview
Explore in AI Chat

Overview

OKL_LA_ADD_ITEMS_UV is a VALID database view owned by the APPS schema within the Oracle E-Business Suite Release 12.1.1 and 12.2.2 environments. It belongs to the OKL product family — Oracle Lease and Finance Management — and is documented as a User Interface view for the asset add-ons page. Its purpose is to expose the line-level data required to render the add-ons region of the leasing contract user interface and to support the associated processing that registers additional assets against an existing contract line.

Because it is a UI-facing view rather than a private, single-purpose construct, it is also frequently referenced in reporting extracts, reconciliation scripts, and integration interfaces that need to identify which contract lines represent add-on items and which inventory items they carry. The view is non-updatable and functions as a projection over the leasing contract line, contract item, line style, and inventory master tables.

Underlying Base Objects

The view is defined over six base objects, all referenced through APPS synonyms: OKL_K_LINES, OKC_K_LINES_B, OKC_K_ITEMS, OKC_LINE_STYLES_B, MTL_SYSTEM_ITEMS_B, and MTL_SYSTEM_ITEMS_TL. Joins are established on the line identifier, so that OKC_K_LINES_B.ID equals both OKL_K_LINES.ID and OKC_K_ITEMS.CLE_ID, while OKC_K_LINES_B.LSE_ID resolves the line style used to eliminate non-add-on lines.

  • OKL_K_LINES supplies the leasing-specific line extension, joined by ID to the contract line.
  • OKC_K_LINES_B provides the core contract line record, including PRICE_UNIT and DNZ_CHR_ID.
  • OKC_K_ITEMS supplies the item association rows, including quantity, the item identifier pair, and the JTOT_OBJECT1_CODE discriminator.
  • OKC_LINE_STYLES_B is filtered to LTY_CODE = 'ADD_ITEM' so that only add-on lines qualify.
  • MTL_SYSTEM_ITEMS_B and MTL_SYSTEM_ITEMS_TL supply the item description, with the translated table restricted to the session language via USERENV('LANG').

Key Columns

  • ID — the contract line identifier (CLE.ID) for the add-on line.
  • PARENT_LINE_ID — the CLE_ID of the parent contract line to which the add-on attaches.
  • UNIT_COST — the line price unit, exposed as a character string through TO_CHAR.
  • OBJECT_CODE — the JTOT object code, restricted to OKX_SYSITEM when an inventory item is joined.
  • QUANTITY — the number of items recorded on the contract item line.
  • NAME — the inventory item description from MTL_SYSTEM_ITEMS_TL.
  • DESCRIPTION — an additional description attribute sourced from MTL_SYSTEM_ITEMS_B.

The view text also selects the surrogate keys ID1 (OBJECT1_ID1) and ID2 (OBJECT1_ID2), which map to the inventory item identifier and organization identifier respectively. These columns are not listed among the documented output attributes but are present in the view definition and are commonly used in downstream joins.

Common Use Cases and Queries

Typical usage includes listing all add-on assets for a given contract line, reconciling add-on quantities against inventory, and building UI extracts for the asset add-ons page. A representative query joins the view to a contract header to isolate add-ons for one contract:

  • SELECT id, parent_line_id, name, quantity, unit_cost FROM okl_la_add_items_uv WHERE parent_line_id = :line_id;
  • SELECT name, SUM(quantity) FROM okl_la_add_items_uv GROUP BY name ORDER BY 2 DESC;
  • SELECT id, id1, id2, object_code, quantity FROM okl_la_add_items_uv WHERE object_code = 'OKX_SYSITEM';

Because the view filters strictly on line style ADD_ITEM and object code OKX_SYSITEM, queries against it return only add-on inventory items, which makes it well suited to contract audit and interface validation reports.