Search Results line_sts_code




Overview
Explore in AI Chat

Overview

OKL_AM_ASSET_LOV_UV is a read-only view owned by the APPS schema in Oracle Lease and Finance Management (OKL), a module of Oracle E-Business Suite. It functions as a list-of-values (LOV) source for free-form lease assets, presenting a consolidated, query-ready projection of lease line assets joined to their parent contract headers, line styles, and status codes. The view is delivered with VALID status and is intended for reporting, form LOV population, and integration extracts rather than transactional data entry.

Its principal filtering logic restricts results to free-form line styles (LSE.LTY_CODE = 'FREE_FORM1'), excludes assets that have a non-cancelled return recorded against them, and omits line statuses of ENTERED, SIGNED, and CANCELLED. The net effect is a view that surfaces only lease assets that are active, contract-bearing, and not yet returned — the population most commonly required by asset management screens and downstream reporting. Because it is a view, it introduces no storage of its own and inherits the read consistency and privileges of its defining query.

Underlying Base Objects

The view is defined over five documented base objects:

  • OKC_K_LINES_V (VIEW) — supplies lease line detail (aliased OALV), including the internal ID, asset name, item description, change request ID, and status code.
  • OKC_K_HEADERS_B (SYNONYM) — the contract header table (aliased OKHV), providing contract number, start date, and end date.
  • OKC_LINE_STYLES_B (SYNONYM) — line style definitions (aliased LSE), used to constrain results to the FREE_FORM1 line style.
  • OKC_STATUSES_V (VIEW) — the statuses lookup (aliased STS), supplying the status code and its translated meaning.
  • OKL_ASSET_RETURNS_V (VIEW) — the asset returns view, referenced in a NOT EXISTS subquery to exclude returned assets.

These objects span the OKC (Contracts Core) and OKL schemas logically; the view itself sits in APPS and is typically granted to reporting and integration users.

Key Columns

  • KLE_ID — internal identifier of the lease line asset (from OALV.ID); the primary join key for downstream consumers.
  • ASSET_NUMBER — the asset name/number presented to users.
  • ASSET_DESCRIPTION — item description of the asset.
  • CHR_ID — the contract header identifier linking the asset to its contract.
  • CONTRACT_NUMBER — business-facing contract number.
  • START_DATE / EXPIRATION_DATE — contract start and end dates (end date aliased from OKHV.END_DATE).
  • LINE_STS_CODE — the status code of the lease line, sourced from OKC_STATUSES_V.CODE. This is the column most often referenced by the search term "line_sts_code".
  • LINE_STATUS — the translated meaning of the code, suitable for display.

Common Use Cases and Queries

The view is typically queried to populate asset LOVs, validate user-entered asset numbers against active leases, and drive asset-return and expiry reports. A representative query retrieving active free-form lease assets with their status:

  • SELECT kle_id, asset_number, contract_number, line_sts_code, line_status FROM apps.okl_am_asset_lov_uv WHERE line_sts_code = :p_status;

Because LINE_STS_CODE is a code value, practical filters combine it with the CONTRACT_NUMBER or EXPIRATION_DATE to isolate assets nearing lease end. Reporting queries frequently select ASSET_NUMBER alongside START_DATE and EXPIRATION_DATE to reconcile the asset population against OKL_ASSET_RETURNS_V. Integrations should treat KLE_ID as the stable key and avoid relying on ASSET_NUMBER for uniqueness. Note that the exclusion subquery already removes returned assets, so consumers need not re-filter on return status.