Results for “okl_assets_lov_uv”

AI-generated from documented ETRM metadata — verify critical details on the linked pages.

Overview

OKL_ASSETS_LOV_UV is a user interface view owned by the APPS schema in Oracle E-Business Suite, defined within the OKL – Lease and Finance Management product family. The view exists to populate the Asset List of Values (LOV) presented to end users on OKL lease and asset-related forms. It exposes a curated, filtered set of contract lines that qualify as leaseable assets, returning a compact projection of four columns: CLE_ID, CHR_ID, ASSET_NUMBER, and DESCRIPTION. Rather than exposing the full underlying contract and line data model, the view pre-applies business filters so that the LOV returns only free-form asset lines on active lease or quote contracts, hiding lines whose status is HOLD, EXPIRED, TERMINATED, or CANCELLED.

The object is documented as VALID in both ETRM 12.1.3 and 12.2.2 reference material, and is not a base table — it is a read-only, joins-only view with no data of its own. Its scope is presentation and light integration: reports, form LOVs, and downstream queries can select from it directly instead of re-implementing the join and status logic manually.

Underlying Base Objects

The view is defined over five OKC contract objects, all referenced through APPS synonyms:

• OKC_K_HEADERS_B — the contract header, aliased CHR. Provides the contract identifier and the SCS_CODE that restricts results to 'LEASE' and 'QUOTE' document types.
• OKC_K_LINES_B — the contract line, aliased CLE. Supplies the line ID (CLE.ID) and the DNZ_CHR_ID foreign key back to the header.
• OKC_K_LINES_TL — the translatable line table, aliased TL. Supplies the asset NAME (ASSET_NUMBER) and ITEM_DESCRIPTION (DESCRIPTION), and is joined on the user's language via the USERENV('LANG') predicate.
• OKC_LINE_STYLES_B — the line style definition, aliased LSE. Constrains the line to style code 'FREE_FORM1', isolating manually entered asset lines from structured line types.
• OKC_STATUSES_B — the status definition, aliased STS. Joins CLE.STS_CODE to the status code and excludes the four non-asset statuses via the STE_CODE predicate.

Because the view is a straight join across these synonyms, it inherits the security of the OKC contract tables and respects multi-language installations through the TL join.

Key Columns

• CLE_ID — the contract line identifier (OKC_K_LINES_B.ID). This is the primary key value returned to the LOV and is typically the value a form stores when an asset is selected.
• CHR_ID — the contract header identifier (OKC_K_LINES_B.DNZ_CHR_ID). Identifies the lease or quote contract to which the asset line belongs.
• ASSET_NUMBER — the line name (OKC_K_LINES_TL.NAME), presented as the asset number in the LOV. This is the first descriptive column a user sees.
• DESCRIPTION — the line item description (OKC_K_LINES_TL.ITEM_DESCRIPTION), the secondary descriptive field displayed alongside the asset number.

Common Use Cases and Queries

Typical applications include populating asset LOV fields on OKL lease and quote entry forms, driving ad-hoc asset listings, and validating which contract lines are eligible for asset-level processing. A basic retrieval by contract looks like this:

• List assets for a contract: SELECT cle_id, asset_number, description FROM okl_assets_lov_uv WHERE chr_id = :p_chr_id ORDER BY asset_number;
• Search by asset number: SELECT cle_id, chr_id, asset_number, description FROM okl_assets_lov_uv WHERE asset_number LIKE :p_prefix || '%';
• Report all available assets: SELECT asset_number, description, chr_id FROM okl_assets_lov_uv ORDER BY asset_number;

Because the status and document-type filters are embedded in the view text, callers do not need to add predicates for HOLD, EXPIRED, TERMINATED, or CANCELLED lines, nor to restrict SCS_CODE to LEASE or QUOTE. This makes OKL_ASSETS_LOV_UV a stable, reusable access path for any process that requires the current set of leaseable assets in the ETRM data model.