Results for “kle_name”

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

Overview

OKL_FUND_ASSETS_LOV_UV is a user interface view owned by the APPS schema in Oracle E-Business Suite Release 12.1.1 and 12.2.2. It belongs to the OKL product family, Oracle Lease and Finance Management. As its description states, the view supplies the assets list of values (LOV) displayed on the funding page of the Lease and Finance Management application. It is a presentation-layer object rather than a transactional table: it does not store data of its own, but projects a denormalized, label-friendly result set drawn from asset and accounts-payable funding sources so that the funding page can populate selection prompts for contract assets.

The view is documented as VALID in the ETRM metadata. Because it is intended for UI consumption, it joins asset attributes with AP invoice funding context and computes several amounts through calls to the OKL_FUNDING_PVT package. This makes it relevant both to interactive funding workflows and to reports or integrations that need the same asset-funding values the application surfaces to users.

Underlying Base Objects

The view text identifies its sources directly. It joins three principal objects:

• OKL_ASSETS_LOV_UV (VIEW) — the asset-side source, aliased A, supplying CLE_ID, CHR_ID, ASSET_NUMBER, and DESCRIPTION.
• OKL_TRX_AP_INVOICES_B (SYNONYM) — the AP invoice header funding source, aliased B, supplying ID and IPVS_ID.
• OKL_TXL_AP_INV_LNS_B (SYNONYM) — the AP invoice line funding source, aliased TPL, supplying TAP_ID and KHR_ID.

The join condition is B.ID = TPL.TAP_ID AND A.CHR_ID = TPL.KHR_ID, linking each asset to its associated AP invoice and invoice line funding records. Two of the referenced base objects are synonyms rather than tables, which is typical where OKL surfaces objects from another application schema. The view also references OKL_FUNDING_PVT (PACKAGE), which is invoked directly within the select list to derive calculated amounts. The documented list of referenced base objects therefore comprises OKL_ASSETS_LOV_UV, OKL_FUNDING_PVT, OKL_TRX_AP_INVOICES_B, and OKL_TXL_AP_INV_LNS_B.

Key Columns

The view exposes ten columns reflecting the funding context of each asset:

• FUND_ID — the funding identifier, taken from B.ID on the AP invoice header source.
• CLE_ID — the contract line identifier for the asset, from the asset LOV source.
• CHR_ID — the contract header identifier, used as the linking key to the AP invoice line.
• KLE_NUM — the asset number, presented as the LOV display value for selecting an asset.
• KLE_NAME — the asset description, provided as the LOV name/description.
• KLE_AMT — the contract line amount, computed by OKL_FUNDING_PVT.GET_CONTRACT_LINE_AMT for the given CHR_ID, CLE_ID, and IPVS_ID.
• KLE_FUND_AMT — the funded amount on the contract line, from OKL_FUNDING_PVT.GET_CONTRACT_LINE_FUNDED_AMT.
• VENDOR_SITE_ID — the vendor site identifier, taken from B.IPVS_ID.
• SUB_AMT — the funding subsidy amount, from OKL_FUNDING_PVT.GET_FUNDING_SUBSIDY_AMOUNT.
• SUB_FUND_AMT — the subsidy amount, from OKL_FUNDING_PVT.GET_AMOUNT_SUBSIDY.

The calculated columns depend on the current state of the underlying funding data, so values reflect the results returned by the package functions at query time.

Common Use Cases and Queries

Typical uses include validating what the funding page LOV returns, reconciling funded versus contract amounts for a set of assets, and building custom reports over asset funding. A representative query filtering to a specific contract header is:

• SELECT fund_id, cle_id, chr_id, kle_num, kle_name, kle_amt, kle_fund_amt, vendor_site_id, sub_amt, sub_fund_amt FROM apps.okl_fund_assets_lov_uv WHERE chr_id = :p_chr_id;

To review funded amounts by asset, a user may select KLE_NUM, KLE_AMT, and KLE_FUND_AMT ordered by KLE_NUM. Because the amount columns invoke OKL_FUNDING_PVT functions per row, queries returning large row sets can be expensive; filtering by CHR_ID or CLE_ID is advisable. When replicating this view in a report, ensure the OKL_FUNDING_PVT package is executed in the correct context so the returned amounts match application behavior.