Results for “okl_am_assets_uv”

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

Overview

The OKL_AM_ASSETS_UV view is a user-facing (UV) database object in the Oracle E-Business Suite (EBS) Leasing and Finance Management module (OKL), owned by the APPS schema. It presents a consolidated snapshot of leased assets alongside their parent contract attributes, enabling reporting and integration scenarios that require asset-level detail joined to contract-level context. The view is structurally tied to the OKL asset master data and the OKC contract data model, surfacing both asset identification fields (asset number, name, item description, status) and contract fields (contract number, contract status, contract dates).

Because the view carries a CONTRACT_STATUS column, it is directly relevant to the search term contract_status: users querying this view gain access to the lifecycle state of the governing contract without needing to manually join the asset tables to the contract headers table. This makes the view useful for status-driven reporting, dashboards, and downstream interfaces that need to filter or aggregate assets by their contract status.

Underlying Base Objects

The view is defined over the following documented base objects:

• OKC_K_LINES_V (VIEW) — aliased as OALV, the principal source of asset-related rows. It supplies asset ID, status, name, item description, line number, change request ID (CHR_ID), and the DNZ contract header reference (DNZ_CHR_ID).
• OKL_K_LINES (SYNONYM) — aliased as KLE, joined on OALV.ID = KLE.ID to supply the cost element value (KLE.OEC).
• OKC_K_HEADERS_B (SYNONYM) — aliased as OKHFV, the contract header base table joined on OKHFV.ID = OALV.DNZ_CHR_ID. It provides contract number, contract status code, contract start and end dates, and the contract ID.
• OKC_LINE_STYLES_B (SYNONYM) — aliased as LSE, used as a filter on LSE.LTY_CODE = 'FREE_FORM1' and joined via OALV.LSE_ID = LSE.ID.
• OKL_AM_UTIL_PVT (PACKAGE) — invoked as OKL_AM_UTIL_PVT.GET_ASSET_QUANTITY(OALV.ID) to derive the asset quantity.

The filter conditions enforce that the asset line style is FREE_FORM1, that the asset's status code matches the contract header status code, and that abandoned assets (STS_CODE <> 'ABANDONED') are excluded.

Key Columns

• ASSET_ID / ID / ID2 — Asset identifier fields; ID2 is a literal placeholder ('#').
• STATUS — The asset's status code (OALV.STS_CODE).
• ASSET_NUMBER / NAME — Asset name/number used for identification in reports.
• ITEM_DESCRIPTION / DESCRIPTION — Descriptive text for the asset item.
• CONTRACT_STATUS — The status code of the associated contract header (OKHFV.STS_CODE), the column relevant to contract_status searches.
• CONTRACT_NUMBER / CONTRACT_ID — Contract header identity fields.
• START_DATE / END_DATE — Contract-level dates from the header.
• START_DATE_ACTIVE / END_DATE_ACTIVE / DATE_TERMINATED — Asset-level active and termination dates.
• DNZ_CHR_ID / CHR_ID — Change request identifiers linking asset and contract header.
• LINE_NUMBER — Line identifier within the contract structure.
• COST — Cost figure derived from the OKL line (KLE.OEC).
• QUANTITY — Asset quantity computed via the OKL utility package.
• EFFECTIVE_FROM — Set to SYSDATE.
• SPLIT_KLE_NAME — Null placeholder column.

Common Use Cases and Queries

A frequent scenario is reporting assets by their contract status — for example, identifying all active leased assets. The following query illustrates the pattern:

• Assets by contract status:

SELECT ASSET_NUMBER, NAME, CONTRACT_NUMBER, CONTRACT_STATUS, COST, QUANTITY
FROM   APPS.OKL_AM_ASSETS_UV
WHERE  CONTRACT_STATUS = 'ACTIVE';

Other practical uses include joining the view to contract master views for enriched reporting, aggregating cost and quantity by contract, and using it as a source for asset-level extract files. Because the view exposes both asset and contract attributes in a single row, it reduces the join complexity typically required between OKL asset tables and OKC contract headers, making it well-suited to ad hoc queries and lightweight integration extracts.