Search Results csi_counters_vl




Overview
Explore in AI Chat

Overview

CSI_COUNTERS_VL is a language (translation) view owned by the APPS schema within the CSI — Install Base product of Oracle E-Business Suite. Its documented purpose is to expose counter instance definitions together with their language-dependent descriptive attributes. In the ETRM metadata for 12.2.2 the object is registered with owner APPS and status VALID. The view combines the non-translated counter definition rows held in the base table CSI_COUNTERS_B with the translated name and description text held in CSI_COUNTERS_TL. The "_VL" suffix is the conventional Oracle EBS naming pattern for a view that presents a base ("_B") entity joined to its translation ("_TL") table, typically resolving to the session language so that consumers see descriptions in the appropriate language.

The view therefore plays a dual role: it is the primary read interface for reporting on counters (such as meter or usage counters attached to installed base instances) and it is a convenient integration and inquiry source where multilingual name and description values are required without an explicit join in the calling code.

Underlying Base Objects

The documented referents of the view are two synonyms: CSI_COUNTERS_B and CSI_COUNTERS_TL.

  • CSI_COUNTERS_B — the base table holding the language-independent counter definition attributes. The view text selects from this table (aliased CCB) the full set of functional and descriptive columns, including COUNTER_ID, GROUP_ID, COUNTER_TYPE, INITIAL_READING, STEP_VALUE, tolerances, unit of measure, derivation and formula information, rollover readings, usage item, activity dates, the standard WHO columns, the OBJECT_VERSION_NUMBER, and the thirty descriptive flexfield (DFF) attribute columns ATTRIBUTE1 through ATTRIBUTE30.
  • CSI_COUNTERS_TL — the translation table (aliased CCT). The view takes NAME and DESCRIPTION from this table, supplying the language-specific text for each counter definition. The join is made on the counter identifier, and the translated rows are filtered to the appropriate language so that a single row is returned per counter in the current session language.

The view therefore does not introduce independent data; it is a read-only projection over the base and translation tables, and it inherits their key constraints and relationships.

Key Columns

Common Use Cases and Queries

Typical uses include reporting on counter definitions in the user's language, feeding integration extracts that require descriptive text, and validating counter setup (tolerances, units, formulas, and effective dates).

List active counters with translated text:

  • SELECT counter_id, name, description, counter_type, uom_code FROM apps.csi_counters_vl WHERE valid_flag = 'Y' ORDER BY name;

Retrieve a specific counter definition:

  • SELECT counter_id, name, initial_reading, step_value, tolerance_plus, tolerance_minus FROM apps.csi_counters_vl WHERE counter_id = :p_counter_id;

Identify derived counters with completed formulas:

  • SELECT counter_id, name, derive_function, formula_text FROM apps.csi_counters_vl WHERE derive_counter_id IS NOT NULL AND formula_incomplete_flag = 'N';

Filter by effective dates to find currently valid definitions:

  • SELECT counter_id, name, start_date_active, end_date_active FROM apps.csi_counters_vl WHERE SYSDATE BETWEEN NVL(start_date_active, SYSDATE) AND NVL(end_date_active, SYSDATE);

Because the view resolves language automatically, it is preferred over joining CSI_COUNTERS_B and CSI_COUNTERS_TL directly in application queries and reports.