Search Results source_meter_name




Overview
Explore in AI Chat

Overview

APPS.EAM_COUNTERS_V is a reporting view in Oracle E-Business Suite 12.1.1 and 12.2.2 that consolidates Enterprise Asset Management (EAM) counter definitions, including both regular counters and counter templates. It exposes translated counter names alongside unit of measure, reading direction, reading type, and the relationships that describe how one counter is derived from a "source" counter. Because the view resolves the source counter's translated name through a correlated subquery, it is the standard object consumed when a report or interface requires the human-readable origin of a counter configuration.

The view was designed to feed Oracle EAM meter and counter setup screens, asset meter assignments, and third-party integrations that synchronize meter definitions with external maintenance or condition-monitoring systems. Its UNION ALL structure merges regular counters (counter_type = 'REGULAR') with counter templates drawn from CSI_COUNTER_TEMPLATE_B/TL, flagging templates with a literal 'N' in the tmpl_flag column.

Underlying Base Objects

The documented base objects are CSI_COUNTERS_B, CSI_COUNTERS_TL, CSI_COUNTER_RELATIONSHIPS, CSI_COUNTER_TEMPLATE_B, and CSI_COUNTER_TEMPLATE_TL, all referenced as APPS synonyms. The first branch joins CSI_COUNTERS_B (ccb) to CSI_COUNTERS_TL (cct) on counter_id with language = userenv('LANG'), giving the translated counter name, and outer-joins CSI_COUNTER_RELATIONSHIPS (ccr) on object_counter_id where relationship_type_code = 'CONFIGURATION'. Date predicates restrict rows to counters and relationships active as of SYSDATE, using NVL defaults for open-ended start and end dates. The second branch selects from the counter template tables to supply template-based rows. The select list for the first branch also contains a correlated subquery against CSI_COUNTERS_TL (aliased cct2) that returns the translated name of ccr.source_counter_id — this is the origin of the source_meter_name column.

Key Columns

  • meter_id — the counter_id of the counter or template.
  • meter_name — translated counter name from CSI_COUNTERS_TL.
  • meter_uom — unit of measure code (uom_code).
  • value_change_dir — direction of value change for the reading.
  • meter_type — reading type of the counter.
  • source_meter_id — source_counter_id from the relationship record; NULL for template rows.
  • source_meter_name — translated name of the source counter, resolved via the correlated subquery on CSI_COUNTERS_TL using the session language.
  • factor, relationship_start_date — conversion factor and active start of the counter relationship.
  • eam_required_flag, used_in_scheduling, initial_reading, user_defined_rate, use_past_reading — EAM behavior attributes.
  • from_effective_date, to_effective_date — active date range of the counter.
  • tmpl_flag — 'N' literal for the regular-counter branch.
  • source_tmpl_id — created_from_counter_tmpl_id, linking a counter to the template it was created from.
  • attribute1 through attribute30 — descriptive flexfield segments.

Common Use Cases and Queries

Because the view supplies source_meter_name without requiring a manual join, it is the natural query surface for meter-relationship reporting. A typical query lists all active counters and the counter that serves as their source:

SELECT meter_id, meter_name, source_meter_id, source_meter_name, factor
FROM apps.eam_counters_v
WHERE source_meter_id IS NOT NULL;

Filtering by meter_name or source_meter_name is common in asset-meter lookup reports, and tmpl_flag distinguishes template-derived rows from regular counters. Integration extracts typically select meter_id, meter_name, meter_uom, meter_type, and source_meter_name so downstream systems can reconstruct the counter hierarchy without touching the CSI tables directly. Note that the LANG-based language predicate means the view returns names only for the connected user's language; multi-language reporting requires separate sessions or a direct query against CSI_COUNTERS_TL.