Search Results csi_ctr_property_template_b




Overview
Explore in AI Chat

Overview

CSI_CTR_PROPERTY_TEMPLATE_B is a table in the CSI (Install Base) product schema of Oracle E-Business Suite, present and valid in both release 12.1.1 and 12.2.2. It stores the counter template property definitions that govern how counters attached to installed base assets are configured and validated. In EBS Install Base, counters are metering constructs used to track usage readings against an asset or instance — for example odometer readings on a vehicle or cycle counts on a machine. The template property rows in this table define the metadata for each such counter: the data type of the value, the list of values it may draw from, whether it is mandatory, and any permissible numeric range or unit of measure. This makes CSI_CTR_PROPERTY_TEMPLATE_B a definitional or setup table rather than a transactional one, and it is typically referenced during counter definition, data entry validation, and downstream reporting of counter readings.

From a Data Vault modeling perspective, the mined foreign key structure classifies this object as standalone. The heuristic suggests that CSI_CTR_PROPERTY_TEMPLATE_B is best treated as a hub-like reference entity rather than a link or satellite, since its relationships are limited and it carries the descriptive definition of a counter property rather than tracking changes over time to another entity.

Key Information Stored

The table is documented with 35 columns and a unique index, CSI_CTR_PROP_TEMPLATE_B_U01, on COUNTER_PROPERTY_ID. The primary key, CSI_CTR_PROPERTY_TEMPLATE_B_PK, is also defined on COUNTER_PROPERTY_ID, making this column the surrogate identifier for each property template row. The following columns are the most significant for functional and reporting purposes:

  • COUNTER_PROPERTY_ID — the surrogate primary key and the unique business-key candidate that identifies each counter property template row.
  • COUNTER_ID — the counter to which this property template belongs, linking the definition back to its parent counter.
  • PROPERTY_DATA_TYPE — the data type of the property value, driving validation and storage rules.
  • PROPERTY_LOV_TYPE — the list of values type used when the property is constrained to a predefined set.
  • IS_NULLABLE — whether a value is required for the property when a counter reading is entered.
  • DEFAULT_VALUE — the value supplied when the user does not explicitly enter one.
  • MINIMUM_VALUE / MAXIMUM_VALUE — the permissible numeric range for the property.
  • UOM_CODE — the unit of measure associated with the property, where applicable.
  • START_DATE_ACTIVE / END_DATE_ACTIVE — the effective dating window for the template property.
  • SECURITY_GROUP_ID — the security grouping under which the row is visible, foreign-keyed to FND_SECURITY_GROUPS.
  • OBJECT_VERSION_NUMBER — the optimistic locking column used by the EBS framework for concurrent update control.
  • The standard WHO columns — LAST_UPDATE_DATE, LAST_UPDATED_BY, CREATION_DATE, CREATED_BY, and LAST_UPDATE_LOGIN — for audit and change tracking.
  • ATTRIBUTE_CATEGORY and ATTRIBUTE1 through ATTRIBUTE15 — the descriptive flexfield columns available for customer-specific extension.
  • MIGRATED_FLAG — an indicator that the row was carried over during a migration or upgrade.

Common Use Cases and Queries

Typical use cases center on validating and reporting counter definitions. A common pattern is to retrieve all property templates for a given counter so the UI or an integration can render the correct entry fields and constraints:

  • Retrieving active template properties for a counter: SELECT * FROM CSI.CSI_CTR_PROPERTY_TEMPLATE_B WHERE COUNTER_ID = :counter_id AND (END_DATE_ACTIVE IS NULL OR END_DATE_ACTIVE > SYSDATE);
  • Identifying mandatory properties: filter on IS_NULLABLE = 'N' to list fields that must be populated for a counter reading.
  • Range and UOM validation: query MINIMUM_VALUE, MAXIMUM_VALUE, and UOM_CODE to build validation logic for inbound counter data.
  • Reporting on counter configuration: join to counter definitions via COUNTER_ID to produce a matrix of properties per counter for administrative review.
  • Upgrade and migration auditing: use MIGRATED_FLAG to isolate rows carried over during an upgrade or data conversion, useful when validating a 12.1.1 to 12.2.2 migration.

Because the table is definitional and comparatively small, full scans are rarely costly, but joining on COUNTER_ID and filtering on the effective dates is the recommended access pattern for interactive queries.

Related Objects

The documented foreign key relationship links this table to FND_SECURITY_GROUPS through SECURITY_GROUP_ID, so all rows are scoped by the security group applied to the operating user. Beyond that, the following related objects are significant:

  • FND_SECURITY_GROUPS — joined on SECURITY_GROUP_ID to resolve the security group context of each template row.
  • CSI_CTR_PROPERTY_TEMPLATE_TL — the translation table that holds the language-specific descriptions for these property templates, joined on COUNTER_PROPERTY_ID.
  • The counter definition tables in the CSI schema that own COUNTER_ID and anchor each property template to its parent counter.
  • CSI counter data tables that hold the actual counter readings, which are validated against the data type, LOV, range, and nullability rules defined here.
  • The CSI Install Base concurrent programs and APIs that create and maintain counter templates and enforce the property constraints at data entry time.

Together these objects form the configuration and validation layer that supports accurate counter-based usage tracking across the Install Base module.