Results for “subsidy_name”

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

Overview

The view OKL_ASSET_SUBSIDY_LOV_UV is a user-interface support object owned by the APPS schema within the Oracle E-Business Suite Release 12.1.1 and 12.2.2 environments. It is registered under the OKL product family, which covers Oracle Leasing and Finance Management. The documented purpose of this view is to supply the list of values (LOV) displayed on the asset subsidy page of the OKL application. In practical terms, it defines the set of subsidy records that an end user may legitimately select when attaching a subsidy to a contract line.

Because it is a view rather than a base table, OKL_ASSET_SUBSIDY_LOV_UV carries no stored data of its own. Instead, it projects, filters, and concatenates information drawn from the subsidy definition tables and the contract line tables, applying both language validation and business-rule validation at query time. This makes it the authoritative runtime source for the "subsidy name" field presented to the user, and it is equally suitable for reporting or integration queries that need to mirror exactly what the application offers on that page.

Underlying Base Objects

The view is defined over several documented base objects. The subsidy side is sourced from OKL_SUBSIDIES_B, which holds the base subsidy definition rows, and OKL_SUBSIDIES_TL, which holds the translated subsidy descriptions. These two are joined on the subsidy identifier, with the translation filtered by the session language through USERENV('LANG'), ensuring that the LOV returns descriptions in the user's current language.

The contract line side is sourced from OKC_K_LINES_B and OKC_LINE_STYLES_B, joined so that only lines whose line style code is FREE_FORM1 are considered. This restricts the LOV to the correct class of contract line on which an asset subsidy may be attached.

The view also references the package OKL_ASSET_SUBSIDY_PVT, invoking its VALIDATE_SUBSIDY_APPLICABILITY function for each candidate combination of subsidy and contract line. Only combinations returning 'Y' are exposed. A further NOT EXISTS clause against OKL_K_LINES and the contract line tables excludes any subsidy already attached to a non-abandoned SUBSIDY-style line for the same contract line, preventing duplicate attachment. All referenced objects resolve through synonyms in the APPS schema.

Key Columns

• SUBSIDY_ID — The unique identifier of the subsidy, sourced from OKL_SUBSIDIES_B.ID. This is the primary return value used to link the selected subsidy back to the contract line.
• SUBSIDY_NAME — The subsidy name from OKL_SUBSIDIES_B.NAME. This is the value most commonly searched for as "subsidy_name" and is the primary display field in the LOV.
• SUBSIDY_DESCRIPTION — The translated short description from OKL_SUBSIDIES_TL.SHORT_DESCRIPTION, supplied for the selected language.
• CLE_ID — The contract line identifier from OKC_K_LINES_B.CLE_ID, identifying the line against which the subsidy applicability check was performed.

Common Use Cases and Queries

The most frequent requirement is to reproduce the subsidy LOV for a specific contract line, or to report which subsidies are attachable. The following query retrieves the valid subsidy choices for a given contract line:

SELECT subsidy_id, subsidy_name, subsidy_description, cle_id FROM apps.okl_asset_subsidy_lov_uv WHERE cle_id = :p_cle_id ORDER BY subsidy_name;

A second common pattern is a simple name lookup, which matches the "subsidy_name" search term directly:

SELECT subsidy_id, subsidy_name FROM apps.okl_asset_subsidy_lov_uv WHERE subsidy_name = :p_subsidy_name;

Because the view enforces both the line style restriction and the package validation, it should be preferred over querying OKL_SUBSIDIES_B directly whenever the objective is to mirror user-facing eligibility. Reporting on subsidy availability should also account for the NOT EXISTS filter, which means a subsidy that is already attached to the same contract line will not appear.