Search Results csi_ctr_properties_bc_v




Overview
Explore in AI Chat

Overview

CSI_CTR_PROPERTIES_BC_V is a backward-compatibility view owned by the APPS schema in Oracle E-Business Suite, defined under the CSI (Install Base) product. Its stated purpose is to expose counter property definitions in the same shape used by the legacy CS_COUNTER_PROPERTIES structure, allowing customer extensions, reports, and integrations written against older releases to continue functioning after the data model was reorganized around the CSI_CTR_PROP_TEMPLATE_VL and CSI_COUNTER_PROPERTIES_VL views. The view is documented as VALID in ETRM for 12.1.1 and 12.2.2.

The object presents one row per counter property, including data-typing and validation attributes. The column most frequently searched for, MAXIMUM_VALUE, is exposed directly by the view and carries the upper bound applicable to a numeric or comparable property when the property data type permits a range check.

Underlying Base Objects

ETRM documents the view as being defined over two referenced base objects:

  • CSI_COUNTER_PROPERTIES_VL — the current, translatable view over counter property definitions associated with actual counters.
  • CSI_CTR_PROP_TEMPLATE_VL — the current, translatable view over counter property templates, which seed property definitions on new counters.

The union structure reflects the migration path: property rows originating from templates carry the template attributes, while rows originating from counters carry the counter association. The view text further shows that certain legacy columns are populated as literal NULL to preserve the old column list, specifically CREATED_FROM_CTR_PROP_TMPL_ID, SOURCE_COUNTER_PROP_ID, and the CONTEXT alias mapped from ATTRIBUTE_CATEGORY. Because it is a union of translatable views, the view returns the language-appropriate NAME and DESCRIPTION for the effective session language.

Key Columns

Common Use Cases and Queries

Typical reporting needs include validating whether counter readings fall within configured bounds, reconciling property templates against instantiated counter properties, and driving downstream integrations that read property definitions. The MAXIMUM_VALUE column is central to bound checking.

List all bounded numeric properties for a counter:

  • SELECT counter_property_id, counter_id, name, property_data_type, default_value, minimum_value, maximum_value, uom_code FROM apps.csi_ctr_properties_bc_v WHERE counter_id = :counter_id AND maximum_value IS NOT NULL ORDER BY name;

Join property definitions to counter instances to test readings against the allowed range:

  • SELECT p.counter_id, p.name, r.reading_value, p.minimum_value, p.maximum_value FROM apps.csi_ctr_properties_bc_v p, apps.csi_counter_readings r WHERE p.counter_property_id = r.counter_property_id AND r.reading_value > p.maximum_value;

Because the view is a compatibility layer, new development should prefer the underlying CSI_COUNTER_PROPERTIES_VL and CSI_CTR_PROP_TEMPLATE_VL views, reserving CSI_CTR_PROPERTIES_BC_V for legacy code paths that depend on the CS_COUNTER_PROPERTIES column signature.