Search Results okl_la_serial_number_uv




Overview
Explore in AI Chat

Overview

OKL_LA_SERIAL_NUMBER_UV is a user interface (UI) view owned by the APPS schema in Oracle E-Business Suite, defined under the OKL – Leasing and Finance Management product. Its documented purpose is to present install base serial numbers of a financial asset, providing a flattened, query-ready projection of serialized leased assets and their associated contract structures. The view is marked VALID and is classified as a VIEW object type, meaning it carries no storage of its own and derives all data from underlying synonyms and base tables at runtime.

Because it is a UI-oriented view rather than a transactional table, it is intended for read access: report builders, OAF/Forms-based inquiry pages, and integration extracts can consume it without touching the normalization logic that links contracts, line styles, items, and the install base. The view collapses the multi-level OKC contract hierarchy (financial line, instance line, install base line) together with CSI install base records and HZ location/party site data into a single row set.

Underlying Base Objects

The documented metadata lists the referenced base objects as synonyms over the following tables: 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 view text joins these through several aliases that reveal the contract hierarchy:

The join path enforces a strict contract genealogy: financial line to instance line to install base line, then to the item reference and finally to the CSI instance and its location.

Key Columns

Common Use Cases and Queries

The view supports asset-level reporting where a serialized item must be traced back to its contract header and financial line, and forward to its physical installation site. Typical scenarios include lease asset inventory reconciliation, verification that serial-numbered equipment is linked to the correct contract, and extracts for downstream asset tracking or integration.

A representative query retrieves serial numbers with their contract context:

  • SELECT DNZ_CHR_ID, KLE_ID, SERIAL_NUMBER, INSTANCE_NUMBER_IB, INVENTORY_ITEM_ID, INVENTORY_ORG_ID FROM OKL_LA_SERIAL_NUMBER_UV WHERE DNZ_CHR_ID = :contract_id;
  • SELECT SERIAL_NUMBER, INSTANCE_NUMBER_IB, INVENTORY_ITEM_ID FROM OKL_LA_SERIAL_NUMBER_UV WHERE INVENTORY_ITEM_ID = :item_id;
  • SELECT KLE_ID, SERIAL_NUMBER, OBJECT_ID1_NEW FROM OKL_LA_SERIAL_NUMBER_UV WHERE INVENTORY_ORG_ID = :org_id;

Because ID and OBJECT_ID2_NEW return literal placeholders, they should not be used as keys. Joins back to OKC_K_LINES_B or CSI_ITEM_INSTANCES should be driven through KLE_ID, DNZ_CHR_ID, or INSTANCE_NUMBER_IB respectively.