Search Results csi_ctr_property_lov_type




Overview
Explore in AI Chat

Overview

APPS.CSI_CTR_PROPERTY_TEMPLATE_V is a reporting view in Oracle E-Business Suite that exposes counter property template definitions used by the Enterprise Territory and Resource Management (ETRM) / Customer Intelligence (CSI) counter model. A "counter" in CSI represents a measurable entity — a usage metric, a tracked quantity, or an instance-level attribute — and each counter definition owns a set of properties that describe its data type, allowable values, and validation constraints. This view flattens those property template rows and decorates them with decoded lookup meanings and unit-of-measure descriptions, making it suitable for direct query, LOV population, and integration extraction without requiring the caller to join multiple base objects.

The object is a view, not a table, and therefore carries no storage of its own; it is a read-only projection over the counter property template base data. This makes it safe for reporting and inquiry purposes, but it must not be used as a DML target. It is relevant in both 12.1.1 and 12.2.2, where the underlying column set and decode logic remain consistent with the documented ETRM metadata.

Underlying Base Objects

The view is defined over four documented objects:

  • CSI_CTR_PROP_TEMPLATE_VL (VIEW) — the primary source, supplying the base property template rows (aliased CCPB). This is the multi-language base view behind the counter property template entity.
  • FND_LOOKUPS (VIEW) — referenced twice. One instance (FL) resolves the default value code and its meaning; a second inline inline-derived instance (FL1) is restricted to LOOKUP_TYPE = 'CSI_CTR_PROPERTY_LOV_TYPE' and supplies the human-readable meaning of the property LOV type.
  • MTL_UNITS_OF_MEASURE (SYNONYM) — supplies the unit-of-measure description (aliased MUM) for any property carrying a UOM code.
  • FND_GLOBAL (PACKAGE) — provides session context (such as security group and user identity) used within the view's access filtering.

All joins to FND_LOOKUPS and MTL_UNITS_OF_MEASURE are outer joins, so property rows are returned even when no matching lookup or unit of measure exists.

Key Columns

Common Use Cases and Queries

The view is typically queried to drive value lists, to audit property definitions, and to migrate counter configuration between environments. A simple listing for a given counter might read:

  • SELECT counter_property_id, name, property_data_type, property_lov_name, default_value
  • FROM apps.csi_ctr_property_template_v
  • WHERE counter_id = :counter_id
  • AND SYSDATE BETWEEN NVL(start_date_active, SYSDATE) AND NVL(end_date_active, SYSDATE + 1);

To inspect available LOV types specifically, developers join or filter on PROPERTY_LOV_TYPE and read PROPERTY_LOV_NAME, which resolves via the CSI_CTR_PROPERTY_LOV_TYPE lookup. Because the joins to FND_LOOKUPS and MTL_UNITS_OF_MEASURE are outer, rows with null LOV types or UOM codes are preserved — important when validating incomplete configurations. The view should be accessed with the APPS schema (or a synonym) and treated strictly as read-only.