Search Results eam_meterreading_validate_pvt




Overview
Explore in AI Chat

Overview

EAM_METERREADING_VALIDATE_PVT is a private (PVT) PL/SQL package owned by APPS within the Oracle Enterprise Asset Management (EAM) module of Oracle E-Business Suite Release 12.1.1 and 12.2.2. Its source file, EAMVMTVS.pls, was first created in February 2005 and carries a version header dated July 2008 (120.1.12010000.1). As its name indicates, the package is a validation utility that enforces business rules governing meter readings captured against EAM assets. Meter readings are periodic counter values recorded for tracked assets—run hours, miles, cycles, and similar measures—and they drive preventive maintenance scheduling and condition-based work order generation. Before such readings are accepted by the processing layer, the data must be checked for completeness and consistency. EAM_METERREADING_VALIDATE_PVT encapsulates that logic, exposing it to the public processing packages (notably EAM_PROCESS_WO_PUB, whose record types appear in the signatures) while keeping the validation internals private to the EAM schema. The package declares AUTHID CURRENT_USER, meaning it executes with the privileges of the calling session rather than the defining schema, and it exposes a single PL/SQL collection type, counter_id_tbl_type, used internally to pass sets of counter identifiers.

Key Procedures and Functions

  • CHECK_REQUIRED — Accepts a single meter reading record (typed as EAM_PROCESS_WO_PUB.eam_meter_reading_rec_type) and validates that all mandatory attributes required for the reading are populated. It returns a status value indicating success or failure together with a message token table (EAM_ERROR_MESSAGE_PVT.Mesg_Token_Tbl_Type) that carries the localized error text. This procedure is the gateway check applied before a reading can be persisted.
  • MANDATORY_ENTERED — Evaluates whether mandatory meter readings have actually been entered for a work order. It operates on a work order identified by entity ID and instance ID, against a full meter reading table (EAM_PROCESS_WO_PUB.eam_meter_reading_tbl_type) and a work order completion date. It returns both a status and a boolean flag (x_man_reading_enter) indicating whether the mandatory reading requirement has been satisfied, allowing the caller to block completion if required readings are missing.

Tables Accessed

The package reads and validates against the core EAM counter model. CSI_COUNTERS_B holds the counter definitions and their attributes, providing the metadata against which entered values are checked. CSI_COUNTER_ASSOCIATIONS links counters to the assets or maintaining organizations that use them, determining which counters are expected to have readings. CSI_COUNTER_RELATIONSHIPS captures parent-child or rollup relationships between counters, which affect whether aggregate readings are consistent. CSI_COUNTER_READINGS stores the historical reading values and is consulted to verify continuity and detect regressions. PLITBLM is an Oracle Applications standard PL/SQL index-by table used to pass token substitution values for error message formatting, supporting the message token table returned by CHECK_REQUIRED. The CSI_* aliases resolve through APPS synonyms in a correctly configured environment.

Usage Notes

EAM_METERREADING_VALIDATE_PVT is a private package and is not part of Oracle's published API surface; the documented reference indicates it is referenced by one other package, presumably the EAM work order public processing package that invokes these validations during work order completion and meter reading entry. Typical invocation paths include the EAM Work Order completion flow, whether driven from the Maintenance Workbench or technician forms, and the Meter Reading entry screens, which call the public EAM_PROCESS_WO_PUB APIs; those public calls in turn delegate validation to this private package. Concurrent programs that process or import meter readings may reach the package through the same public entry points. Custom code should not call EAM_METERREADING_VALIDATE_PVT directly, because private package signatures are not guaranteed across patch levels; customizations should invoke the supported public APIs and rely on this package only implicitly. Because the package runs with AUTHID CURRENT_USER, callers must have the necessary privileges on the underlying CSI tables when executing it, generally satisfied through the standard APPS grants.