Search Results reset_mode

Overview

CSI_COUNTER_READINGS_BC_V is a backward-compatibility view owned by the APPS schema in Oracle E-Business Suite, belonging to the CSI (Install Base) product family. Its documented purpose is to expose the column layout historically associated with counter reading data so that legacy customizations, reports, and integrations written against the older CS_COUNTER_VALUES interface continue to function after the underlying data model was consolidated into the CSI_COUNTER_READINGS table. The view is recorded in ETRM 12.2.2 as VALID, and the underlying object organization is identical between 12.1.1 and 12.2.2, so the same operational characteristics apply to both releases.

The view performs several column renames and derived calculations rather than acting as a pure projection. This makes it a translation layer: consumers reference familiar column names, while the database resolves them to modern columns and, for certain fields, to PL/SQL function calls against the CSI_COUNTER_READINGS_PVT package. The VALUE_TIMESTAMP column, which is the term most frequently searched in connection with this object, is passed straight through from the base table and retains its original name and semantics.

Underlying Base Objects

The view is defined over two documented referenced objects: the synonym CSI_COUNTER_READINGS, which resolves to the base table holding the current counter reading data, and the package CSI_COUNTER_READINGS_PVT, which supplies the GET_READING_BEFORE_RESET function used in the derived columns. No other tables or views participate in the definition.

• CSI_COUNTER_READINGS — primary data source; all persisted columns, including VALUE_TIMESTAMP, COUNTER_READING, RESET_MODE, and the descriptive flexfield attributes, are selected directly from this object.
• CSI_COUNTER_READINGS_PVT — invoked once, inside a DECODE expression, to retrieve the reading that preceded a reset for the affected counter and timestamp combination.

Because the view references a package function, it is not a simple read-only projection over one table; the package must be valid and accessible in the APPS schema for queries against PRE_RESET_LAST_RDG and POST_RESET_FIRST_RDG to succeed.

Key Columns

• COUNTER_VALUE_ID / COUNTER_ID — primary identifiers linking the reading to its parent counter definition.
• VALUE_TIMESTAMP — the effective date and time of the reading. It is the principal column for time-based filtering, ordering, and interval analysis of counter consumption.
• COUNTER_READING / MISC_READING — the recorded counter value and any associated miscellaneous or adjustment reading (formerly ADJUSTMENT_READING).
• RESET_FLAG / RESET_REASON — RESET_FLAG is derived by DECODE on RESET_MODE, returning 'N' for a null reset mode and 'Y' otherwise.
• PRE_RESET_LAST_RDG / POST_RESET_FIRST_RDG — computed values, both null when RESET_MODE is null; these support reset-boundary reconciliation.
• CONTEXT and ATTRIBUTE1–15 — the descriptive flexfield segment mapping, with ATTRIBUTE_CATEGORY aliased to CONTEXT.
• COUNTER_GRP_LOG_ID / VALID_FLAG — aliases of TRANSACTION_ID and DISABLED_FLAG respectively, retained for backward compatibility.
• WHO columns — CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, LAST_UPDATED_BY, and LAST_UPDATE_LOGIN.

Common Use Cases and Queries

Typical usage centers on historical consumption reporting and integration extracts. A frequent pattern retrieves the latest reading per counter within a date window using VALUE_TIMESTAMP:

• Consumption reporting — ordering readings by VALUE_TIMESTAMP to derive meter deltas between periods.
• Reset reconciliation — selecting PRE_RESET_LAST_RDG and POST_RESET_FIRST_RDG where RESET_FLAG = 'Y'.
• Legacy interface feeds — extracting ATTRIBUTE columns and CONTEXT for downstream systems expecting the original CS_COUNTER_VALUES layout.

Sample query:

• SELECT counter_id, value_timestamp, counter_reading FROM csi_counter_readings_bc_v WHERE value_timestamp BETWEEN :p_start AND :p_end ORDER BY counter_id, value_timestamp;

Because the derived columns call the package function, queries restricted to non-derived columns such as VALUE_TIMESTAMP avoid that overhead and generally perform better in high-volume reporting.