Results for “counter_type”

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

Overview

OKL_BPD_CNTR_READING_UV is an APPS-owned database view within the Oracle E-Business Suite OKL (Leasing and Finance Management) product family. It presents counter reading information associated with contract usage lines, joining contract header, contract line, asset, counter, and unit-of-measure data into a single denormalized projection. In practice, the view serves reporting and integration consumers who need to see, for a given contract, which physical or logical counters (such as odometer or hour-meter devices) apply to which leased assets, together with the counter type, unit of measure, serial number, and effective date range.

The view is registered as VALID in the APPS schema and follows the standard OKL "_UV" naming convention for user views intended to flatten the underlying normalized OKC/OKL contract model. Because it resolves counter-type information directly, it is frequently encountered during investigations of the counter_type attribute in leasing contracts.

Underlying Base Objects

The view is defined over a mix of synonyms and views. The documented base objects are:

• CS_COUNTERS (SYNONYM) – source of counter number, counter name, and the CN.TYPE column exposed as COUNTER_TYPE.
• MTL_UNITS_OF_MEASURE_TL (SYNONYM) – translation table supplying the unit-of-measure description, filtered by the session language.
• OKC_K_HEADERS_B (SYNONYM) – contract header, providing CONTRACT_NUMBER.
• OKC_K_LINES_B (SYNONYM) – referenced repeatedly to disambiguate usage, OKS, asset, and asset-line rows.
• OKC_K_ITEMS (SYNONYM) – the polymorphic junction records linking lines to objects such as OKL_USAGE, OKX_COVASST, and OKX_COUNTER.
• OKC_K_LINES_TL (SYNONYM) – translated asset number.
• OKL_CNTR_LVLNG_GRPS_V, OKL_CNTR_LVLNG_LNS_V, OKX_ASSETS_V (VIEW) – counter-leveling group and line definitions and the asset master, supplying asset number, serial number, and description.

Joins are driven through JTOT_OBJECT1_CODE discriminators ('OKL_USAGE', 'OKX_COVASST', 'OKX_COUNTER') and OBJECT1_ID2 = '#' markers typical of the OKC object model.

Key Columns

• ID / CLG_ID – identifier of the counter-leveling group record.
• COUNTER_GROUP – name of the counter-leveling group.
• COUNTER_NUMBER, COUNTER_NAME – counter identity and description.
• COUNTER_TYPE – the classification of the counter (CN.TYPE), the attribute most often queried.
• CONTRACT_NUMBER, ASSET_NUMBER, ASSET_SERIAL_NUMBER, ASSET_DESCRIPTION – contract and asset context.
• EFFECTIVE_DATE_FROM, EFFECTIVE_DATE_TO – validity window of the counter group assignment.
• UNIT_OF_MEASURE – the counter's measurement unit, translated by language.

Common Use Cases and Queries

Typical usage includes reconciling counters against contracts, auditing which counter types are attached to leased assets, and feeding downstream maintenance or billing logic.

SELECT contract_number, asset_number, counter_number,
       counter_name, counter_type, unit_of_measure
FROM   apps.okl_bpd_cntr_reading_uv
WHERE  counter_type = :p_type
AND    contract_number = :p_contract;

To list all counters for an asset serial number:

SELECT contract_number, counter_name, counter_type
FROM   apps.okl_bpd_cntr_reading_uv
WHERE  asset_serial_number = :p_serial;

Because COUNTER_TYPE is sourced from CS_COUNTERS.TYPE, consumers should validate that value against the counter type lookup before applying filters in production reports.