Search Results csi_counters_b_n03

Overview

CSI.CSI_COUNTERS_B is the base transactional table in the Oracle E-Business Suite Customer Intel ligence (CSI) module that stores the attributes of instantiated counters associated with an Item Instance or a Service Contract Line. An instantiated counter originates from a counter template; the template from which it was copied is stamped in this table through the CREATED_FROM_COUNTER_TMPL_ID column, preserving the lineage back to the source counter. Counters may be defined as "Regular" or "Formula" types, and the reading type of a given counter instance may be either "Absolute" or "Changed." The table also carries attributes such as unit of measure code, rollover thresholds, effectivity dates, estimation references, usage rate defaults, scheduling indicators, and descriptive flexfield (attribute) columns.

The object is registered as VALID in the FND design data under CSI.CSI_COUNTERS_B and is stored in the APPS_TS_TX_DATA tablespace with a PCTFREE of 10. In 12.2.2 the documented schema exposes 76 columns. Under a heuristic Data Vault classification mined from the foreign key structure, this object leans toward a hub, since COUNTER_ID functions as the durable business key around which descriptive and derived attributes are attached. That classification is a modeling suggestion only; the physical design remains a conventional EBS transactional base table.

Key Information Stored

The primary key is CSI_COUNTERS_B_PK, defined on the COUNTER_ID column. A unique index, CSI_COUNTERS_B_U01, is also defined on COUNTER_ID in the APPS_TS_TX_IDX tablespace, making it the documented business-key candidate for the table. The most significant columns include:

• COUNTER_ID — Auto-generated internal primary key uniquely identifying each counter instance.
• GROUP_ID and DEFAULTED_GROUP_ID — Identifiers used to group related counters; GROUP_ID is served by the non-unique index CSI_COUNTERS_B_N01.
• COUNTER_TYPE — Indicates whether the counter instance is a Regular or Formula counter.
• CREATED_FROM_COUNTER_TMPL_ID — References the counter template from which the instance was copied.
• INITIAL_READING / INITIAL_READING_DATE — Baseline reading value and the date it was captured.
• UOM_CODE — Unit of measure for readings; indexed by CSI_COUNTERS_B_N03.
• READING_TYPE — Distinguishes "Absolute" from "Changed" reading semantics.
• VALID_FLAG and FORMULA_INCOMPLETE_FLAG — Validity indicators for formula counters and derived filters.
• FORMULA_TEXT — Expression text (up to 1996 characters) for Formula counter types.
• ROLLOVER_LAST_READING / ROLLOVER_FIRST_READING / AUTOMATIC_ROLLOVER — Rollover threshold values and behavior control.
• DERIVE_COUNTER_ID, DERIVE_FUNCTION, DERIVE_PROPERTY_ID — Derivation definition for derived counters.
• START_DATE_ACTIVE / END_DATE_ACTIVE — Effectivity window of the counter instance.
• SECURITY_GROUP_ID — Foreign key to FND_SECURITY_GROUPS controlling row-level access.
• OBJECT_VERSION_NUMBER and the standard WHO columns (LAST_UPDATE_DATE, CREATED_BY, etc.) — Concurrency control and audit trail.

Columns such as USE_PAST_READING, USED_IN_SCHEDULING, EAM_REQUIRED_FLAG, MIGRATED_FLAG, and CUSTOMER_VIEW support estimation, scheduling, migration, and self-service visibility requirements.

Common Use Cases and Queries

Typical usage centers on identifying the counters attached to a given item instance or service contract line, validating formula counters, and reporting on reading configuration. A common lookup retrieves an instance by its identifier:

• SELECT counter_id, counter_type, reading_type, uom_code, initial_reading FROM csi.csi_counters_b WHERE counter_id = :p_counter_id;
• SELECT c.counter_id, c.counter_type, c.formula_text, c.valid_flag FROM csi.csi_counters_b c WHERE c.group_id = :p_group_id AND c.valid_flag = 'Y';
• SELECT counter_id, counter_type FROM csi.csi_counters_b WHERE created_from_counter_tmpl_id = :p_template_id;

Reporting scenarios include availability of counters for preventive maintenance scheduling, rollover configuration reviews, and identification of incomplete formula definitions (FORMULA_INCOMPLETE_FLAG = 'Y'). Effectivity-based queries filtered on START_DATE_ACTIVE and END_DATE_ACTIVE are used to determine the counter configuration in force on a given date.

Related Objects

The following objects are the most significant dependencies and dependents of CSI_COUNTERS_B:

• FND_SECURITY_GROUPS — referenced by CSI_COUNTERS_B.SECURITY_GROUP_ID, providing row-level security resolution.
• EAM_PM_LAST_SERVICE — references this table through METER_ID, linking completed maintenance service records to the counter used.
• EAM_PM_SCHEDULING_RULES — references this table through METER_ID, driving meter-based preventive maintenance scheduling.
• CSI_COUNTERS_TL and related counter template tables — provide the template definitions from which instances are created via CREATED_FROM_COUNTER_TMPL_ID.
• CSI_ITEM_INSTANCES — the item instance context with which instantiated counters are associated.
• CSI_COUNTER_READINGS — stores the readings captured against each counter instance, joined on COUNTER_ID.

Together these objects form the counter lifecycle: template definition, instantiation, reading capture, and downstream consumption by maintenance and service scheduling processes.