Search Results get_adjacent_reading

Overview

The APPS.EAM_METER_READINGS_JSP package body is an internal helper package within the Oracle E-Business Suite Enterprise Asset Management (EAM) module. It supports the Java Server Page (JSP) based user interface used by maintenance personnel to record and view meter readings for assets and equipment. Meter readings form the backbone of condition-based and usage-based maintenance strategies in EAM: they capture cumulative values such as hours run, mileage, or units produced, which drive preventive maintenance scheduling, meter-based work order generation, and asset performance reporting.

This package encapsulates the server-side PL/SQL logic that would otherwise reside in the JSP layer, keeping UI logic thin while centralizing reading-processing rules. It validates whether a meter reading is mandatory for a given asset/meter combination, determines the most recent historical reading, and inserts new rows into the meter readings table. The package is classified as OTHER in the API taxonomy, meaning it is not a formally supported public API but rather an internal component of the EAM self-service and maintenance web pages. It is currently VALID in the APPS schema and references seven documented procedures/functions.

Key Procedures and Functions

• HAS_MANDATORY_METER_READING — Determines whether any mandatory meter reading requirement exists in the current context, typically scoped to the asset or work order being processed.
• IS_METER_READING_MANDATORY — Evaluates whether a specific meter reading is mandatory for a given asset and meter, enabling the UI to enforce entry before allowing completion of a maintenance transaction.
• GET_LATEST_METER_READING_ID — Retrieves the identifier of the most recent meter reading, providing the baseline for validating new readings (e.g., rejecting decreasing values where not permitted).
• INSERT_ROW — Performs the physical insert of a new meter reading row into the underlying table, applying standard EAM validation and WHO-column stamping via FND_GLOBAL.
• GET_CURRENT_READING_DATA — Returns the current reading information for display on the JSP page, including the last recorded value and associated meter attributes.
• CHECK_ASSET_METER_ASSOCIATION — Verifies that a meter is validly associated with the referenced asset before allowing a reading to be captured.
• GET_ADJACENT_READING — Retrieves the reading immediately preceding or following a reference reading, supporting navigation through reading history.
• ADD_METER_READING — The primary entry point that orchestrates validation and insertion of a new meter reading, invoking the helper procedures above.

Tables Accessed

• EAM_METERS — Source of meter definition data including meter type, unit of measure, and rollover characteristics.
• EAM_METER_READINGS — The base table storing historical reading values; INSERT_ROW and ADD_METER_READING write here, while GET_LATEST_METER_READING_ID and GET_ADJACENT_READING read from it.
• EAM_METER_READINGS_S — A sequence or secondary/summary object referenced by the package; it supports generation of reading identifiers and is the object most closely matching the user's search string.
• WIP_DISCRETE_JOBS — Referenced to associate meter readings with discrete manufacturing jobs, enabling usage capture against production work orders.
• DUAL — Used for scalar evaluations and sequencing logic.

Additional dependencies include EAM_METERS_UTIL, EAM_DEBUG, EAM_EXECUTION_JSP, FND_API, FND_GLOBAL, and FND_MSG_PUB, which provide utility logic, debugging, API error handling, and message stack management.

Usage Notes

This package is invoked almost exclusively from the EAM JSP-based meter reading pages in the Maintenance and Self-Service responsibilities. It is not referenced by any other database object, confirming its role as a leaf-level UI support package. Customizations should treat it as private: direct calls are not supported, and any extension should be routed through the EAM public APIs or the JSP controller layer. Because the package depends on FND_GLOBAL and FND_MSG_PUB, it must be called within a properly initialized EBS session context (application, responsibility, and user) so that auditing columns and error messages resolve correctly. Its behavior is identical in 12.1.1 and 12.2.2, as the package remains valid and unchanged across those releases.