Results for “csi_counter_template_b_u01”

AI-generated from documented ETRM metadata — verify critical details on the linked pages.

Overview

The CSI.CSI_COUNTER_TEMPLATE_B table is a core setup object within the Oracle EBS Enterprise Asset Management (EAM) and Enterprise Track and Rebuild Management (ETRM) suite, owned by the CSI schema. It stores the configuration templates used to define counters during the counter instantiation process. A counter in this context represents an accumulating measurement — such as meter readings, odometer values, or operational usage totals — associated with an asset or product. Templates defined here govern how counter instances are created, read, rolled over, estimated, and scheduled.

Each record can describe either a Regular counter or a Formula counter, and its reading type may be Absolute or Changed. The table also captures unit of measure, rollover boundaries, source/derived counter relationships, effectivity dates, and estimation settings. From a dimensional modeling perspective, the mined foreign-key structure classifies this object as standalone for Data Vault purposes; however, given its auto-generated COUNTER_ID primary key and its descriptive, attribute-rich nature, it can reasonably be modeled as a satellite anchored to a counter hub, with GROUP_ID functioning as an informal grouping key.

Key Information Stored

The surrogate primary key is COUNTER_ID, which is auto-generated and enforced by the primary key CSI_COUNTER_TEMPLATE_B_PK. The unique index CSI_COUNTER_TEMPLATE_B_U01 also spans COUNTER_ID, confirming it as the single business-key candidate. The non-unique index CSI_COUNTER_TEMPLATE_B_N01 on GROUP_ID supports grouping-based access.

• COUNTER_ID — internal primary key identifying the counter template.
• GROUP_ID — groups related counter templates together.
• COUNTER_TYPE — distinguishes Regular versus Formula counters.
• READING_TYPE — indicates Absolute or Changed reading behavior.
• UOM_CODE — unit of measure for the counter readings.
• INITIAL_READING / INITIAL_READING_DATE — baseline reading and its effective date.
• ROLLOVER_LAST_READING / ROLLOVER_FIRST_READING — rollover from/to bounds for cyclical counters.
• DERIVE_COUNTER_ID / DERIVE_FUNCTION / DERIVE_PROPERTY_ID — source counter and logic for derived values.
• FORMULA_TEXT / FORMULA_INCOMPLETE_FLAG / VALID_FLAG — formula definition and validation indicators.
• START_DATE_ACTIVE / END_DATE_ACTIVE — effectivity window for the template.
• ESTIMATION_ID / DEFAULT_USAGE_RATE — estimation configuration and default consumption rate.
• USED_IN_SCHEDULING / EAM_REQUIRED_FLAG / AUTOMATIC_ROLLOVER — operational behavioral flags.
• SECURITY_GROUP_ID — foreign key to FND_SECURITY_GROUPS for access control.

Common Use Cases and Queries

Typical scenarios include validating counter setup before instantiation, auditing rollover configurations, and reporting formula completeness. A frequent query retrieves all active Regular counters within a group:

• SELECT counter_id, counter_type, uom_code FROM csi_counter_template_b WHERE group_id = :p_group AND valid_flag = 'Y' AND SYSDATE BETWEEN start_date_active AND NVL(end_date_active, SYSDATE + 1);
• Detecting incomplete formulas: SELECT counter_id FROM csi_counter_template_b WHERE formula_incomplete_flag = 'Y' OR valid_flag = 'N';
• Reporting rollover boundaries for cyclic counters: filter on rollover_last_reading and rollover_first_reading being non-null.
• Derived-counter lineage tracing using derive_counter_id to walk parent/child counter relationships.
• Security-scoped extraction joining SECURITY_GROUP_ID to FND_SECURITY_GROUPS.

Related Objects

• FND_SECURITY_GROUPS — joined via CSI_COUNTER_TEMPLATE_B.SECURITY_GROUP_ID = FND_SECURITY_GROUPS.SECURITY_GROUP_ID.
• CSI_COUNTER_TEMPLATE_TL — translated (language) companion table keyed by COUNTER_ID.
• CSI_COUNTER_INSTANCES — instantiated counters created from these templates.
• CSI_COUNTER_READINGS — transactional readings captured against instances.
• CSI_ESTIMATIONS_B — referenced through ESTIMATION_ID.
• MTL_UNITS_OF_MEASURE — resolves UOM_CODE.
• Concurrent programs and public APIs such as the Counter Template import/validation routines that read and enforce VALID_FLAG and formula consistency.