Search Results subsidy_override_amount




Overview
Explore in AI Chat

Overview

APPS.OKL_ASSET_SUBSIDY_UV is a supplementary view within the Oracle E-Business Suite (EBS) Enterprise Contracts / Lease Management (OKL) module. It is registered against FND Design Data OKL.OKL_ASSET_SUBSIDY_UV and carries a status of VALID at the time of documentation. Oracle classifies this object explicitly as a "supplementary view used to simplify forms coding," which means its primary design intent is to flatten and pre-join subsidy-related columns so that Oracle Forms-based user interfaces can retrieve asset-level subsidy data through a single, simplified query.

The view exposes the financial subsidy arrangements attached to individual contract asset lines, including the subsidy name, description, monetary amount, an override amount, vendor identifiers, and party role information. For EBS 12.1.1 and 12.2.2, this view is not part of the public integration surface. Oracle's own documentation includes a standing warning that querying or altering data through this view is not recommended and that its structure may change dramatically in subsequent minor or major releases. Report developers and integration architects should therefore treat it as an internal implementation object rather than a stable interface.

Underlying Base Objects

The view is defined over seven documented dependencies, all accessed through APPS synonyms or views:

  • OKL_SUBSIDIES_ALL_B — the core subsidy base table supplying identifier, description, and amount data.
  • OKL_SUBSIDIES_TL — the translation table supplying language-dependent subsidy text.
  • OKL_K_LINES — the lease/contract line entity providing subsidy line context and asset associations.
  • OKC_K_LINES_B — the Contracts core line table, linking the subsidy to its parent contract line.
  • OKC_K_PARTY_ROLES_B — the Contracts party-role table, resolving the subsidy provider and vendor roles.
  • OKC_LINE_STYLES_B — the Contracts line-style table used to classify line types.
  • OKX_VENDORS_V — the trading community vendor view used to resolve the vendor name.

The join topology connects a contract identifier (DNZ_CHR_ID) and asset line identifier (ASSET_CLE_ID) to a subsidy record, and then to the party role and vendor definition. Downstream, the view is referenced by PL/SQL packages OKL_ASSET_SUBSIDY_PVT, OKL_CS_LC_CONTRACT_PVT, and OKL_SUBSIDY_POOL_AUTH_TRX_PVT, confirming it is consumed by internal business logic as well as by Forms.

Key Columns

  • SUBSIDY_ID — unique numeric identifier for the subsidy record.
  • SUBSIDY_CLE_ID — the subsidy line identifier, tying the row to a specific contract line.
  • NAME / DESCRIPTION — subsidy name (VARCHAR2 30) and description (VARCHAR2 150).
  • AMOUNT — the subsidy amount, NUMBER(14).
  • SUBSIDY_OVERRIDE_AMOUNT — the field the user searched for; a VARCHAR2(40) column holding the subsidy override amount as displayed or entered, rather than a native numeric. This datatype choice reflects the view's Forms-oriented origin and means consumers must apply explicit numeric conversion before arithmetic.
  • DNZ_CHR_ID — the contract header identifier.
  • ASSET_CLE_ID — the asset line identifier the subsidy is attached to.
  • CPL_ID — the subsidy provider party identifier.
  • VENDOR_ID / VENDOR_NAME — the subsidy vendor's identifier and display name (VARCHAR2 240).

Common Use Cases and Queries

Typical scenarios include reconciling subsidy amounts on leased assets, auditing the difference between AMOUNT and SUBSIDY_OVERRIDE_AMOUNT, and reporting subsidy exposure by vendor. The following query returns all subsidies for a given contract:

SELECT SUBSIDY_ID, NAME, AMOUNT, SUBSIDY_OVERRIDE_AMOUNT, VENDOR_NAME
FROM APPS.OKL_ASSET_SUBSIDY_UV
WHERE DNZ_CHR_ID = :contract_id;

To compare base and override amounts, cast the override column explicitly:

SELECT SUBSIDY_ID, AMOUNT, TO_NUMBER(SUBSIDY_OVERRIDE_AMOUNT) override_amt
FROM APPS.OKL_ASSET_SUBSIDY_UV
WHERE SUBSIDY_OVERRIDE_AMOUNT IS NOT NULL
AND TO_NUMBER(SUBSIDY_OVERRIDE_AMOUNT) <> AMOUNT;

Because the view is unsupported for direct querying, production reporting should preferably target the underlying OKL_SUBSIDIES_ALL_B table through supported APIs, using this view only where Oracle's own Forms and packages already do so.