Search Results eam_meterreading_utility_pvt




Overview
Explore in AI Chat

Overview

APPS.EAM_METERREADING_UTILITY_PVT is the private utility package body within the Oracle Enterprise Asset Management (EAM) module that supports meter reading processing and related asset maintenance transactions. In Oracle EBS 12.1.1 and 12.2.2, the PVT suffix designates a private API layer whose procedures are intended for internal invocation by the EAM public APIs and concurrent processes rather than by external callers directly. The package encapsulates the low-level data manipulation and helper logic that the public meter reading interfaces depend upon, including the writing of meter reading records, maintenance of last service readings, counter hierarchy enabling and disabling, activity and genealogy updates, and the rebuild of work orders affected by meter-driven maintenance rules.

The object resides in the APPS schema with a status of VALID, and its dependency graph confirms a tightly coupled role within the EAM infrastructure. It depends on the public meter reading and meter APIs, the EAM process work order packages, the EAM error message utility, and the FND_API framework, indicating that it participates in the standard EAM API error handling and processing model.

Key Procedures and Functions

The ETRM documentation records eight procedures and functions within this package body:

  • PERFORM_WRITES — Coordinates the persistence of meter reading data collected during a processing cycle, acting as the central write routine for the package.
  • INSERT_ROW — Performs insertion of a meter reading or related utility row into the target structures managed by the package.
  • UPDATE_LAST_SERVICE_READING — Maintains the last service reading value associated with an asset or meter, supporting preventive maintenance trigger evaluation.
  • ENABLE_SOURCE_METER — Activates a source meter, typically in the context of counter associations and relationships used to derive readings.
  • DISABLE_COUNTER_HIERARCHY — Deactivates a counter hierarchy, removing or suspending the association logic used to roll up or derive meter values.
  • UPDATE_ACTIVITY — Updates the maintenance activity information linked to meter reading processing, ensuring the work management record reflects current readings.
  • UPDATE_GENEALOGY — Maintains the asset genealogy relationships affected by meter-driven maintenance activity, delegating to the EAM genealogy package where required.
  • UPDATE_REBUILD_WORK_ORDER — Handles regeneration or rebuilding of work orders when meter readings trigger maintenance requirements.

Tables Accessed

The package references several core EAM and installed base tables through APPS synonyms:

  • CSI_COUNTER_ASSOCIATIONS — Stores the associations between counters and meters; read and updated to enable source meters and manage counter relationships.
  • CSI_COUNTER_RELATIONSHIPS — Defines relationships between counters, used when enabling or disabling counter hierarchies.
  • CSI_ITEM_INSTANCES — The installed base instance records representing the assets against which meter readings are recorded and service readings maintained.
  • WIP_DISCRETE_JOBS — The work order header records consulted or modified when rebuilding work orders driven by meter readings.
  • PLITBLM — A PL/SQL internal table type used within the package for in-memory collections during row processing.

Usage Notes

Because EAM_METERREADING_UTILITY_PVT is classified as a PVT (private) API, it is not intended for direct invocation by customer extensions. It is invoked internally by the public EAM meter reading APIs, notably EAM_METERREADING_PUB and EAM_METER_PUB, as well as by EAM work order processing packages such as EAM_PROCESS_WO_PUB and EAM_PROCESS_WO_PVT. Meter reading entry forms, the EAM meter reading concurrent programs, and preventive maintenance scheduling flows ultimately drive execution of these procedures through the public layer.

The package uses FND_API and EAM_ERROR_MESSAGE_PVT for error capture and message propagation, so any failure surfaces through the standard EAM error stack. It is documented as not referenced by any other database object and is referenced by one other package. Customizations should target the supported public APIs rather than this private utility, and should preserve the dependency references to CSI, WIP, and the EAM public packages.