Results for “okl_cs_cont_assets_uv”

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

Overview

OKL_CS_CONT_ASSETS_UV is a read-only reporting view owned by the APPS schema in Oracle E-Business Suite Release 12.1.1 and 12.2.2. It belongs to the OKL (Leasing and Finance Management) product family and presents contract-linked asset information by joining lease contract headers to their associated asset lines. The view is intended for inquiry, reporting, and integration scenarios where a denormalized, flattened picture of "which assets belong to which contract" is required without navigating the underlying entity relationships directly. Because it is defined over other views (OKC_K_HEADERS_V and OKL_CS_ASSET_LINES_V), it carries no data of its own and inherits the security and validation logic of those sources. The status of the object is VALID, and it is flagged in the ETRM documentation as Oracle proprietary and confidential.

Underlying Base Objects

The view text exposes a two-table join between the contract header view and the asset lines view, filtered and ordered for presentation:

• OKC_K_HEADERS_V (VIEW) — supplies the contract identity (ID and contract number) from the contract headers source; aliased as CHR in the defining query.
• OKL_CS_ASSET_LINES_V (VIEW) — supplies asset-level attributes (asset number, serial number, model number, description, asset ID, and registration organization), aliased as ALV.
• OKC_UTIL (PACKAGE) — referenced as an underlying dependency by the OKL asset lines view, providing shared contract utility logic.

The join predicate links ALV.DNZ_CHR_ID = CHR.ID, with a filter excluding contracts whose status code equals ABANOINED (an aborted/annulled style status). Results are ordered by contract ID. This means the view returns one row per qualifying asset line per contract, and any contract carrying the excluded status is suppressed entirely.

Key Columns

• CONTRACT_ID — internal identifier of the lease contract (CHR.ID); the primary join key and ordering column.
• CONTRACT_NUMBER — the user-facing contract number from the headers view.
• ASSET_NUMBER — the inventory or asset number of the leased asset.
• SERIAL_NUMBER — the manufacturer serial number, useful for physical asset reconciliation.
• MODEL_NUMBER — the model designation of the asset; this is the column most commonly searched by users seeking "model_number" context.
• ASSET_DESCRIPTION — descriptive text for the asset.
• ASSET_ID — the internal asset identifier, used for joins back to asset master tables.
• REGISTRATION — mapped from ALV.ORG_ID, indicating the operating unit or registration organization context.

Common Use Cases and Queries

Typical uses include contract-to-asset reporting, asset inventory reconciliation, and integration extracts feeding data warehouses or external asset tracking systems. A frequent pattern is locating all assets of a given model across contracts:

• SELECT contract_number, asset_number, serial_number, model_number FROM okl_cs_cont_assets_uv WHERE model_number = :model_number;
• SELECT contract_number, asset_number, registration FROM okl_cs_cont_assets_uv WHERE contract_number = :contract_number ORDER BY asset_number;
• SELECT model_number, COUNT(*) FROM okl_cs_cont_assets_uv GROUP BY model_number ORDER BY 2 DESC;

Because the view is pre-filtered to exclude aborted contracts and to return only rows with a matching asset line, reports built on it will not surface contracts lacking assets. For completeness checks, the constituent views should be queried directly.