Search Results eam_metr_processor




Overview
Explore in AI Chat

Overview

APPS.EAM_METR_PROCESSOR is a PL/SQL package within the Oracle Enterprise Asset Management (EAM) module. Its business function is to process incoming meter reading data and apply it to the appropriate asset meter records in Oracle EBS. Enterprise Asset Management relies on accurate meter readings to track usage, runtime, and other measurement-based values for assets, which in turn drive preventive maintenance schedules and condition-based maintenance triggers. This package serves as the processing bridge between meter reading data captured at the interface level and the validated meter reading records stored in the EAM application tables.

The package is owned by the APPS schema and is classified as an OTHER API type in the ETRM documentation for 12.2.2. Its status is VALID, confirming that it is a compiled, active object in the E-Business Suite instance. In Oracle EBS 12.1.1, this package operates within the same overall EAM meter processing architecture, and its role remains consistent: transforming staged or imported meter reading requests into permanent EAM meter reading records while capturing any processing errors through the standard WIP interface error mechanism.

Key Procedures and Functions

The package exposes a single documented procedure:

  • PROCESS_METER_READING_REQUESTS — This procedure drives the processing of pending meter reading requests. It reads meter reading data staged in the interface tables, validates and transforms that data, writes valid records into the EAM meter reading tables, and records processing failures into the WIP interface errors table. It encapsulates the bulk of the package's business logic and is the primary entry point for meter reading request processing. No parameter list is documented in the ETRM metadata; the procedure is described here by purpose only.

Because the package body is not fully exposed in the documentation excerpt, additional private procedures may exist internally, but only PROCESS_METER_READING_REQUESTS is documented as the public interface procedure.

Tables Accessed

The package references the following documented tables through APPS synonyms:

  • EAM_METER_READINGS_INTERFACE — The staging table holding meter reading data awaiting processing. The package reads from this table to obtain the requests that require validation and application.
  • EAM_METER_READINGS — The base transaction table for meter readings. The package writes validated meter reading records here.
  • EAM_METER_READINGS_S — The sequence (or related supporting object) used to generate unique identifiers for new meter reading records.
  • WIP_INTERFACE_ERRORS — The standard EBS error log table. The package writes any processing errors encountered during meter reading validation into this table, providing a consistent error-handling mechanism shared with manufacturing and WIP interfaces.
  • WIP_INTERFACE_S — The sequence used to generate unique interface error identifiers.

These references confirm that the package is a data-loading routine: it consumes staged interface records, applies them to the core meter reading tables, and manages error capture through the widely used WIP interface framework.

Usage Notes

EAM_METR_PROCESSOR is typically invoked when meter reading data must be imported or processed in bulk. Common invocation points include:

  • Concurrent programs within the EAM module that submit meter reading import or processing jobs, where PROCESS_METER_READING_REQUESTS is called to process all pending interface records.
  • Custom code or interfaces that load data into EAM_METER_READINGS_INTERFACE and then call the procedure to validate and apply those readings.
  • Interface execution flows where external systems (such as handheld meter collection devices) feed readings into the interface tables, after which this package completes the processing cycle.

Because the package is referenced by zero other packages according to the ETRM metadata, its usage is generally driven from the top level via concurrent programs or direct custom invocations rather than through dependency chains. The only documented dependency is on SYS.STANDARD, indicating reliance on Oracle's built-in PL/SQL package. Error records written to WIP_INTERFACE_ERRORS should be reviewed and resolved after each processing run. When extending or troubleshooting meter reading processing, the interface and base tables should be checked to confirm whether records were successfully applied or logged as errors.