Search Results csi_ctr_property_template_v

Overview

The APPS.CSI_CTR_PROPERTY_TEMPLATE_V view is a reporting and integration object within the Oracle E-Business Suite CSI – Install Base product. Its documented purpose is to expose counter property templates — the reusable definitions that describe the attributes (properties) that can be captured against counters associated with customer products and installed base instances. In Oracle E-Business Suite 12.1.1 and 12.2.2 the object is registered as a VALID view owned by the APPS schema, providing a stable, denormalized read interface over the underlying counter property template entity.

Rather than requiring callers to join the base template table with lookup and unit-of-measure sources, the view pre-resolves descriptive meanings and default codes. This makes it well suited to concurrent-program extracts, Oracle Discoverer/OBIEE reporting layers, and integration interfaces that need to publish or consume counter property metadata without reimplementing the lookup joins.

Underlying Base Objects

The view is defined over four documented referenced objects:

• CSI_CTR_PROP_TEMPLATE_VL (view) — the primary source (aliased CCPB), supplying all counter property template columns.
• FND_LOOKUPS (view) — joined twice as FL and FL1 with outer-join syntax to resolve lookup meanings and default codes.
• MTL_UNITS_OF_MEASURE (synonym) — outer-joined as MUM on UOM_CODE to obtain the unit-of-measure description.
• FND_GLOBAL (package) — referenced for session-based values such as security group context.

The driving join CCPB.UOM_CODE = MUM.UOM_CODE(+) is an outer join, so templates without a unit of measure are still returned. Likewise FL.LOOKUP_TYPE(+) = CCPB.PROPERTY_LOV_TYPE and FL1.LOOKUP_CODE(+) = FL.LOOKUP_TYPE are outer joins, ensuring rows are preserved when no matching lookup exists.

Key Columns

• COUNTER_PROPERTY_ID — primary identifier for the counter property template.
• NAME / DESCRIPTION — the template's name and descriptive text.
• COUNTER_ID — the counter to which the property template belongs.
• PROPERTY_DATA_TYPE — the data type governing valid property values.
• PROPERTY_LOV_TYPE / PROPERTY_LOV_NAME — the lookup type used for value validation and its resolved meaning.
• DEFAULT_VALUE_CODE / DEFAULT_VALUE — the default lookup code and default value for the property.
• IS_NULLABLE, MINIMUM_VALUE, MAXIMUM_VALUE — nullability and permissible value bounds.
• UOM_CODE / UNIT_OF_MEASURE — unit of measure code and its description.
• START_DATE_ACTIVE / END_DATE_ACTIVE — effective dating for the template.
• SECURITY_GROUP_ID, OBJECT_VERSION_NUMBER — multi-org security context and optimistic locking version.
• ATTRIBUTE_CATEGORY and ATTRIBUTE1–ATTRIBUTE15 — the standard EBS descriptive flexfield (DFF) columns.
• CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN — standard WHO audit columns.
• MIGRATED_FLAG — indicates whether the record was migrated from a legacy source.

Common Use Cases and Queries

Typical uses include validating counter property configuration, building extracts of template definitions for integration, and driving dynamic property capture in service or asset applications. A simple listing of active templates is shown below.

SELECT counter_property_id, name, description, property_data_type,
       property_lov_name, default_value, uom_code, unit_of_measure
FROM   apps.csi_ctr_property_template_v
WHERE   SYSDATE BETWEEN start_date_active AND NVL(end_date_active, SYSDATE+1)
ORDER BY name;

Because the view resolves lookup meanings and units of measure, callers should not re-join FND_LOOKUPS or MTL_UNITS_OF_MEASURE. Filtering on counter_id is the most efficient access path when retrieving the property templates belonging to a specific counter, and the WHO columns support incremental or change-data-style extraction for downstream interfaces.