Search Results reading_values
Overview
EAM_METR_VALIDATOR is an Oracle Application Object Library PL/SQL package owned by the APPS schema and classified under ETRM as an OTHER API. It is a component of the Enterprise Asset Management (EAM) meter reading subsystem within Oracle E-Business Suite 12.1.1 and 12.2.2. The package encapsulates the validation logic that governs how meter readings captured against assets, work orders, and organizations are admitted into the EAM meter reading tables. In an EAM implementation, meter readings drive preventive maintenance scheduling, condition-based maintenance triggers, and asset utilization tracking, so ensuring that each reading is internally consistent and correctly attributed is critical to downstream maintenance planning.
The package operates as a subordinate utility rather than as a standalone business API. It depends only on the SYS.STANDARD package, indicating that its internal logic relies on standard PL/SQL constructs, and it is itself referenced by the EAM_METR_PROCESSOR package and by its own package body. This dependency pattern confirms its role as a shared validation service invoked by the meter processing layer before records are committed.
Key Procedures and Functions
The ETRM metadata documents fifteen procedures and functions within the package. These can be grouped by purpose rather than by individual signature:
- VALIDATE — The principal validation entry point. It applies the package's business rules to an incoming meter reading before it is accepted for processing.
- POPULATE_READING — Populates reading-related attributes on the record under validation, assembling the values required for downstream processing.
- POPULATE_WHO — Populates the standard "WHO" audit columns (creation and update attribution) on the record being handled.
- LAST_UPDATED_BY_NAME / LAST_UPDATED_BY — Retrieve the name and identifier of the user who last updated the record, supporting audit reporting and traceability.
- CREATED_BY_NAME / CREATED_BY — Retrieve the name and identifier of the user who created the record, complementing the update audit pair.
- ORGANIZATION_CODE / ORGANIZATION_ID — Resolve and validate the inventory organization context for the meter reading, converting between the coded and numeric representations.
- WORK_ORDER_NAME_ID — Resolves the work order reference associated with the reading, mapping between the descriptive name and the internal identifier.
- METER_NAME / METER_ID — Resolve the meter reference for the reading, converting between meter name and meter identifier.
- READING_DATE — Handles the effective date of the meter reading, which determines its position in the asset's reading history.
- RESET_FLAG — Evaluates the reset indicator, which signals that an asset has been reset and that accumulated meter values must be interpreted accordingly.
- READING_VALUES — Processes the reading value payload, including cumulative or incremental values associated with the meter.
Tables Accessed
The package accesses four tables through APPS synonyms:
- EAM_METERS — The meter definition table. It supplies meter attributes and confirms that the referenced meter is valid and active for the organization and asset.
- EAM_METER_READINGS — The destination table for validated readings, holding the historical meter reading records used by maintenance scheduling.
- EAM_METER_READINGS_INTERFACE — The staging interface table through which externally sourced or bulk-loaded readings arrive before validation and transfer into the main readings table.
- MTL_PARAMETERS — The inventory organization parameters table, used to validate and resolve organization context for the reading.
Usage Notes
EAM_METR_VALIDATOR is not intended for direct invocation by end users or custom concurrent programs. It is called by EAM_METR_PROCESSOR, the processing package responsible for handling meter reading intake, including readings submitted through the EAM meter reading interface. Customizations that extend meter reading behavior should route through EAM_METR_PROCESSOR or the supported interface tables rather than calling EAM_METR_VALIDATOR procedure directly, since internal validation sequences and error handling expectations are governed by the calling processor. The package remains VALID in the APPS schema in both 12.1.1 and 12.2.2, with no documented change in its procedure inventory between those releases.