Search Results csi_counters_b




Overview
Explore in AI Chat

Overview

CSI_COUNTERS_B is a core table in the Oracle E-Business Suite CSI – Install Base product. It holds the counter instance data associated with installed assets and maintainable items tracked throughout their operational lifecycle. A counter represents a measurable accumulation — meter readings, cycle counts, usage quantities, or elapsed intervals — that drives preventive maintenance scheduling, warranty entitlement consumption, and service contract billing within Enterprise Asset Management (EAM) and related modules.

The table resides in the CSI schema and is documented as VALID in the ETRM reference for release 12.1.1 and 12.2.2. It is physically wide, containing 76 documented columns, reflecting the flexibility required to model many counter types (absolute, derived, rollover, time-based) with tolerances, units of measure, and formula-driven computation.

The metadata carries a heuristic Data Vault classification of hub-leaning. From a dimensional modeling perspective, this suggests treating COUNTER_ID as a hub business key, with descriptive and mutable attributes such as tolerances, formulas, and flags modeled as satellite data. It should be noted that this classification is a mining heuristic derived from the foreign-key structure rather than a formally declared design.

Key Information Stored

The primary key is defined by the unique index CSI_COUNTERS_B_PK on COUNTER_ID, which serves as the surrogate identifier for each counter instance. A second unique index, CSI_COUNTERS_B_U01, is also documented on COUNTER_ID, reinforcing it as the sole business-key candidate in the documented schema.

Common Use Cases and Queries

Typical reporting scenarios include identifying active counters for a maintainable item, auditing effective-dated counter configurations, and extracting counters referenced by EAM maintenance schedules.

To list currently active counters with their measurement context:

  • SELECT COUNTER_ID, COUNTER_TYPE, UOM_CODE, INITIAL_READING, START_DATE_ACTIVE, END_DATE_ACTIVE FROM CSI.CSI_COUNTERS_B WHERE VALID_FLAG = 'Y' AND SYSDATE BETWEEN START_DATE_ACTIVE AND NVL(END_DATE_ACTIVE, SYSDATE + 1);

To find counters used in PM scheduling:

  • SELECT c.COUNTER_ID, c.UOM_CODE, c.DEFAULT_USAGE_RATE FROM CSI.CSI_COUNTERS_B c WHERE c.USED_IN_SCHEDULING = 'Y' AND c.EAM_REQUIRED_FLAG = 'Y';

To review derived counters and their formulas:

  • SELECT COUNTER_ID, DERIVE_COUNTER_ID, DERIVE_FUNCTION, FORMULA_TEXT FROM CSI.CSI_COUNTERS_B WHERE DERIVE_COUNTER_ID IS NOT NULL;

Common reporting uses include meter-to-reading reconciliation, rollover configuration audits, and security-group-scoped counter inventories.

Related Objects

The documented foreign-key metadata establishes the following relationships:

  • EAM_PM_LAST_SERVICE.METER_ID references CSI_COUNTERS_B — records the most recent service reading per meter.
  • EAM_PM_SCHEDULING_RULES.METER_ID references CSI_COUNTERS_B — links preventive maintenance scheduling rules to their driving counters.
  • FND_SECURITY_GROUPS — referenced through CSI_COUNTERS_B.SECURITY_GROUP_ID for row-level data security.
  • Counter reading and transaction tables in the CSI Install Base product maintain the accumulated values associated with each counter instance.
  • Counter group and template definitions supply the GROUP_ID and CREATED_FROM_COUNTER_TMPL_ID context for each instance.

Together these dependencies establish CSI_COUNTERS_B as a hub-leaning reference point connecting install base counter configuration to EAM maintenance execution.