Search Results value_timestamp




Overview
Explore in AI Chat

Overview

APPS.CSI_COUNTER_READINGS_BC_V is a Business Component (BC) view within the Oracle E-Business Suite Customer Intelligence / Installed Base (CSI) module. It presents counter reading data captured against tracked instances and counters, exposing a flattened, business-friendly projection of the CSI_COUNTER_READINGS table. The view is intended for use by servicing, telemetry, and meter-management screens and by integration layer components that need to surface counter values without directly accessing the base entity table.

In EBS 12.1.1 and 12.2.2 the view is defined for APPS and is commonly consumed through the Oracle Application Framework (OAF) or through PL/SQL APIs that reference the CSI_COUNTER_READINGS_PVT package. Its naming convention (_BC_V) identifies it as a Business Component view, meaning it is designed to support entity object queries and validation logic rather than ad-hoc operational reporting, though it is frequently used for both.

Underlying Base Objects

The view is defined directly over the synonym CSI_COUNTER_READINGS, which resolves to the physical counter readings table. It additionally references the package CSI_COUNTER_READINGS_PVT, whose functions are invoked inside the SELECT list to derive calculated columns.

  • CSI_COUNTER_READINGS — the primary source of counter value rows, including the reading, timestamp, adjustment and reset metadata, and descriptive flexfield attributes.
  • CSI_COUNTER_READINGS_PVT — supplies GET_READING_BEFORE_RESET, which returns the last reading prior to a reset, and GET_PREVIOUS_NET_READING, which returns the prior net reading for the same counter. Both are resolved per COUNTER_ID and VALUE_TIMESTAMP.

Because two function calls execute for every row returned, the view is not a simple projection and can be costly against counters with large reading histories.

Key Columns

Common Use Cases and Queries

The view is used to reconstruct meter and counter consumption, particularly where resets or adjustments must be accounted for. A typical query lists ordered readings for a counter:

SELECT counter_id, value_timestamp, counter_reading,
       net_reading, prev_net_reading, reset_flag
FROM   apps.csi_counter_readings_bc_v
WHERE  counter_id = :p_counter_id
ORDER  BY value_timestamp;

Integration components query the view to publish latest readings to external telemetry systems, filtering on VALUE_TIMESTAMP to return only recent values. Analysts use PRE_RESET_LAST_RDG and POST_RESET_FIRST_RDG to explain discontinuities in consumption reports, and NET_READING minus PREV_NET_READING to compute incremental usage. Because the derived columns depend on package function calls, restricting by COUNTER_ID and a bounded VALUE_TIMESTAMP range materially improves performance.