Search Results mtl_description

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:

• OKL_ASSET_RETURNS_ALL_B and OKL_ASSET_RETURNS_TL — the core asset return records and their translated (language) rows, supplying return dates, comments, flags, IDs, and descriptive attributes.
• OKL_K_LINES_FULL_V — supplies contract line attributes such as asset number, item description, status code (CLE_STS_CODE), CHR_ID, residual value, and OEC.
• OKC_K_HEADERS_ALL_B, OKC_K_ITEMS, OKC_K_LINES_B, OKC_LINE_STYLES_B, OKC_K_PARTY_ROLES_V, and OKC_STATUSES_V — provide contract number, contract status, parties, and line style information.
• FND_LOOKUPS — resolves lookup codes such as ARS_CODE and ART1_CODE into their displayed meanings (ASSET_RETURN_STATUS, ASSET_RETURN_TYPE).
• MTL_SYSTEM_ITEMS_B — supplies inventory item number, description, and organization for the returned item.
• HZ_PARTIES — provides lessee party name and party ID.
• OKX_VENDORS_V and OKL_AM_REMARKET_TEAMS_UV — supply remarketer and agent information.
• OKL_SYSTEM_PARAMS and the OKL_AM_UTIL_PVT package (via GET_RULE_FIELD_VALUE) — supply system parameters and derived rule-based values such as the title custodian.
• FND_GLOBAL — provides environment context (for example, organization/operating unit) within the session.

Key Columns

• CLE_STS_CODE / CLE_STS_MEANING — the status code and corresponding meaning of the contract line’s leased asset, sourced from OKL_K_LINES_FULL_V (KLE.STS_CODE). This is the column most relevant to the user’s search term “cle_sts_code.”
• CHR_STS_CODE / CHR_STS_MEANING — the contract header status code and meaning, from OKC.STS_CODE.
• ASSET_NUMBER, ITEM_DESCRIPTION, INVENTORY_ITEM_NUMBER, MTL_DESCRIPTION, MTL_ORGANIZATION_ID — identifying and descriptive details of the asset.
• CONTRACT_NUMBER, RESIDUAL_VALUE, OEC, END_DATE, PRICE_UNIT — contract and valuation attributes.
• DATE_RETURNED, DATE_RETURN_DUE, DATE_RETURN_NOTIFIED, DATE_REPOSSESSION_ACTUAL, DATE_REPOSSESSION_REQUIRED, DATE_HOLD_UNTIL, DATE_TITLE_RECEIVED — the lifecycle dates associated with the return.
• ASSET_RETURN_STATUS, ASSET_RETURN_TYPE (from FND_LOOKUPS) — decoded descriptions of return condition and processing type.
• VOLUNTARY_YN, RELOCATE_ASSET_YN, ASSET_RELOCATED_YN, REPURCHASE_AGMT_YN, LIKE_KIND_YN, COMMMERCIALLY_REAS_SALE_YN — commercial and behavioral flags governing the return.
• REMARKETER_NAME, AGENT_NAME, AGENT_ID — parties responsible for remarketing.
• LESSEE_PARTY_NAME, LESSEE_PARTY_ID, LESSEE_KPR_ID — customer identification.
• FLOOR_PRICE, NEW_ITEM_PRICE, NEW_ITEM_NUMBER, NEW_ITEM_DESCRIPTION, ASSET_FMV_AMOUNT — pricing and replacement item information. Note the column alias DATE_TITLE_RETURNED maps internally to OAR.DATE_TITLE_RETURNED although the description lists DATE_TITLE_RECEIVED.

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.