Search Results eam_counters_v




Overview
Explore in AI Chat

Overview

EAM_COUNTERS_V is an Oracle Application Object Library view owned by the APPS schema and classified as VALID in Oracle E-Business Suite releases 12.1.1 and 12.2.2. It is registered under the Enterprise Asset Management (EAM) product family and is documented in the ETRM reference repository as a reporting view that returns all active meters and meter templates. The view is read-only by design: it consolidates the counter definition, translation, and relationship data held in the CSI counter tables into a single denormalized projection that is convenient for concurrent programs, BI Publisher data templates, Oracle Discoverer workbooks, and custom SQL reports.

The distinguishing characteristic of the view is the TMPL_FLAG column. In the documented view text, TMPL_FLAG is hard-coded to the literal value 'N', which means the shipped definition returns meter (counter) records rather than meter templates. Because the underlying CSI_COUNTERS_B and CSI_COUNTERS_TL tables are shared by meter templates, the numeric counter identifiers returned here may also be referenced by the template tables, and the SOURCE_TMPL_ID column (aliased from CREATED_FROM_COUNTER_TMPL_ID) preserves the link back to the originating template. Consumers should therefore treat EAM_COUNTERS_V as the authoritative source for active, effective-dated meter definitions.

Underlying Base Objects

The documented base objects referenced by the view are:

  • CSI_COUNTERS_B – the base table holding the counter identifier, unit of measure, direction, reading type, initial reading, scheduling flags, effective dates, and the 30 descriptive flexfield attributes.
  • CSI_COUNTERS_TL – the translation table supplying NAME and DESCRIPTION in the session language, filtered by LANGUAGE = USERENV('LANG').
  • CSI_COUNTER_RELATIONSHIPS – the relationship table joined with an outer join (+) on OBJECT_COUNTER_ID, providing SOURCE_COUNTER_ID, FACTOR, and ACTIVE_START_DATE for counters derived from another meter.
  • CSI_COUNTER_TEMPLATE_B and CSI_COUNTER_TEMPLATE_TL – referenced by the view metadata, corresponding to the template definition and translation tables queried when the template-oriented variant of the view is resolved.

The joins are driven from CSI_COUNTERS_B, with the translation and relationship tables attached via outer joins where appropriate. The WHERE clause applies SYSDATE BETWEEN NVL(START_DATE_ACTIVE, SYSDATE-1) AND NVL(END_DATE_ACTIVE, SYSDATE+1) against the base counter and the outer relationship, so only currently effective meters and only currently effective relationship rows are returned.

Key Columns

Common Use Cases and Queries

Typical scenarios include listing all active meters by unit of measure, identifying meters created from a specific template, and tracing derived meters back to their source meter for reading reconciliation and preventive maintenance scheduling.

List active meters and their scheduling flags:

  • SELECT METER_ID, METER_NAME, METER_UOM, METER_TYPE, EAM_REQUIRED_FLAG, USED_IN_SCHEDULING FROM APPS.EAM_COUNTERS_V WHERE TMPL_FLAG = 'N' ORDER BY METER_NAME;

Find meters generated from a given template:

  • SELECT METER_ID, METER_NAME, SOURCE_TMPL_ID, FROM_EFFECTIVE_DATE FROM APPS.EAM_COUNTERS_V WHERE SOURCE_TMPL_ID = :template_id;

Report derived meter relationships with conversion factors:

  • SELECT METER_ID, METER_NAME, SOURCE_METER_ID, SOURCE_METER_NAME, FACTOR FROM APPS.EAM_COUNTERS_V WHERE SOURCE_METER_ID IS NOT NULL;

Because effective-date filtering and the language filter are embedded in the view definition, these queries require no additional date or language predicates; the values returned are already scoped to the current effective window and to the session language identified by USERENV('LANG').