Results for “tradein_amount”

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

Overview

OKL_LA_TRADEIN_UV is a reporting view owned by the APPS schema in Oracle E-Business Suite, delivered as part of the OKL (Lease and Finance Management) product family. Its documented description is "Trade-in Details View." The view consolidates trade-in asset attributes captured against lease and finance contract lines, exposing the trade-in amount, the associated asset cost, and the descriptive details of the leased or financed asset. It is registered as a VALID object at ETRM 12.2.2 and remains available in the 12.1.1 code line, since the underlying OKC and OKL contract-line schema is common to both releases.

The view is read-only by design. It does not store data; it projects and joins contract-line data maintained by the Oracle Contracts (OKC) core tables and the Lease Management extension table. Because the view joins translation and status tables, it returns only active, non-terminated lines and is suitable for inquiry, concurrent-program extracts, XML Publisher report sources, and ad hoc operational reporting. It is not intended as a transactional interface, and no programmatic DML should be attempted against it.

Underlying Base Objects

The view is defined over five referenced objects, all resolved through APPS synonyms:

• OKC_K_LINES_B — the base contract line table, supplying the line identifier and header (DNZ_CHR_ID) context.
• OKC_K_LINES_TL — the translated contract line name table, filtered to the session language.
• OKC_LINE_STYLES_B — the line style definition, used to restrict the view to the FREE_FORM1 line style.
• OKC_STATUSES_B — the status code definition, used to exclude HOLD, EXPIRED, and CANCELLED lines.
• OKL_K_LINES — the Lease and Finance Management extension table holding the trade-in amount and asset cost values.

The join keys are KLE.ID = CLE.ID for both the base and translated line tables, CLE.LSE_ID = LSE.ID for the line style, CLE.STS_CODE = STS.CODE for the status, and CLET.LANGUAGE = USERENV('LANG') for language resolution. The FK between OKC_K_LINES_B and OKL_K_LINES is a one-to-one line extension relationship keyed on the contract line ID.

Key Columns

• ID — the contract line identifier, aliased from KLE.ID, serving as the primary row key.
• DNZ_CHR_ID — the contract header identifier from the base line, linking the trade-in back to the contract.
• ASSET_NUMBER — the asset number or line name, sourced from the translated line table.
• TRADEIN_AMOUNT — a character representation of KLE.TRADEIN_AMOUNT produced by TO_CHAR; note the datatype conversion when ordering or arithmetic is required.
• ASSET_ID — the same identifier as ID, exposed under an asset-oriented alias.
• DESCRIPTION — the item description of the asset, from CLET.ITEM_DESCRIPTION.
• ASSET_COST — the asset cost value sourced from KLE.OEC. This is the column most frequently targeted by users searching for "asset_cost," and it represents the recorded cost basis of the trade-in asset rather than the trade-in credit.
• AMOUNT — the trade-in amount, aliased from KLE.TRADEIN_AMOUNT and returned in numeric form.

Common Use Cases and Queries

Typical uses include trade-in valuation reporting, reconciliation of trade-in credit against asset cost, and feeds into leasing profitability extracts. All queries should be issued as the APPS schema or an account with APPS privileges.

• List trade-ins with cost and credit above a threshold: SELECT id, asset_number, asset_cost, amount FROM apps.okl_la_tradein_uv WHERE asset_cost IS NOT NULL ORDER BY asset_cost DESC;
• Aggregate trade-in value per contract header: SELECT dnz_chr_id, SUM(amount) FROM apps.okl_la_tradein_uv GROUP BY dnz_chr_id;
• Compare cost to credit: SELECT asset_number, asset_cost, amount, (asset_cost - amount) variance FROM apps.okl_la_tradein_uv;
• Search by a specific asset: SELECT id, dnz_chr_id, asset_number, description FROM apps.okl_la_tradein_uv WHERE asset_number = :p_asset;

Because TRADEIN_AMOUNT is a character column while ASSET_COST and AMOUNT are numeric, comparisons and sorting should reference AMOUNT rather than TRADEIN_AMOUNT to avoid implicit conversion and to ensure correct numeric ordering.