Search Results csi_counter_properties_vl




Overview
Explore in AI Chat

Overview

CSI_COUNTER_PROPERTIES_VL is a language-enabled (VL) view owned by the APPS schema within the Oracle E-Business Suite Install Base module (CSI). It exposes the user-facing attributes of counter properties defined against counters in the enterprise asset and install base model. A counter property represents a measurable or descriptive attribute associated with a counter — for example, a name, a data type, a default value, a unit of measure, and a valid operating range. The view joins the base table, which stores the language-independent property definition, to the translation table, which stores the language-dependent name and description. Filtering on the current session language ensures that consumers see only the textual attributes relevant to their locale.

Because it is a VL view, CSI_COUNTER_PROPERTIES_VL is the appropriate object for reports, concurrent programs, Discoverer workbooks, and integration extracts that must present counter property names and descriptions in the runtime language. Direct queries against the underlying _B table would return no translatable text, and queries against the _TL table alone would lack the operational attributes. This view therefore serves as the canonical read interface for counter property metadata in APPS.

Underlying Base Objects

The view is defined over two documented base objects, referenced through synonym definitions:

  • CSI_COUNTER_PROPERTIES_B — the base (language-independent) table holding the counter property identifier, counter reference, data type, nullability, default, minimum and maximum values, unit of measure, effective dates, object version number, WHO audit columns, descriptive flexfield attributes, migration flag, LOV type, security group, and the source counter property template identifier.
  • CSI_COUNTER_PROPERTIES_TL — the translation table supplying the NAME and DESCRIPTION columns keyed by COUNTER_PROPERTY_ID and LANGUAGE.

The join predicate links COUNTER_PROPERTY_ID across both tables and restricts rows to CCPT.LANGUAGE = USERENV('LANG'), the session language derived from the user environment. In Oracle EBS 12.1.1 and 12.2.2 the view resides in the APPS schema and is reported as VALID.

Key Columns

Common Use Cases and Queries

Typical uses include reporting counter property definitions by counter or counter template, validating property configuration against data type and range constraints, and extracting property metadata for integrations with condition monitoring or telemetry systems. The following query lists all active properties for a given counter:

SELECT counter_property_id, name, description, property_data_type,
  default_value, minimum_value, maximum_value, uom_code
FROM apps.csi_counter_properties_vl
WHERE counter_id = :p_counter_id
  AND TRUNC(SYSDATE) BETWEEN start_date_active AND NVL(end_date_active, TRUNC(SYSDATE));

A second common pattern inspects mandatory properties missing a default:

SELECT name, property_data_type, is_nullable
FROM apps.csi_counter_properties_vl
WHERE is_nullable = 'N' AND default_value IS NULL;

Because the view applies the USERENV('LANG') predicate internally, callers should not add their own language filters; doing so risks conflicting with the seeded translation row. Joining to CSI_COUNTERS_B on COUNTER_ID provides counter context when the report requires both counter and property detail.