Search Results okl_cs_asset_counters_uv




Overview
Explore in AI Chat

Overview

OKL_CS_ASSET_COUNTERS_UV is a read-only database view owned by the APPS schema in Oracle E-Business Suite releases 12.1.1 and 12.2.2. It is delivered as part of the OKL – Lease and Finance Management product family and presents a consolidated picture of asset-level meter or counter readings associated with lease contract lines. The view joins contract header and line data from the OKC contract tables to installed asset instances, counter definitions, and the most recent counter readings held in the CS (Customer Service / Enterprise Asset Management) counter tables.

Its principal role is reporting and integration. Lease contracts frequently contain assets that carry usage meters—hours, miles, cycles, and similar measures—that drive billing, term extensions, or residual calculations. Rather than requiring report authors to reconstruct the multi-level contract-to-asset path, OKL_CS_ASSET_COUNTERS_UV exposes the resolved relationship in a single object, along with the latest valid reading and its timestamp. The view is documented against both 12.1.1 and 12.2.2, and the same column set is expected on either release.

Underlying Base Objects

The view is defined over a set of joined base tables, synonyms, and supporting views. The contract side is sourced from OKC_K_HEADERS_B (which contributes CONTRACT_NUMBER and the header ID, aliased KHR_ID) and OKC_K_LINES_B, which appears four times as CLE1 through CLE4 to traverse the contract's line hierarchy. The line styles are resolved through OKC_LINE_STYLES_B (four aliases), with LTY_CODE values of FREE_FORM1, FREE_FORM2, and INST_ITEM driving the traversal. OKC_K_ITEMS supplies the item linkage.

The asset side is anchored by CSI_ITEM_INSTANCES, providing the serial number, quantity, and instance identifier. MTL_SYSTEM_ITEMS_VL and MTL_UNITS_OF_MEASURE_VL resolve the item description and unit of measure. Counter definitions come from CS_COUNTER_GROUPS and CS_COUNTERS, while the readings themselves are held in CS_COUNTER_VALUES. The FA_ADDITIONS_B table supplies the fixed asset number and asset ID. Leasing-specific numbering is supplied by OKL_CNTR_LVLNG_LNS_B and OKL_CNTR_LVLNG_GRPS_V, which provide CLL_ID and CLG_ID respectively. The package CSI_COUNTER_READINGS_PVT is also documented as a referenced object, supporting reading retrieval logic.

Key Columns

  • CONTRACT_NUMBER – Lease contract identifier from OKC_K_HEADERS_B, together with KHR_ID.
  • ASSET_NUMBER / ASSET_ID – Fixed asset identification from FA_ADDITIONS_B.
  • SERIAL_NUMBER / QUANTITY – Installed instance details from CSI_ITEM_INSTANCES; ITEM_DESCRIPTION identifies the item.
  • COUNTER_NAME / COUNTER_ID – The specific meter defined on CS_COUNTERS; CONSOLIDATED_COUNTER_NAME provides the corresponding CS_COUNTER_GROUPS name.
  • LAST_READING_DATE / LAST_READING – The most recent counter reading and its timestamp. The view restricts results to the maximum VALUE_TIMESTAMP per counter, or returns rows where no reading exists.
  • UNIT_OF_MEASURE – UOM for the reading.
  • CLL_ID / CLG_ID – Lease leveling line and group identifiers from the OKL leveling tables.
  • PARENT_LINE_ID – The parent contract line, useful for hierarchical reporting.

Common Use Cases and Queries

Typical uses include reporting current meter positions for leased assets, reconciling billing based on usage, and driving depreciation or residual value logic where consumed usage is a factor.

A basic retrieval of the latest readings for a contract:

  • SELECT contract_number, asset_number, counter_name, last_reading, last_reading_date FROM okl_cs_asset_counters_uv WHERE contract_number = :contract_number ORDER BY asset_number, counter_name;

A query listing all counters on a given asset:

  • SELECT serial_number, counter_name, consolidated_counter_name, last_reading, unit_of_measure FROM okl_cs_asset_counters_uv WHERE asset_id = :asset_id;

Because the view is secured through the APPS schema and reflects standard EBS security, access is granted to responsibility-specific users. The user search term lse_id corresponds to the LSE_ID column on OKC_K_LINES_B, which appears only in the view definition's join predicates and is not exposed as an output column.