Search Results add_item




Overview
Explore in AI Chat

Overview

OKL_LA_ADD_ITEMS_UV is an APPS-owned database view in Oracle E-Business Suite, documented under the ETRM (Enterprise Transaction Repository Model) metadata for release 12.2.2 and applicable to 12.1.1. It presents the set of add-item lines attached to an Oracle Lease and Finance Management (OLFM) contract, joining lease line, contract line, contract item, line style, and inventory item data into a single flattened row per add-item line. The "UV" suffix denotes a user view intended for read-only consumption by reports, concurrent programs, and integrations rather than by the base transaction forms.

In the leasing model, add-item lines are used to attach inventory or service items (for example, equipment additions or ancillary charges) to an existing contract line. This view isolates that specific usage by filtering the line style to ADD_ITEM, so callers do not need to know the underlying OKL and OKC joins. It is primarily consumed through a synonym exposed in the APPS schema, allowing custom BI Publisher reports, SQL*Plus extracts, and interface programs to retrieve the descriptive details of each add-item line, including the linked inventory item description and the parent contract line.

Underlying Base Objects

The documented base objects referenced by this view are all synonyms in the APPS schema: OKL_K_LINES, OKC_K_LINES_B, OKC_K_ITEMS, OKC_LINE_STYLES_B, MTL_SYSTEM_ITEMS_B, and MTL_SYSTEM_ITEMS_TL. OKL_K_LINES supplies the lease-specific line header (joined to OKC_K_LINES_B on ID). OKC_K_LINES_B provides the contract line itself, including CLE_ID and the line style reference LSE_ID. OKC_LINE_STYLES_B resolves the style code and is used to filter to LTY_CODE = 'ADD_ITEM'. OKC_K_ITEMS carries the item assignment on the line, including the object references and quantity.

MTL_SYSTEM_ITEMS_B holds the inventory item master, joined on OBJECT1_ID1 = INVENTORY_ITEM_ID and OBJECT1_ID2 = TO_CHAR(ORGANIZATION_ID), with the additional predicate JTOT_OBJECT1_CODE = 'OKX_SYSITEM' confirming the item is system-item typed. MTL_SYSTEM_ITEMS_TL supplies the translated item description, restricted to the session language via USERENV('LANG').

Key Columns

  • ID — Identifier of the line (cle.id), used to associate the add-item line to its parent record.
  • PARENT_LINE_ID — The CLE_ID of the contract line to which the add item belongs.
  • UNIT_COST — The line price unit, converted to character via TO_CHAR(cle.price_unit).
  • ID1 / ID2 — Object references from OKC_K_ITEMS; for system items these correspond to inventory item ID and (as a character) organization ID.
  • OBJECT_CODE — The object type code (JTOT_OBJECT1_CODE), which is OKX_SYSITEM in this view.
  • QUANTITY — Number of items (NUMBER_OF_ITEMS) on the add-item line.
  • NAME — Translated inventory item description from MTL_SYSTEM_ITEMS_TL (aliased as NAME).
  • DESCRIPTION — The long description from MTL_SYSTEM_ITEMS_B.

Common Use Cases and Queries

Typical usage includes reporting add-on items per lease contract, extracting item-level detail for billing reconciliation, and feeding interface tables. Because the view already joins the item master and translation, queries are short. For example, to retrieve all add items for a contract's parent line:

SELECT id, parent_line_id, id1, object_code, quantity, name, description
FROM   apps.okl_la_add_items_uv
WHERE  parent_line_id = :p_cle_id;

To list add items with their unit cost by inventory item:

SELECT id1, name, unit_cost, quantity
FROM   apps.okl_la_add_items_uv
WHERE  object_code = 'OKX_SYSITEM'
ORDER BY name;

Because the view filters on line style and item type internally, callers should not re-apply those predicates unless narrowing results further. Note that UNIT_COST is exposed as a character string, so numeric operations require an explicit conversion.