Search Results okx_asset




Overview
Explore in AI Chat

Overview

OKL_POOL_ASSETS_LOV_UV is an APPS-owned database view in Oracle E-Business Suite (validated against 12.1.1 and 12.2.2) that exposes a list-of-values (LOV) style result set of fixed assets which are associated with booked lease contracts and line styles of the type FIXED_ASSET. In practice, the view answers the question: "Which fixed assets are linked to a given leased asset position?" It is consumed primarily by Oracle Lease and Finance Management (OKL) and Oracle Contracts (OKC) forms, where a user must select the asset that a contract line references.

Although it is a view rather than a table, it functions as a reporting and integration primitive. Its role is twofold: (1) it drives LOV pickers within the ETRM (Enterprise Trade and Risk Management / Lease Management) application, and (2) it can be reused in custom reports and interfaces to resolve an asset_id to a human-readable asset_number and description without having to reconstruct the underlying lease-to-asset join. The name "POOL_ASSETS" reflects that the assets originate from a pool of assets attached to lease contract lines.

Underlying Base Objects

The view is defined over six documented base objects (all accessed via APPS synonyms):

The literal OKX_ASSET that the user searched for is the JTOT_OBJECT1_CODE value that keys the join between contract line items and fixed assets. It is the pivot that ties an OKC contract line to an FA asset.

Key Columns

  • ASSET_ID — the primary key of the fixed asset from FA_ADDITIONS_B; it is the value passed into OKC_K_ITEMS.OBJECT1_ID1 (converted to character).
  • ASSET_NUMBER — the user-visible asset number from FA_ADDITIONS_B, the typical display value in an LOV.
  • DESCRIPTION — the asset description from FA_ADDITIONS_TL in the current session language.

Because the view restricts itself to those three projected columns, it is a lean, purpose-built LOV rather than a general asset query. Additional attributes (asset category, book, cost) are not exposed and must be obtained by joining back to FA_ADDITIONS_B and related FA tables.

Common Use Cases and Queries

Typical uses include LOV population in lease contract line entry, validation that a chosen asset is genuinely associated with a booked lease contract line of the FIXED_ASSET style, and reconciliation reports.

Listing all pool assets for reporting:

SELECT asset_id, asset_number, description FROM apps.okl_pool_assets_lov_uv ORDER BY asset_number;

Resolving a specific asset:

SELECT asset_number, description FROM apps.okl_pool_assets_lov_uv WHERE asset_id = :p_asset_id;

Pattern-matching an asset number for an LOV-style lookup:

SELECT asset_id, asset_number FROM apps.okl_pool_assets_lov_uv WHERE UPPER(asset_number) LIKE UPPER(:p_search)||'%';

Count of distinct pooled assets per contract requires joining back to OKC_K_ITEMS and OKC_K_HEADERS_B, since the view does not project the contract ID. As with any APPS synonym-based view, it should be queried through the APPS schema or a synonym and is subject to the standard Oracle EBS security and performance model; the joins across OKC and FA tables can be costly on large lease portfolios, so predicates on asset_id or asset_number are recommended.