Search Results adjustment_reading

Overview

CSI_COUNTER_READINGS_V is a read-only database view owned by the APPS schema within the Oracle E-Business Suite Install Base module (CSI). It consolidates counter definition attributes from the counter header with individual meter or counter readings recorded against those counters. The view is valid in both EBS 12.1.1 and 12.2.2 and functions as the primary reporting and integration surface for counter reading data, exposing a denormalized row per reading that joins setup metadata (counter name, unit of measure, reading type, rollover boundaries) directly to transactional values.

Because readings drive warranty entitlement, preventive maintenance scheduling, service contract billing, and usage-based charge calculations, this view is frequently consumed by reports, Oracle Discoverer workbooks, BI Publisher data templates, and inbound/outbound interface programs. Its denormalized shape removes the need for report developers to re-create the join between the counter definition and the reading table.

Underlying Base Objects

The view is documented as being defined over the following objects: CSI_COUNTERS_VL (a view), CSI_COUNTER_READINGS (exposed through a synonym), and CSI_COUNTER_READINGS_PVT (a package that performs maintenance logic against the underlying reading table). CSI_COUNTERS_VL supplies the counter definition portion — name, description, initial reading, reading type, UOM, direction, counter type, rollover limits, and customer/filter configuration. CSI_COUNTER_READINGS supplies the transactional portion — the counter value identifier, counter identifier, value timestamp, the actual counter reading, and reset/adjustment information.

The presence of CSI_COUNTER_READINGS_PVT indicates that inserts and updates are not performed directly on this view; the private package API is the supported write path, and the view is intended strictly for query access.

Key Columns

• COUNTER_VALUE_ID — unique identifier of the individual reading row.
• COUNTER_ID — foreign key linking the reading to its counter definition.
• COUNTER_NAME / COUNTER_DESCRIPTION — human-readable identity of the counter.
• COUNTER_READING — the recorded value captured at VALUE_TIMESTAMP.
• VALUE_TIMESTAMP — the effective date/time of the reading; central to chronological ordering and trend reporting.
• INITIAL_READING, READING_TYPE, UOM_CODE, DIRECTION — the baseline value, the nature of the reading (for example absolute versus periodic), the unit of measure, and whether the counter increments or decrements.
• ROLLOVER_LAST_READING / ROLLOVER_FIRST_READING — the upper and lower boundaries at which a mechanical or software counter wraps.
• RESET_MODE and RESET_REASON — these columns, returned from CSI_COUNTER_READINGS, are the attributes most relevant to users searching on reading_before_reset, since they describe the circumstances under which a counter was reset and therefore when a prior baseline no longer applies.
• ADJUSTMENT_TYPE / ADJUSTMENT_READING — indicate corrective adjustments applied to the counter.
• ATTRIBUTE_CATEGORY and ATTRIBUTE1 through ATTRIBUTE30 — the standard EBS descriptive flexfield segment columns, enabling client-specific extensibility.
• OBJECT_VERSION_NUMBER, CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN — the standard EBS auditing columns.
• CUSTOMER_VIEW, FILTER_TYPE, FILTER_TIME_UOM, GROUP_ID — counter configuration controlling visibility and aggregation grouping.

Common Use Cases and Queries

Typical scenarios include meter trending for a specific installed base instance, identifying counters that were reset during a period for warranty or billing exception review, and validating the last reading captured against a contract entitlement. A standard query joining the view to the install base instance hierarchy is shown below.

• Retrieve the latest reading per counter for a customer-facing report.
• Audit readings where RESET_MODE or RESET_REASON is populated to identify baseline discontinuities, which is the practical answer to a search on reading_before_reset.
• Feed usage data into service contract or maintenance work order processes.

Example SQL:

SELECT counter_name, counter_reading, value_timestamp, reset_mode, reset_reason
FROM csi_counter_readings_v
WHERE counter_id = :counter_id
ORDER BY value_timestamp DESC;

Because the view applies no row-level security beyond the underlying tables, standard EBS Multi-Org and security predicates against the Install Base entity should be applied by the consuming report or interface.