Search Results property_lov_name




Overview
Explore in AI Chat

Overview

CS_CTR_CSXCTCCV_PROPERTY_V is a Service (CS) module database view that supports the CSXCTCCV Oracle E-Business Suite form. In EBS 12.1.1 and 12.2.2, CSXCTCCV is used to define, maintain, and display counter properties and their associated values. The view consolidates master property definitions from CS_COUNTER_PROPERTIES, the most recent captured property value from CS_COUNTER_PROP_VALUES, and lookup meaning metadata from FND_LOOKUPS. It presents a single, denormalized row per counter property, pairing the property definition with its latest effective value and, where applicable, a lookup display name.

Within reporting and integration contexts, the view functions as a read-only presentation layer. It is not a transactional entity and is not implemented as a stored database object in the documented environment; its definition is delivered as view text and instantiated at runtime or referenced by the form's supporting logic. The "_PROPERTY_V" suffix follows the EBS convention for a "values" or "validation" view tied to a specific form or business function. Because the view joins current property definitions against the sequence-selected latest value, it is well suited to queries that need the active configuration of a counter plus its most recent reading without writing additional aggregation logic.

Underlying Base Objects

The documented view text is defined over three base objects:

  • CS_COUNTER_PROPERTIES A — master table of counter property definitions, supplying name, description, data type, default value, minimum and maximum values, UOM, nullability, date ranges, and standard WHO/attribute columns.
  • CS_COUNTER_PROP_VALUES B — captured property values, outer-joined on COUNTER_PROPERTY_ID so that properties without a stored value still appear.
  • FND_LOOKUPS C — joined on PROPERTY_LOV_TYPE = C.LOOKUP_CODE and C.LOOKUP_TYPE = 'CS_COUNTER_PROPERTY_LOV', providing the lookup meaning used as the property LOV name.

The join to CS_COUNTER_PROP_VALUES is filtered to the latest value. A correlated subquery selects MAX(COUNTER_PROP_VALUE_ID) from CS_COUNTER_PROP_VALUES joined to CS_COUNTER_VALUES and CS_COUNTERS, constrained by N.SEQ_NO = O.CTR_VAL_MAX_SEQ_NO. This ensures the view returns the value associated with the maximum sequence number on the owning counter. The outer join to the latest value uses NVL(B.COUNTER_PROP_VALUE_ID, -1) so that properties lacking values resolve to the sentinel -1 and remain visible. ETRM lists no other referenced base objects.

Key Columns

  • COUNTER_PROPERTY_ID — primary identifier of the property definition; the principal join key.
  • COUNTER_ID — identifier of the owning counter.
  • PROPERTY_NAME / DESCRIPTION — display attributes of the property. The view text aliases A.NAME; the column list documents it as PROPERTY_NAME.
  • PROPERTY_VALUE / VALUE_TIMESTAMP — the most recent captured value and the time it was recorded.
  • PROPERTY_DATA_TYPE — governs interpretation and validation of the value.
  • DEFAULT_VALUE, MINIMUM_VALUE, MAXIMUM_VALUE, UOM_CODE, IS_NULLABLE — constraint and defaults metadata.
  • START_DATE_ACTIVE / END_DATE_ACTIVE — effective dating of the property definition.
  • PROPERTY_LOV_TYPE and PROPERTY_LOV_NAME — the lookup code and its translated meaning from FND_LOOKUPS.
  • DEFAULT_VALUE_CODE — a derived column returning A.DEFAULT_VALUE when PROPERTY_LOV_TYPE is NULL, otherwise NULL. This column is the subject of the user search "default_value_code": it exposes the property's default as a coded value only for non-LOV properties, distinguishing it from LOV-driven properties whose permissible values are defined by lookup.
  • OBJECT_VERSION_NUMBER — optimistic locking counter used by the form.
  • ROW_ID — retained ROWID of the base property row, supporting form block binding.
  • Standard WHO and ATTRIBUTE1–15, CONTEXT — audit and flexfield context columns.

Common Use Cases and Queries

Typical uses include exposing counter property configuration for reporting, validating property defaults in interfaces, and supplying the CSXCTCCV form with a flat data source. Sample query listing properties and their latest values:

  • SELECT counter_property_id, property_name, property_value, value_timestamp, property_data_type FROM cs_ctr_csxctccv_property_v;
  • SELECT counter_id, property_name, default_value, default_value_code, property_lov_name FROM cs_ctr_csxctccv_property_v WHERE property_lov_type IS NULL;
  • SELECT p.property_name, p.uom_code, p.minimum_value, p.maximum_value FROM cs_ctr_csxctccv_property_v p WHERE p.property_value IS NOT NULL AND p.counter_id = :counter_id;

Because DEFAULT_VALUE_CODE is NULL for LOV-typed properties, filtering on that column isolates properties whose defaults are literal rather than lookup-driven. Reporting queries should account for the effective-dating columns and the possible absence of a captured value, since the outer join intentionally returns null values for unset properties.