Results for “number_of_units”

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

Overview

OKL_CS_LINE_VERSION_UV is an Oracle E-Business Suite 12.1.1 / 12.2.2 view owned by the APPS schema and defined within the OKL – Leasing and Finance Management product family. Its documented purpose is to present a consolidated list of line versions, exposing a denormalized, report-ready projection of contract line data tied to leasing assets. Rather than requiring callers to join the many header, line, item, and status tables individually, the view encapsulates that logic and surfaces a single logical record set for each distinct line version.

Because the view is defined as a UNION of two SELECT blocks, it is deliberately constructed to span more than one line-handling pattern in OKL/OKC contracts: the standard free-form line structure (driven through OKC_LINE_STYLES_B with an LTY_CODE of 'FREE_FORM1' and a nested 'ITEM' model line) and an asset-oriented path rooted in the transaction asset table OKL_TXL_ASSETS_B. This makes the view a convenient integration and reporting surface for consumers who need asset numbers, parent line identifiers, residual and capital values, and statuses without navigating the underlying model themselves. It should be treated as a read-only reporting object; it exposes no DML semantics of its own.

Underlying Base Objects

The documented base objects referenced by OKL_CS_LINE_VERSION_UV are: OKC_K_HEADERS_B, OKC_K_HEADERS_BH, OKC_K_ITEMS, OKC_K_ITEMS_H, OKC_K_LINES_BH, OKC_K_LINES_HV, OKC_K_LINES_TLH, OKC_LINE_STYLES_B, OKC_STATUSES_V, OKL_K_HEADERS, OKL_K_LINES, OKL_K_LINES_H, and OKL_TXL_ASSETS_B. With the exception of OKC_K_LINES_HV and OKC_STATUSES_V, which are themselves views, the remainder are synonyms resolving to the underlying OKC and OKL tables.

The structure reveals a layered dependency. Header-level identity (ID, CONTRACT_NUMBER, CURRENCY_CODE) originates from OKC_K_HEADERS_B, with the historical variant OKC_K_HEADERS_BH appearing in the union branch. Line-level attributes come from OKC_K_LINES_HV and OKC_K_LINES_BH, while translated text (such as ITEM_DESCRIPTION) is retrieved via OKC_K_LINES_TLH with the USERENV('LANG') language bind. Item counts and item-level details flow from OKC_K_ITEMS_H (and OKC_K_ITEMS). Leasing-specific financial attributes — residual value, residual percentage, residual guarantee amount, OEC, and capital amount — are sourced from OKL_K_LINES_H. Status meaning is resolved through OKC_STATUSES_V, and asset identifiers originate from OKL_TXL_ASSETS_B on the transaction-asset branch and from the line NAME on the free-form branch.

Key Columns

• ID / CONTRACT_NUMBER – Header identity of the owning contract, carried from OKC_K_HEADERS_B (aliased HDR).
• ASSET_NUMBER – The asset identifier, derived from TOP_LINE.NAME on the free-form branch or TXLA.ASSET_NUMBER on the asset branch.
• PARENT_LINE_ID – The parent line reference (TOP_LINE.ID or TXLA.KLE_ID), used to relate a version row to its originating line.
• DESCRIPTION – Line item description text, resolved through the translated lines source.
• CURRENT_UNITS – The number of items currently associated with the line, from CIM.NUMBER_OF_ITEMS.
• LINE_STATUS / ASSET_STATUS – The line status code (STS_CODE) and its decoded meaning (STS.MEANING) from OKC_STATUSES_V.
• MAJOR_VERSION – The version indicator; the view joins consistently on MAJOR_VERSION across line, item, and KLE sources to align rows to a single version.
• Residual and capital measures – NVL-guarded columns for RESIDUAL_VALUE, RESIDUAL_PERCENTAGE, RESIDUAL_GRNTY_AMOUNT, OEC, and CAPITAL_AMOUNT, all defaulting to 0 when null.
• CURRENCY_CODE – The contract currency from the header.

Common Use Cases and Queries

The view is typically used for asset-level leasing reports, line version comparisons, and downstream extraction into data warehouses. A basic listing of line versions for a contract can be produced as follows:

SELECT id, contract_number, asset_number, parent_line_id, description, current_units, line_status, asset_status, major_version, currency_code FROM apps.okl_cs_line_version_uv WHERE contract_number = :p_contract_number ORDER BY parent_line_id, major_version;

To aggregate residual and capital exposure by asset, consumers can sum the NVL-guarded financial columns grouped by asset_number and contract_number. Because the view is a UNION with DISTINCT semantics and joins on MAJOR_VERSION, results represent one row per distinct line version; callers filtering on a specific version should constrain MAJOR_VERSION explicitly to avoid mixing versions. In integration scenarios the view is commonly the source for extracts that reconcile OKC line structures with OKL asset records, and its reliance on OKC_K_LINES_HV and OKC_STATUSES_V means it should be queried as a reporting object only, with no expectation of DML support.