Search Results csi_counter_template_b_pk

Overview

CSI_COUNTER_TEMPLATE_B is a core table within the Oracle E-Business Suite Install Base (CSI) module. It holds counter template definitions. A counter template provides the metadata or blueprint that governs how a specific counter — a numeric measurement such as a meter reading, usage counter, or odometer value — behaves for an installed asset. Counters themselves are attached to install base instances and track consumption, wear, or operational metrics over time.

The table resides in the CSI schema and is fully valid in both Oracle EBS 12.1.1 and 12.2.2. Its documented physical schema contains 76 columns and its primary key, CSI_COUNTER_TEMPLATE_B_PK, is defined on the COUNTER_ID column. A separate unique index, CSI_COUNTER_TEMPLATE_B_U01 (COUNTER_ID), also enforces uniqueness on the same identifier, making COUNTER_ID the primary business-key candidate in addition to the technical surrogate key.

From a Data Vault modeling perspective, the metadata's heuristic classification is standalone. In Data Vault terms, this table is best treated as a hub-like or reference entity: it defines the counter template as a discrete, independently identified business object, with its descriptive attributes (tolerances, formulas, directions, rollover behavior) forming satellite-like detail. It does not document any foreign keys into other ETRM tables other than its security group reference, reinforcing its role as a foundational definition table rather than a transactional link.

Key Information Stored

The table captures both the identity and the behavioral rules of a counter template. The most significant columns include:

• COUNTER_ID — the primary key and unique business identifier for the template.
• COUNTER_TYPE — classifies the counter (for example, numeric or timed based on usage).
• GROUP_ID and DEFAULTED_GROUP_ID — associate the template with a counter group hierarchy.
• INITIAL_READING and INITIAL_READING_DATE — define the starting value and timestamp.
• STEP_VALUE — controls the increment or resolution of readings.
• TOLERANCE_PLUS and TOLERANCE_MINUS — allowable deviation bounds.
• UOM_CODE — the unit of measure for the readings.
• DERIVE_COUNTER_ID, DERIVE_FUNCTION, and DERIVE_PROPERTY_ID — support derived or calculated counters.
• FORMULA_TEXT and FORMULA_INCOMPLETE_FLAG — hold and validate the calculation formula.
• VALID_FLAG, START_DATE_ACTIVE, END_DATE_ACTIVE — govern lifecycle and effective dating.
• ROLLOVER_LAST_READING, ROLLOVER_FIRST_READING, and AUTOMATIC_ROLLOVER — define rollover behavior when readings exceed capacity.
• DIRECTION, READING_TYPE, and USE_PAST_READING — control reading semantics.
• SECURITY_GROUP_ID — the single documented foreign key, referencing FND_SECURITY_GROUPS.
• OBJECT_VERSION_NUMBER, LAST_UPDATE_DATE, LAST_UPDATED_BY, CREATION_DATE, CREATED_BY — standard EBS auditing and concurrency columns.

Common Use Cases and Queries

Typical reporting scenarios include retrieving active counter templates, checking their tolerances, and reviewing rollover configuration. A representative query retrieves templates associated with a counter group:

• SELECT counter_id, counter_type, uom_code, tolerance_plus, tolerance_minus FROM csi_counter_template_b WHERE valid_flag = 'Y' AND group_id = :p_group_id;
• SELECT counter_id, formula_text, formula_incomplete_flag FROM csi_counter_template_b WHERE formula_incomplete_flag = 'Y';
• SELECT counter_id, initial_reading, step_value, direction, automatic_rollover FROM csi_counter_template_b WHERE sysdate BETWEEN start_date_active AND NVL(end_date_active, sysdate + 1);

These queries support setup validation, data migration audits, and operational dashboards. Because COUNTER_ID is both the primary key and the defining business key, direct lookups by COUNTER_ID are stable and index-supported.

Related Objects

The documented relationship data is limited. The single foreign key is:

• FND_SECURITY_GROUPS — joined via SECURITY_GROUP_ID for row-level security and access control.

Beyond the documented FK, the counter template is referenced at runtime by transactional Install Base counter tables that store actual readings and by the counter group hierarchy. Analysts should join CSI_COUNTER_TEMPLATE_B to the security groups table when applying organization-level security, and to counter instance and reading tables to reconcile template rules against recorded values.