Results for “okl_pool_assets_uv”

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

Overview

OKL_POOL_ASSETS_UV is an Oracle E-Business Suite view owned by the APPS schema within the OKL (Lease and Finance Management) product family. Its documented purpose is to serve as the Securitization - Pool Assets UI view, meaning it supplies the data layer behind the Pool Assets user interface used in lease securitization and portfolio funding processes. The object holds a VALID status and is delivered as part of the standard ETRM 12.1.1 / 12.2.2 installation, so it is a supported, upgrade-safe object referenced directly by Oracle application code.

Because the view resolves the complex contractual relationships between lease contracts, contract line items, assets, system items, vendors, and lease-specific line attributes into a single flat row per pooled asset, it functions as a denormalized reporting and integration artifact. Rather than requiring consumers to traverse the OKC contract schema and OKX asset/system item views independently, the view presents a consolidated projection suitable for UI display, concurrent program output, and outbound interfaces.

Underlying Base Objects

The documented referenced base objects are OKC_K_ITEMS, OKC_K_LINES_B, OKC_K_PARTY_ROLES_B, OKC_LINE_STYLES_B, OKL_K_HEADERS, OKL_K_LINES, and the OKX views OKX_ASSETS_V, OKX_SYSTEM_ITEMS_V, and OKX_VENDORS_V. All OKC and OKL references are synonyms resolving to the APPS base tables, while the OKX objects are views.

In the view text, OKC_K_ITEMS appears three times (aliased CIMA, CITM, and conceptually for the asset/system item junction), joined to OKX_ASSETS_V and OKX_SYSTEM_ITEMS_V through the JTOT_OBJECT1_CODE discriminator values 'OKX_ASSET' and 'OKX_SYSITEM'. OKC_K_LINES_B and OKC_LINE_STYLES_B are self-joined three times each to segregate FIXED_ASSET, ITEM, and FREE_FORM1 line style categories. OKC_K_PARTY_ROLES_B is outer-joined (denoted by the (+) operator) to resolve the OKL_VENDOR role into OKX_VENDORS_V. OKL_K_LINES supplies the lease-specific attributes OEC and RESIDUAL_PERCENTAGE, and OKL_K_HEADERS anchors the contract through DNZ_CHR_ID, the document/contract identifier.

Key Columns

• DNZ_CHR_ID — The contract/document identifier, linking the pooled asset to its parent lease header.
• KLE_ID — The contract line identifier (from OKC_K_LINES_B), uniquely identifying the lease line on which the asset sits.
• ASSET_ID / ASSET_NUMBER / MODEL_NUMBER / MANUFACTURER_NAME — Asset identity attributes sourced from OKX_ASSETS_V, describing the physical or financial asset being pooled.
• ITEM_ID1 — The system item identifier from OKX_SYSTEM_ITEMS_V, identifying the inventory or item definition associated with the line.
• VENDOR_ID1 — The vendor identifier resolved through the OKL_VENDOR party role and OKX_VENDORS_V.
• OEC — The original equipment cost (or equivalent lease line value) retrieved from OKL_K_LINES.
• RESIDUAL_PERCENTAGE — The residual value percentage carried on the lease line, central to securitization valuation.

Common Use Cases and Queries

Typical scenarios include validating pool composition before securitization, reconciling asset-level OEC and residual values to the lease line, and extracting data for investor or funding-agreement reporting. A basic listing by contract is:

• SELECT dnz_chr_id, kle_id, asset_number, model_number, manufacturer_name, oec, residual_percentage FROM okl_pool_assets_uv WHERE dnz_chr_id = :p_contract_id;
• SELECT asset_number, vendor_id1, item_id1, oec FROM okl_pool_assets_uv ORDER BY dnz_chr_id, kle_id;

Because several joins are outer joins on the vendor path, VENDOR_ID1 may be null when no OKL_VENDOR role exists on the line; queries should therefore use NVL or left-join-style predicates where vendor presence is optional. Filtering on DNZ_CHR_ID or KLE_ID is recommended, as the view spans all lease contracts and is not partitioned for selective querying.