Search Results meter_description

Overview

APPS.EAM_RUNTIME_INTERVAL_V is a runtime interval view in Oracle E-Business Suite Enterprise Asset Management. It consolidates preventive maintenance (PM) scheduling rules with meter and counter definitions so that runtime interval logic can be queried directly without joining the scheduling, counter, and last-service tables manually. The view is used primarily for reporting on PM schedules driven by meter readings, and for integrations that must resolve a schedule's active meter, its unit of measure, its reading direction, and the runtime interval that governs when the next service becomes due.

The view exposes a meter_description column, which is one of the commonly searched attributes and corresponds to the description of the meter (counter) associated with a scheduling rule. This makes the view useful when users need to identify PM schedules by meter description rather than by internal counter identifiers.

Underlying Base Objects

The view is defined over the following documented base objects: CSI_COUNTERS_B, CSI_COUNTERS_TL, CSI_COUNTER_TEMPLATE_B, CSI_COUNTER_TEMPLATE_TL, EAM_PM_LAST_SERVICE, EAM_PM_SCHEDULINGS, and EAM_PM_SCHEDULING_RULES, and it calls the EAM_METERS_UTIL package. The definition is a UNION of two branches.

• The first branch joins EAM_PM_SCHEDULING_RULES to EAM_PM_SCHEDULINGS, EAM_PM_LAST_SERVICE, CSI_COUNTERS_B, and CSI_COUNTERS_TL. It filters for ccb.counter_type = 'REGULAR', enforces active-date range on the counter, and restricts the translation table to the session language via userenv('LANG').
• The second branch applies to template-based schedules, where eps.tmpl_flag = 'Y'. It joins to CSI_COUNTER_TEMPLATE_B and CSI_COUNTER_TEMPLATE_TL instead of the installed counter tables, and derives the usage rate from cctb.default_usage_rate.
• In the first branch, the user-defined rate is obtained through eam_meters_util.get_meter_usage_rate(ccb.counter_id); the second branch returns a NULL last_service_reading cast to NUMBER.

Key Columns

• rule_id, pm_schedule_id, rule_type — identify the PM scheduling rule and its type.
• activity_association_id — links to the last cyclic activity / last service record.
• meter_id, meter_name, meter_uom, meter_description — the counter and its translated name, unit of measure, and description.
• value_change_dir — the counter direction, indicating increasing or decreasing readings.
• runtime_interval — the interval value that drives PM scheduling.
• last_service_reading — the reading recorded at the last service; NULL for template-based rows.
• user_defined_rate — the meter usage rate (from EAM_METERS_UTIL or the template default).
• effective_reading_from, effective_reading_to, effective_date_from, effective_date_to — validity bounds for the rule.
• Audit columns: created_by, creation_date, last_update_login, last_update_date, last_updated_by.

Common Use Cases and Queries

Typical uses include identifying PM schedules by meter description, validating runtime intervals for a given meter, and feeding integrations that compute remaining usage before service is due.

SELECT pm_schedule_id, rule_id, meter_id, meter_name,
       meter_description, meter_uom, runtime_interval,
       last_service_reading, user_defined_rate
FROM   apps.eam_runtime_interval_v
WHERE  meter_description LIKE '%HOUR%';

Because the view already resolves the active counter, translation, last service, and rate, it removes the need for consumers to reproduce the multi-table join logic embedded in its definition.