Search Results csi_ctr_prop_template_vl




Overview
Explore in AI Chat

Overview

CSI_CTR_PROP_TEMPLATE_VL is a language-enabled (VL) view in the Oracle E-Business Suite Install Base (CSI) module. It presents translated counter property template definitions used to describe the configurable properties of counters that are tracked against install base instances. Counters represent measurable quantities associated with a customer asset — such as meter readings, usage volumes, or cycle counts — and each counter can be associated with a property template that defines the type, format, and validation rules for the values collected against it.

The view resolves the language-specific name and description from the translation table and joins them to the base definition table, exposing a single logical row per counter property for the session language. Because it filters translation rows using USERENV('LANG'), the view automatically returns the display text appropriate to the current runtime language, which makes it suitable for concurrent programs, OAF pages, and custom reports that must respect the locale of the executing user. The object is owned by the APPS schema and is documented as valid in both EBS 12.1.1 and 12.2.2.

Underlying Base Objects

The view is defined over two documented base objects:

  • CSI_CTR_PROPERTY_TEMPLATE_B — the base (non-translated) table holding the physical definition of each counter property, including data type, LOV type, nullability, default, minimum and maximum values, unit of measure, effective dates, and descriptive flexfield attributes. This table carries the primary key COUNTER_PROPERTY_ID.
  • CSI_CTR_PROPERTY_TEMPLATE_TL — the translation table storing the language-specific NAME and DESCRIPTION keyed by COUNTER_PROPERTY_ID and LANGUAGE.

The view joins these two objects on COUNTER_PROPERTY_ID and constrains the translation row to the current session language via the USERENV('LANG') predicate. Because the B table supplies all structural attributes and the TL table supplies only the display text, the view combines both into a single denormalized presentation layer. Both objects are referenced in the ETRM metadata as synonyms resolved through the APPS schema.

Key Columns

Common Use Cases and Queries

Typical scenarios include validating configuration during counter setup, reporting on property definitions available for a given counter, and integrating counter metadata with external metering systems. The following query retrieves all active properties for a specific counter in the session language:

SELECT counter_property_id, name, property_data_type, uom_code, minimum_value, maximum_value FROM csi_ctr_prop_template_vl WHERE counter_id = :p_counter_id AND TRUNC(SYSDATE) BETWEEN NVL(start_date_active, SYSDATE) AND NVL(end_date_active, SYSDATE) ORDER BY name;

Because the view is already language-filtered, it should be preferred over querying the _B and _TL tables directly in user-facing reporting. Developers building custom OAF pages or concurrent programs that display counter property templates can rely on the view to provide translated text without additional join logic or explicit language handling.