Search Results chr_sts_meaning




Overview
Explore in AI Chat

Overview

OKL_AM_ASSET_RETURNS_UV is a user-facing (UV) view owned by the APPS schema in Oracle E-Business Suite Release 12.1.1 and 12.2.2. It is part of the OKL — Leasing and Finance Management product family and exposes consolidated asset return information drawn from contract headers, contract lines, asset return transactions, lookup values, inventory items, parties, and vendors. The view consolidates data required to report on the disposition of leased assets at end of term, including the date a return was due or actually received, the status and type of the return, remarketing information, and commercial terms such as residual value and floor price.

Because it is a view rather than a base table, no data is stored directly within it. Instead, it provides a denormalized projection built from several transactional and reference objects, enabling reporting tools, concurrent programs, and integration interfaces to retrieve asset return details without performing extensive joins manually. The view is documented with STATUS = VALID on the ETRM 12.2.2 metadata.

Underlying Base Objects

The view is defined over a set of documented base objects, including the following tables, views, synonyms, and packages:

Key Columns

Common Use Cases and Queries

This view is typically used to produce asset return registers, end-of-term disposition reports, and interfaces that feed remarketing or accounting processes. A frequent requirement is to filter on the contract line status code (CLE_STS_CODE), which is why users search for that column name. A representative query is:

SELECT asset_number, cle_sts_code, cle_sts_meaning, contract_number, date_returned, asset_return_status, lessee_party_name, remarketer_name
FROM apps.okl_am_asset_returns_uv
WHERE org_id = :p_org_id
AND cle_sts_code = :p_cle_sts_code
AND date_returned >= :p_from_date;

Other common scenarios include listing all returns still pending (DATE_RETURNED IS NULL), identifying assets with a repurchase agreement flag, or joining back to OKC_K_HEADERS_ALL_B for additional contract detail. Because the view is filtered by ORG_ID and uses FND_GLOBAL for environment context, reports should always constrain on the operating unit to respect multi-org security.