Search Results inst_item




Overview
Explore in AI Chat

Overview

APPS.OKL_LA_SERIAL_NUMBER_UV is a reporting view within the Oracle E-Business Suite (EBS) Lease and Finance Management (OKL) module. It is one of the _UV ("user view") objects that expose serialized, instance-level asset data to downstream reporting, integration, and contract-authoring consumers. Its central purpose is to resolve a serialized item — an Oracle Install Base instance from CSI_ITEM_INSTANCES — to the specific lease contract line under which that item is financed, together with its physical installation location.

The view returns this data in a flattened, denormalized shape that mirrors the Object1/Object2 key idiom used by the OKC contract line framework. In particular, the user search term "inst_item" corresponds directly to the line style INST_ITEM, which is hard-coded in the view's WHERE clause as the discriminator identifying the Install Base item line. This confirms the view's intended semantic role: it exists to expose serial number and instance identifiers for lines typed as INST_ITEM.

Underlying Base Objects

The view is defined over seven referenced base objects, all exposed to APPS as synonyms: CSI_ITEM_INSTANCES, HZ_LOCATIONS, HZ_PARTY_SITES, HZ_PARTY_SITE_USES, OKC_K_ITEMS, OKC_K_LINES_B, and OKC_LINE_STYLES_B.

The join structure is deliberately nested and hierarchical across three levels of contract lines. From the finance header line (CLE_FIN, line style FREE_FORM1) the view descends to an intermediate line (CLE_INST, line style FREE_FORM2) and finally to the Install Base item line (CLE_IB, line style INST_ITEM). The OKC_K_ITEMS table provides the Object1 linkage between the INST_ITEM line and the Install Base instance: the predicate cim_ib.object1_id1 = csi.instance_id with jtot_object1_code = 'OKX_IB_ITEM' ties the contract line to the specific CSI instance. Installation location is resolved through HZ_PARTY_SITE_USES (site_use_type INSTALL_AT), joined to HZ_PARTY_SITES and then HZ_LOCATIONS.

Key Columns

Common Use Cases and Queries

Typical usage includes generating serial-number reports for leased assets, reconciling Install Base instances to their governing lease contracts, and driving integrations that must publish asset-to-contract mappings. Because the view is keyed by serial number, it is frequently joined to CSI or OKC reporting queries.

A representative query retrieving serialized items for a contract is:

SELECT serial_number,
       instance_number_ib,
       inventory_item_id,
       inventory_org_id,
       object_id1_new
FROM   apps.okl_la_serial_number_uv
WHERE  dnz_chr_id = :contract_id;

To locate the contract line for a given serial number:

SELECT kle_id, dnz_cle_id, dnz_chr_id
FROM   apps.okl_la_serial_number_uv
WHERE  serial_number = :serial_number;

Note that the view exposes no primary key; the ID column is a literal NULL. Consumers therefore must rely on KLE_ID or DNZ_CHR_ID as the meaningful identifying columns.