Search Results csi_counter_properties_b_pk

Overview

CSI_COUNTER_PROPERTIES_B is a CSI (Install Base) table in Oracle E-Business Suite that stores the master definitions of counter instance properties. In EBS 12.1.1 and 12.2.2, counters are used extensively in telecommunication, utility, and asset-intensive industries to track cumulative readings, usage quantities, or operational metrics associated with a customer asset (an installed base instance). Each row in this table defines a property that can be captured against a counter, such as the property's data type, allowed list of values, default, minimum and maximum bounds, unit of measure, and the period during which the property is active.

The _B suffix indicates that this is the base (non-translated) table in a standard EBS translation pattern; the corresponding _TL table typically carries language-specific descriptive columns. In Data Vault modeling terms, the mined FK structure classifies this object as a standalone table, suggesting it functions as a hub-like entity with its own primary key and no strong dependency to an upstream parent other than a security-group reference. This classification is heuristic and should be treated as a modeling suggestion rather than a documented constraint.

Key Information Stored

The table contains 36 documented columns. Its surrogate primary key is COUNTER_PROPERTY_ID, enforced by the CSI_COUNTER_PROPERTIES_B_PK constraint. A unique index, CSI_COUNTER_PROPERTIES_B_U01, also exists on the same column, making it the documented business-key candidate.

• COUNTER_PROPERTY_ID — Surrogate primary key and business-key candidate identifying each property definition.
• COUNTER_ID — The counter instance to which the property belongs; the principal join key to counter-level data.
• PROPERTY_DATA_TYPE — Declares the data type (for example, number, character, or date) expected for the property value.
• PROPERTY_LOV_TYPE — Identifies the list-of-values type used to constrain acceptable property values.
• CREATED_FROM_CTR_PROP_TMPL_ID — Links the property back to the counter property template from which it was generated.
• IS_NULLABLE — Indicates whether a value is mandatory for the property.
• DEFAULT_VALUE — Predefined value applied when no explicit value is supplied.
• MINIMUM_VALUE and MAXIMUM_VALUE — Numeric range boundaries enforced for the property.
• UOM_CODE — Unit of measure associated with the property value.
• START_DATE_ACTIVE and END_DATE_ACTIVE — Effective dating that governs whether the property is currently active.
• SECURITY_GROUP_ID — Foreign key to FND_SECURITY_GROUPS, controlling data access at the group level.
• OBJECT_VERSION_NUMBER, LAST_UPDATE_DATE, LAST_UPDATED_BY, CREATION_DATE, CREATED_BY, LAST_UPDATE_LOGIN — Standard EBS auditing and optimistic-locking columns.
• ATTRIBUTE_CATEGORY and ATTRIBUTE1 through ATTRIBUTE15 — DFF (Descriptive Flexfield) storage for customer-extensible attributes.
• MIGRATED_FLAG — Flags records introduced through a migration or conversion process.

Common Use Cases and Queries

Typical usage centers on diagnosing counter configuration, generating property-definition reports, and validating constraints before counter readings are captured. A common query joins the table to itself or to counter data to list active properties for a given counter.

• Listing active properties for a counter: SELECT counter_property_id, property_data_type, default_value FROM csi_counter_properties_b WHERE counter_id = :counter_id AND SYSDATE BETWEEN start_date_active AND NVL(end_date_active, SYSDATE + 1) AND security_group_id = :sgid;
• Auditing recently added or migrated definitions using MIGRATED_FLAG, CREATED_BY, and CREATION_DATE.
• Reporting mandatory versus optional properties via IS_NULLABLE and range enforcement via MINIMUM_VALUE/MAXIMUM_VALUE.
• Tracing template derivation with CREATED_FROM_CTR_PROP_TMPL_ID.

Because SECURITY_GROUP_ID is present, reports run against this table must apply the appropriate security-group predicate to comply with EBS data security.

Related Objects

The following objects are the most significant to consider when working with CSI_COUNTER_PROPERTIES_B:

• FND_SECURITY_GROUPS — Referenced via SECURITY_GROUP_ID; governs access control.
• Counter instance tables in the CSI schema — Joined through COUNTER_ID to associate properties with a specific counter.
• Counter property template tables — Joined through CREATED_FROM_CTR_PROP_TMPL_ID to show the originating template.
• Counter property value tables — Related at property level to hold captured readings against each definition.
• The corresponding _TL translation table — Joined on COUNTER_PROPERTY_ID for language-specific descriptions.
• CSI Install Base public APIs that create and maintain counter structures, which populate this table indirectly.

These relationships are the primary integration points for reporting, migration, and troubleshooting activities involving counter properties.