Search Results cs_counter_property_lov

Overview

The APPS.CS_COUNTER_PROPERTIES_V view is a denormalized reporting and integration layer built on top of the ETRM (Enterprise Territory and Resource Management) counter configuration model in Oracle E-Business Suite 12.1.1 and 12.2.2. It exposes the attributes of counter properties — the individual measurable or configurable characteristics assigned to a counter — while resolving several foreign key values into meaningful display text. Specifically, the view transforms raw codes and identifiers into human-readable descriptions by joining to units of measure and lookup definitions.

Because it is owned by APPS and published as a synonym-accessible view, it is intended for use by forms, LOV (list of values) queries, concurrent programs, and custom reporting. The user search term cs_counter_property_lov reflects this: the view is commonly used as the driving source for list-of-values queries that populate property selection fields in ETRM setup and counter definition screens. Rather than requiring callers to resolve lookups, UOMs, and type meanings separately, the view returns them pre-joined, simplifying both UI and reporting development.

Underlying Base Objects

The view is defined over the following documented objects:

• CS_COUNTER_PROPERTIES (SYNONYM) — the primary table holding each counter property record, aliased as a. All core columns in the view originate here.
• MTL_UNITS_OF_MEASURE (SYNONYM) — joined via an outer join on UOM_CODE to translate the stored code into the descriptive UNIT_OF_MEASURE (alias b).
• FND_LOOKUPS (VIEW) — accessed twice. Alias c resolves PROPERTY_LOV_TYPE against the property's lookup type, and an inline subquery aliased c1 restricts to the lookup type CS_COUNTER_PROPERTY_LOV.
• FND_GLOBAL (PACKAGE) — referenced indirectly as a standard dependency for APPS-owned views to support session/context globalization.

All joins to the lookup and unit-of-measure objects use Oracle outer-join syntax (the (+) operator), ensuring that counter property rows are returned even when no matching UOM or lookup value exists. This is significant because property rows may legitimately have null UOM or null LOV associations.

Key Columns

• COUNTER_PROPERTY_ID / COUNTER_ID — primary identifier of the property and the parent counter to which it belongs.
• NAME / DESCRIPTION — the property's identifying label and free-text description.
• PROPERTY_DATA_TYPE / IS_NULLABLE / DEFAULT_VALUE — datatype declaration, nullability flag, and the default value assigned to the property.
• MINIMUM_VALUE / MAXIMUM_VALUE — allowed numeric range constraints, when applicable.
• UOM_CODE / UNIT_OF_MEASURE — the stored code and its resolved descriptive name from MTL_UNITS_OF_MEASURE.
• PROPERTY_LOV_TYPE / PROPERTY_LOV_NAME — the lookup type driving the LOV and its decoded meaning. When PROPERTY_LOV_TYPE is null, both decoded values are returned as null via DECODE.
• DEFAULT_VALUE_CODE — the lookup code corresponding to the default value, derived through the c alias.
• SOURCE_COUNTER_PROP_ID / CREATED_FROM_CTR_PROP_TMPL_ID — lineage columns indicating where the property was copied from or which template created it.
• START_DATE_ACTIVE / END_DATE_ACTIVE — effective dating for the property definition.
• ATTRIBUTE1–15 / CONTEXT — the standard descriptive flexfield (DFF) columns.
• OBJECT_VERSION_NUMBER, CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN — standard audit columns.

Common Use Cases and Queries

The most frequent use is populating a property LOV on an ETRM counter setup form. A typical query filters by counter and active date range:

• Retrieving all active properties for a given counter, ordered by name, to build a selection list.
• Reporting on property definitions with resolved UOM and LOV meanings for configuration review.
• Auditing default values and LOV type linkages across counters.

Sample SQL:

SELECT counter_property_id, name, unit_of_measure, property_lov_name, default_value
FROM apps.cs_counter_properties_v
WHERE counter_id = :counter_id
AND (start_date_active IS NULL OR start_date_active <= SYSDATE)
AND (end_date_active IS NULL OR end_date_active >= SYSDATE)
ORDER BY name;

Because joins to lookups and UOM are outer joins, callers need not account for missing reference data; the view returns the property row regardless, with null descriptive columns where no match exists.