Results for “previous_contract”

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

Overview

OKL_OR_ASSET_INFO_UV is a read-only database view owned by the APPS schema in Oracle E-Business Suite Release 12.1.1 and 12.2.2. It belongs to the OKL product family — Oracle Lease and Finance Management — and serves as the primary access point for asset-level information associated with a lease or finance contract line. The view is the master-detail counterpart to OKL_OR_HEADER_INFO_UV, presenting the "asset" side of an originated contract record. Because it joins contract header lines with their associated lease line attributes, it exposes a single flattened row per contract line for reporting, extracts, and inter-module integration.

The view is used primarily by Originator and OKL reporting components and by customer-facing Accounting and Asset Management inquiries that need residual values, expected delivery/funding dates, and descriptive asset attributes in one place. In ETRM parlance the "_OR_" naming convention denotes the Originator data model, and "_UV_" denotes a user or validation view intended for query rather than direct DML.

Underlying Base Objects

The view is defined over three APPS synonyms:

• OKC_K_LINES_B — the base contract line table, providing CLEV_FIN.ID and DNZ_CHR_ID, EXCEPTION_YN, and the ownership/header linkage.
• OKC_K_LINES_TL — the translated contract line table, supplying ASSET_NUMBER (NAME) and ITEM_DESCRIPTION, filtered by USERENV('LANG') so descriptions return in the session language.
• OKL_K_LINES — the OKL lease line extension table, which contributes the residual percentage, residual value, residual code, RVI premium, prescribed asset flag, re-lease indicator, previous contract, delivery/funding dates, expected asset cost, and the DFF ATTRIBUTE1–15 columns.

The join is an inner join on OKC_K_LINES_B.ID = OKC_K_LINES_TL.ID = OKL_K_LINES.ID, meaning only contract lines that have a corresponding OKL lease-line record are returned. Notably, thirteen integration-related columns — including ASSET_KEY_ID — are exposed as literal TO_CHAR(NULL) placeholders rather than being sourced from a physical column. These correspond to the FA/inventory integration attributes reserved for the asset master side of the model.

Key Columns

• CLEV_FIN_ID — surrogate contract line identifier (OKC_K_LINES_B.ID), the effective primary key for this view.
• DNZ_CHR_ID — contract header / chapter identifier linking the line to its parent contract.
• ASSET_NUMBER / ITEM_DESCRIPTION — translated asset number and long description.
• RESIDUAL_VALUE, RESIDUAL_PERCENTAGE, RESIDUAL_CODE, RVI_PREMIUM — residual and residual-value-insurance attributes used in lease pricing and termination accounting.
• DATE_DELIVERY_EXPECTED, DATE_FUNDING_EXPECTED, EXPECTED_ASSET_COST — funding and cost expectations used in cash flow projections.
• ASSET_KEY_ID — exposed as a NULL placeholder. In the current view implementation no physical asset_key_id is returned; the column exists solely to preserve the interface contract for downstream consumers expecting the Originator asset-key column.
• ATTRIBUTE_CATEGORY, ATTRIBUTE1–15 — the descriptive flexfield columns sourced from OKL_K_LINES.

Common Use Cases and Queries

Typical uses include lease-detail reports, asset reservation extracts, and reconciliation of OKL lease lines to the OKC contract structure. A representative query follows:

• Reporting assets with residual and expected-cost information for a contract:
  SELECT clev_fin_id, asset_number, item_description, residual_value, expected_asset_cost FROM okl_or_asset_info_uv WHERE dnz_chr_id = :p_chr_id;
• Locating an asset by contract reference:
  SELECT clev_fin_id, dnz_chr_id, asset_number FROM okl_or_asset_info_uv WHERE asset_number = :p_asset_number;
• Filtering re-lease or prescribed-asset lines:
  SELECT asset_number, re_lease_yn, prescribed_asset_yn FROM okl_or_asset_info_uv WHERE re_lease_yn = 'Y';

Because ASSET_KEY_ID returns NULL, callers requiring an actual asset key must source it from the OKL_OR_ASSET_MASTER_UV view or the underlying OKL asset tables rather than from this view.