Search Results subsidy_cle_id

Overview

OKL_ASSET_SUBSIDY_UV is a user interface view owned by the APPS schema within the Oracle E-Business Suite Release 12.1.1 and 12.2.2 environment. It belongs to the OKL product family, Leasing and Finance Management, and carries a status of VALID. As described in the ETRM metadata, the view serves as the user interface view for the asset subsidies page, meaning that the Oracle Forms-based asset subsidy screen and related presentation logic resolve their data from this single, denormalized projection rather than from the underlying normalized transaction tables directly. The view consolidates subsidy header information, translated descriptive text, contract line context, and vendor details into one flat row per qualifying subsidy line, which simplifies both UI rendering and ad hoc reporting. Because it is a view rather than a table, it stores no data of its own; every query executes against the base objects at runtime, so results always reflect the current committed state of the leasing contracts. The view is also relevant to integration and reporting consumers who need a compact, business-friendly representation of asset subsidies without navigating the OKC contract and OKL subsidy entity model themselves.

Underlying Base Objects

The documented base objects referenced by OKL_ASSET_SUBSIDY_UV are OKC_K_LINES_B, OKC_K_PARTY_ROLES_B, OKC_LINE_STYLES_B, OKL_K_LINES, OKL_SUBSIDIES_ALL_B, OKL_SUBSIDIES_TL, and OKX_VENDORS_V. With the exception of OKX_VENDORS_V, which is itself a view, the remaining objects are referenced through synonyms in the APPS schema. The join structure is driven from the subsidy line: OKL_K_LINES (aliased KLE) provides the subsidy amount and override amount and links to OKL_SUBSIDIES_ALL_B (SUBB) on SUBSIDY_ID, which in turn links to OKL_SUBSIDIES_TL (SUBT) on ID with the language restriction SUBT.LANGUAGE = USERENV('LANG') to return the session-appropriate translation. The same OKL_K_LINES row joins to OKC_K_LINES_B (CLEB) on line ID, and OKC_LINE_STYLES_B (LSEB) is joined on the line style with the filter LTY_CODE = 'SUBSIDY'. Vendor information is attached through OKC_K_PARTY_ROLES_B (CPLB) using an outer join on DNZ_CHR_ID and CLE_ID with the role code 'OKL_VENDOR', and OKX_VENDORS_V supplies the vendor name and identifier through a further outer join on the JTOT object code 'OKX_VENDOR'. The predicate CLEB.STS_CODE <> 'ABANDONED' excludes abandoned contract lines from the result set.

Key Columns

• SUBSIDY_ID — Identifier of the subsidy record from OKL_K_LINES, the primary linkage back to the subsidy entity.
• SUBSIDY_CLE_ID — The contract line identifier (CLEB.ID) associated with the subsidy line.
• NAME — Subsidy name sourced from OKL_SUBSIDIES_ALL_B.
• DESCRIPTION — Short description from the translated OKL_SUBSIDIES_TL table.
• AMOUNT — The subsidy amount recorded on the line.
• SUBSIDY_OVERRIDE_AMOUNT — Character-converted override amount, returned through TO_CHAR, reflecting the UI's text-based presentation of this field.
• DNZ_CHR_ID — The contract (header) identifier that anchors the line to its lease.
• ASSET_CLE_ID — The contract line identifier for the asset to which the subsidy applies; this is the column most directly associated with the user search term "asset_cle_id" and is the practical key for joining subsidies to asset lines.
• CPL_ID — Party role identifier for the vendor role record.
• VENDOR_ID and VENDOR_NAME — Vendor identifier and name from OKX_VENDORS_V, populated only where a vendor role exists for the contract line.

Common Use Cases and Queries

Typical usage includes reviewing all subsidies attached to a lease, validating vendor attribution on subsidy lines, and feeding downstream reports that reconcile subsidy amounts against asset lines. The most frequent lookup pattern filters on the asset contract line identifier:

• SELECT subsidy_id, asset_cle_id, name, amount, vendor_name FROM okl_asset_subsidy_uv WHERE asset_cle_id = :p_asset_cle_id;
• SELECT dnz_chr_id, asset_cle_id, subsidy_id, amount, subsidy_override_amount FROM okl_asset_subsidy_uv WHERE dnz_chr_id = :p_contract_id ORDER BY asset_cle_id;
• SELECT vendor_id, vendor_name, COUNT(*) subsidy_count, SUM(amount) total_amount FROM okl_asset_subsidy_uv GROUP BY vendor_id, vendor_name;

Because the view applies the USERENV('LANG') translation filter and the abandoned-line exclusion internally, consumers should not attempt to replicate those predicates; doing so risks returning rows the UI would suppress. Queries should generally be restricted by DNZ_CHR_ID or ASSET_CLE_ID to keep execution plans efficient, since the view joins six base objects and can otherwise scan a large portion of the leasing contract data.