Search Results net_reading




Overview

CSI_CP_COUNTERS_V is a backward-compatibility view owned by the APPS schema in Oracle E-Business Suite Release 12.1.1 and 12.2.2. It belongs to the CSI – Install Base product family and exposes customer product counter data. The view is documented in ETRM as "Backward Compatible: Customer Product Counters," indicating that it preserves an earlier interface contract—commonly relied upon by legacy reports, integrations, and custom extensions—while the underlying physical model evolved to the multi-lingual CSI_COUNTERS_VL and CSI_COUNTER_READINGS structures.

Functionally, the view presents the definition of a counter attached to a customer product instance alongside its last or current reading. Because it flattens counter master data, counter readings, item instance attributes, and item master descriptions into one row per counter value, it serves as a convenient reporting and integration surface without requiring callers to join the individual base objects themselves. Its aliases (for example, COUNTER_DESCRIPTION, COUNTER_NAME, CUSTOMER_PRODUCT_ID) reflect the naming conventions of the pre-R12 counter interface, which is the primary reason the view is retained and flagged as valid in the ETRM catalog.

Underlying Base Objects

ETRM documents the following referenced objects for the 12.2.2 definition:

  • CSI_COUNTERS_VL (VIEW) — the multi-lingual counter definition view, supplying counter name, description, type, unit of measure, tolerance thresholds, rollover values, formula incomplete flag, and effective dates.
  • CSI_COUNTER_READINGS (SYNONYM) — the transactional counter reading table, supplying reading values, timestamps, reset and adjustment information, and the DFF attribute columns.
  • CSI_COUNTER_ASSOCIATIONS (SYNONYM) — the association between counters and instances, referenced in the relationship that links counter definitions to customer product instances.
  • CSI_ITEM_INSTANCES (SYNONYM) — the install base instance table, providing INSTANCE_ID (exposed as CUSTOMER_PRODUCT_ID), instance number (exposed as REFERENCE_NUMBER), serial number, and lot number.
  • MTL_SYSTEM_ITEMS_KFV (SYNONYM) — the item key flexfield view, providing the concatenated segments and description exposed as PRODUCT_NAME and PRODUCT_DESCRIPTION.

The view text joins CSI_COUNTERS_VL, CSI_COUNTER_READINGS, CSI_ITEM_INSTANCES, and the item key flexfield view, projecting NVL(CV.COUNTER_READING, C.INITIAL_READING) as the effective counter reading and deriving RESET_FLAG via DECODE on the reset mode. It therefore behaves as a denormalized read layer over the counter and install base model rather than storing any data itself.

Key Columns

Common Use Cases and Queries

The view is typically used to report counter history and current readings per installed product, to reconcile readings against item instances, and to feed downstream integrations that still expect the legacy column names. A representative query listing counters and their latest readings for a given instance follows:

  • SELECT customer_product_id, reference_number, serial_number, counter_name, counter_description, counter_reading, net_reading, uom_code, value_timestamp FROM csi_cp_counters_v WHERE reference_number = :instance_number ORDER BY counter_name, value_timestamp DESC;
  • SELECT product_name, product_description, counter_name, counter_reading, tolerance_plus, tolerance_minus FROM csi_cp_counters_v WHERE counter_reading > tolerance_plus; — identifies readings that exceed configured upper tolerances.
  • SELECT counter_name, counter_description, COUNT(*) FROM csi_cp_counters_v WHERE reset_flag = 'Y' GROUP BY counter_name, counter_description; — summarizes reset activity by counter.
  • SELECT reference_number, serial_number, counter_name, counter_reading FROM csi_cp_counters_v WHERE uom_code = :uom AND value_timestamp >= :from_date; — supports period-based reading extracts.

Because the view derives the effective reading with NVL and sources attributes from four distinct base objects, queries against it can be resource-intensive on large install bases. Restricting predicates to instance identifiers, counter identifiers, or reading timestamps is advisable when using it for high-volume extracts. The view is read-only and should not be used as a target for DML; counter readings must be maintained through the Install Base counter APIs against the underlying tables.