Search Results property_lov_type




Overview
Explore in AI Chat

Overview

APPS.CSI_CTR_PROPERTIES_BC_V is a consolidated Oracle EBS view that exposes counter property definitions originating from two source entities: property templates and instantiated counter properties. The suffix "BC" denotes a business-component style view, indicating that it is intended to present a harmonized, denormalized shape suitable for programmatic consumption rather than a single normalized table. In practice, the view merges rows from CSI_CTR_PROP_TEMPLATE_VL (the template definition side) with rows from CSI_COUNTER_PROPERTIES_VL (the concrete counter-property instance side) through a UNION ALL, so that downstream consumers can query one source for both template-level and instance-level property metadata.

This view is significant in reporting and integration because it surfaces property definitions used by Oracle Installed Base (CSI) counter functionality, including data typing, nullability, default and range constraints, units of measure, and LOV behavior. The property_lov_type column, which users frequently search for, is exposed directly by this view, making it the natural access point when investigating how a counter property is presented in a list of values.

Underlying Base Objects

Per the documented ETRM metadata for 12.2.2, the view is defined over two referenced base objects:

  • CSI_COUNTER_PROPERTIES_VL (VIEW) — the VL (view language) representation of counter property instances.
  • CSI_CTR_PROP_TEMPLATE_VL (VIEW) — the VL representation of counter property templates.

Both underlying objects are themselves views, which typically join a base (_B/_TL) table pair to perform language-row filtering and translation resolution. The consolidation view performs a UNION ALL of the two, and for the template branch it projects NULL into CREATED_FROM_CTR_PROP_TMPL_ID and SOURCE_COUNTER_PROP_ID, indicating those connection columns exist only meaningfully on the instance side. The instance branch likewise supplies its own counter property identity. The union ensures a stable column list and preserves row provenance logic.

Key Columns

  • COUNTER_PROPERTY_ID and COUNTER_ID — the primary identity and owning counter of the property.
  • NAME and DESCRIPTION — user-facing labels resolved through the VL layer.
  • PROPERTY_DATA_TYPE — declared type (numeric, date, text, etc.) governing validation behavior.
  • IS_NULLABLE — indicates whether a value is mandatory for the counter property.
  • DEFAULT_VALUE, MINIMUM_VALUE, MAXIMUM_VALUE — default and boundary constraints.
  • UOM_CODE — unit of measure associated with numeric properties.
  • PROPERTY_LOV_TYPE — the list-of-values classification controlling how valid property values are presented or restricted; this is the column referenced by the search term "property_lov_type".
  • START_DATE_ACTIVE / END_DATE_ACTIVE — effective dating of the property definition.
  • ATTRIBUTE_CATEGORY (aliased as CONTEXT), ATTRIBUTE1..ATTRIBUTE15 — descriptive flexfield context and segments.
  • OBJECT_VERSION_NUMBER — optimistic locking token, useful when the view feeds OAF or REST integrations.
  • SECURITY_GROUP_ID — multi-org/security grouping used in access control.

Common Use Cases and Queries

The view is typically used to enumerate which properties exist for a counter, to validate property configuration before loading readings, or to investigate how the LOV type is defined for a given property. Because it merges template and instance rows, callers should filter by COUNTER_ID when they need instance-only data.

SELECT counter_property_id,
       counter_id,
       name,
       property_data_type,
       property_lov_type,
       is_nullable,
       uom_code
FROM   apps.csi_ctr_properties_bc_v
WHERE  counter_id = :p_counter_id
ORDER  BY name;

To find properties that permit a list-of-values but are not mandatory:

SELECT name, property_lov_type, default_value
FROM   apps.csi_ctr_properties_bc_v
WHERE  property_lov_type IS NOT NULL
AND    is_nullable = 'Y';

When integrating with counter reading transactions, the view provides the data type and range information needed to validate incoming values, and the OBJECT_VERSION_NUMBER supports concurrency-safe updates. Because it is a union of two VL views, performance is best when queries are constrained by COUNTER_ID or COUNTER_PROPERTY_ID, allowing the optimizer to push predicates into each branch.