Search Results is_meter_reading_required_v
Overview
APPS.EAM_METERS_UTIL is a utility PL/SQL package within the Oracle E-Business Suite Enterprise Asset Management (EAM) module. Its primary business function is to centralize the logic that governs asset meter and counter behavior: validating whether meter readings are required or mandatory, computing usage rates and averages, maintaining last service dates and readings, and enforcing the rules surrounding meter resets. In EBS 12.1.1 and 12.2.2 the package is classified as a UTIL API, meaning it is not an end-user facing interface but an internal helper layer called by higher-level meter APIs, work order processing logic, and JSP-based user interfaces. Its existence ensures that consistent meter semantics are applied across preventive maintenance scheduling, work order completion, and counter reading entry, rather than duplicating validation logic in each calling program.
Key Procedures and Functions
The package exposes 28 documented procedures and functions. These can be grouped into four functional areas:
- Mandatory/Required reading checks — IS_METER_READING_MANDATORY, IS_METER_READING_MANDATORY_V, IS_METER_READING_REQUIRED, IS_METER_READING_REQUIRED_V, and HAS_MANDATORY_METER_READING determine whether a meter reading must be supplied for a given asset or activity. The _V variants typically operate in a validation context.
- Usage and average calculations — GET_METER_USAGE_RATE and GET_AVERAGE compute consumption rates and rolling averages from stored counter readings, which feed preventive maintenance interval calculations.
- Last service maintenance — UPDATE_LAST_SERVICE_READING, UPDATE_LAST_SERVICE_READING_WO, UPDT_LAST_SRVC_DATES_WO_WPR, UPDATE_LAST_SERVICE_DATES, and UPDATE_LAST_SERVICE_DATES_WO persist the reading and date values associated with the most recent preventive maintenance service, both in general and in the specific context of work orders.
- Reset and continuing reading validation — RESET_METER, CANNOT_ENTER_VALUE, CANNOT_UPDATE_RESET, RESET_READING_EXISTS, NORMAL_READING_BEFORE_RESET, NEXT_READING_EXISTS, READING_EXISTS, and UPDATE_CHANGE_METER_LTD enforce the business rules that constrain resets, prevent invalid sequencing of readings around a reset, and guard against updates to already-inconsistent meter data.
The package also references itself, indicating recursive or internal helper usage.
Tables Accessed
Through APPS synonyms the package reads and writes the core EAM and CSI meter tables. CSI_COUNTERS_B, CSI_COUNTER_ASSOCIATIONS, and CSI_COUNTER_READINGS store the counter definitions, asset-to-counter associations, and the actual reading history against which all usage, average, and reset logic is evaluated. EAM_PM_ACTIVITIES, EAM_PM_SCHEDULINGS, EAM_PM_SCHEDULING_RULES, and EAM_PM_LAST_SERVICE support the preventive maintenance scheduling and last-service tracking functions. EAM_SUPPRESSION_RELATIONS defines suppression behavior, EAM_WORK_ORDER_DETAILS and MTL_EAM_ASSET_ACTIVITIES tie meter data to work order execution and asset activity, and WIP_DISCRETE_JOBS links meter consumption to manufacturing job tracking.
Usage Notes
EAM_METERS_UTIL is referenced by eleven other packages, including CSI_COUNTER_PVT, CSI_COUNTER_READINGS_PUB, CSI_COUNTER_READINGS_PVT, CSI_COUNTER_TEMPLATE_PVT, EAM_METERREADING_UTILITY_PVT, EAM_METERREADING_VALIDATE_PVT, EAM_METER_READINGS_JSP, EAM_METR_VALIDATOR, EAM_WORKORDERREP_PVT, EAM_WO_COMP_UTILITY_PVT, and the EAM_RUNTIME_INTERVAL_V view. This confirms that the package is invoked from counter public APIs, meter reading validation and utility layers, the JSP-based meter reading entry user interface, work order reporting, and work order completion processing. Custom code should not generally call EAM_METERS_UTIL directly; instead developers should invoke the documented public APIs such as CSI_COUNTER_READINGS_PUB, which in turn delegate to this utility. Direct invocation risks bypassing validation sequencing enforced at higher layers and is not supported for external integration.