Search Results net_reading

Overview

CS_CP_COUNTERS_V is a Service (CS) module reporting view in Oracle E-Business Suite 12.1.1 and 12.2.2. As stated in the ETRM metadata, it "contains the information pertaining to counters (values, groups)." In the Oracle TeleService and depot repair model, counters represent cumulative or stepped meter readings taken against a customer product — for example, the number of copies produced by a copier, hours logged on an engine, or cycles recorded on capital equipment. This view consolidates counter definition data with the transactional readings captured for each counter, and enriches the result with customer product and inventory item context.

The view is intended primarily for reporting, inquiry, and integration rather than for transactional processing. Its most notable computed attribute is NET_READING, which normalizes a raw counter reading by subtracting miscellaneous usage and prior-period adjustments, and by reconciling readings that span a counter reset. Because the view joins counter values, counter definitions, counter groups, customer products, and item master information in a single row, it removes the burden of reconstructing this five-way join in ad hoc queries.

Underlying Base Objects

The ETRM record lists no separately documented base objects, but the view text itself identifies the following sources:

• CS_COUNTERS — the counter definition (name, description, unit of measure, step value, tolerances, rollover bounds, active dates).
• CS_COUNTER_VALUES — the individual readings, including COUNTER_READING, VALUE_TIMESTAMP, reset attributes, and sequence number.
• CS_COUNTER_GROUPS — the grouping construct; the join is restricted to groups whose SOURCE_OBJECT_CODE is 'CP'.
• CS_CUSTOMER_PRODUCTS — the installed base instance the counter belongs to, supplying serial number, lot number, and reference number.
• MTL_SYSTEM_ITEMS_KFV — the item flexfield view, supplying the concatenated product name and description; the organization is resolved through CS_STD.GET_ITEM_VALDN_ORGZN_ID.

The join between CS_COUNTERS and CS_COUNTER_VALUES is an outer join on both COUNTER_ID and the maximum sequence number (CTR_VAL_MAX_SEQ_NO), so counters without readings are still returned.

Key Columns

• NET_READING — the derived, adjusted reading computed through DECODE on RESET_FLAG; this is the value most consumers want.
• COUNTER_READING — the raw captured reading prior to adjustment.
• COUNTER_ID, COUNTER_GROUP_ID, COUNTER_VALUE_ID, COUNTER_GRP_LOG_ID — primary and foreign keys linking the reading to its definition and group.
• NAME, DESCRIPTION — the counter identity as defined on CS_COUNTERS.
• VALUE_TIMESTAMP, SEQ_NO — when the reading was taken and its order within the counter's history.
• RESET_FLAG, RESET_REASON, PRE_RESET_LAST_RDG, POST_RESET_FIRST_RDG — reset context required to interpret cumulative readings.
• MISC_READING, MISC_READING_TYPE, PREV_NET_CURR_DIFF — components subtracted when deriving NET_READING.
• INITIAL_READING, STEP_VALUE, UOM_CODE, TOLERANCE_PLUS, TOLERANCE_MINUS, ROLLOVER_LAST_READING, ROLLOVER_FIRST_READING — unit and validation attributes of the counter.
• CUSTOMER_PRODUCT_ID, SERIAL_NUMBER, LOT_NUMBER, REFERENCE_NUMBER, PRODUCT_NAME, PRODUCT_DESCRIPTION — installed-base and item context.
• Standard WHO columns (CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_BY) and ATTRIBUTE1–15 with CONTEXT.

Common Use Cases and Queries

Typical uses include meter-based billing and warranty verification, preventive maintenance scheduling, usage trend reporting, and extracting counter history into a data warehouse. A search for "net_reading" indicates the analyst is looking for adjusted usage rather than raw readings, which is precisely what this view provides.

Latest adjusted reading per customer product:

• SELECT customer_product_id, serial_number, name, net_reading, value_timestamp FROM cs_cp_counters_v WHERE sequence_no = (SELECT MAX(sequence_no) FROM cs_cp_counters_v b WHERE b.counter_id = cs_cp_counters_v.counter_id);

Readings consumed within a date range for a given installed base:

• SELECT serial_number, product_name, name, net_reading, value_timestamp FROM cs_cp_counters_v WHERE customer_product_id = :p_cp_id AND value_timestamp BETWEEN :p_from AND :p_to ORDER BY value_timestamp;

Identifying counters that have been reset, so that NET_READING logic can be audited:

• SELECT counter_id, name, reset_reason, pre_reset_last_rdg, post_reset_first_rdg, counter_reading, net_reading FROM cs_cp_counters_v WHERE reset_flag = 'Y';

Because the view is not implemented as a database object in some instances (as the metadata notes), deployments should verify object validity in their environment before referencing it in concurrent programs or interface extracts.