Search Results cs_counter_properties_v




Overview
Explore in AI Chat

Overview

CS_COUNTER_PROPERTIES_V is a Service (CS) module view owned by the APPS schema in Oracle E-Business Suite 12.1.1 and 12.2.2. It exposes the metadata that defines individual counter properties — the measurable attributes attached to a counter, such as a meter or usage gauge — together with their referenced unit of measure and list-of-values rendering. The view is a denormalized reporting layer: it joins the transactional counter-property definition table to units of measure and to FND lookups, resolves lookup codes into their displayed meanings, and returns a stable presentation of property constraints (data type, nullability, default, minimum/maximum, effective dates). Because the definition table is exposed through a view rather than accessed directly, Oracle EBS preserves a controlled read interface for reporting, concurrent programs, and external integrations that must inspect counter-property configuration without depending on physical table layout.

Underlying Base Objects

The view is defined over the following documented base objects:

The joins are all outer joins (B(+), C(+)), so a counter property is still returned when its unit of measure or lookup code is not resolvable. The SELECT applies DECODE to route DEFAULT_VALUE based on PROPERTY_LOV_TYPE: NULL type returns the stored default value directly, otherwise the lookup MEANING is returned as DEFAULT_VALUE, and A.DEFAULT_VALUE is separately exposed as DEFAULT_VALUE_CODE for lookup-driven properties.

Key Columns

  • COUNTER_PROPERTY_ID — primary identifier for the property definition; joins back to the base table.
  • COUNTER_ID — identifies the parent counter to which the property belongs.
  • NAME / DESCRIPTION — user-facing property name and description.
  • PROPERTY_DATA_TYPE — the data type governing valid property values.
  • IS_NULLABLE — flag indicating whether the property may be left unset.
  • DEFAULT_VALUE — the resolved default; contains the lookup MEANING when PROPERTY_LOV_TYPE is populated, otherwise the stored default.
  • DEFAULT_VALUE_CODE — the raw stored default value, exposed only when PROPERTY_LOV_TYPE is not null.
  • MINIMUM_VALUE / MAXIMUM_VALUE — permitted value range for numeric properties.
  • UOM_CODE / UNIT_OF_MEASURE — unit of measure code and its description.
  • PROPERTY_LOV_TYPE / PROPERTY_LOV_NAME — LOV lookup code and resolved meaning.
  • START_DATE_ACTIVE / END_DATE_ACTIVE — effective dating for the property definition.
  • ATTRIBUTE1–15 / CONTEXT — descriptive flexfield segments.
  • OBJECT_VERSION_NUMBER, LAST_UPDATE_DATE, LAST_UPDATED_BY, CREATION_DATE, CREATED_BY, LAST_UPDATE_LOGIN — standard auditing columns.

Common Use Cases and Queries

Typical scenarios include listing properties for a given counter, auditing which properties permit nulls, and reporting default and range constraints for integration mapping. Sample queries:

  • Properties for a counter: SELECT counter_property_id, name, property_data_type, is_nullable FROM cs_counter_properties_v WHERE counter_id = :counter_id;
  • Lookup-backed properties with resolved defaults: SELECT name, property_lov_name, default_value, default_value_code FROM cs_counter_properties_v WHERE property_lov_type IS NOT NULL;
  • Properties with units of measure: SELECT v.name, v.minimum_value, v.maximum_value, v.unit_of_measure FROM cs_counter_properties_v v WHERE v.uom_code IS NOT NULL;
  • Nullability audit: SELECT counter_id, name, is_nullable FROM cs_counter_properties_v ORDER BY counter_id, name;

Because the view resolves lookup meanings and units in a single pass, it is preferred over querying the base table directly for any report that must display human-readable default values or unit descriptions.