Search Results create_meter_reading

Overview

APPS.EAM_METERREADING_PUB is the public PL/SQL application programming interface for meter reading maintenance within Oracle Enterprise Asset Management (EAM). The package header declares AUTHID CURRENT_USER, meaning that execution privileges and unqualified name resolution follow the invoking schema rather than the package owner, which is a standard convention for EAM public APIs that must respect caller context. Per its embedded header comment, the package is used to create and disable meter readings. It exposes two documented key procedures, create_meter_reading and disable_meter_reading, both of which first validate and massage the IN parameters before carrying out the respective operation. The package is registered under the EAM product with a public scope, an active lifecycle, and the display name "Meter Reading package," and it owns the business entity designation EAM_METER_READING. Its API classification is PUB, making it the sanctioned entry point for external callers that need to insert or deactivate counter readings associated with EAM assets without writing directly to the underlying counter tables.

Key Procedures and Functions

The documented interface contains three program units, of which two are the principal public procedures:

• CREATE_METER_READING — Creates a meter reading record. The procedure validates and massages the incoming parameters and then performs the insert operation against the counter reading structures. The package defines the Meter_Reading_Rec_Type record to carry the reading payload, including meter_id, current_reading, current_reading_date, reset_flag, description, work order linkage fields such as wip_entity_id, check-in/check-out fields, adjustment attributes, reset reason, and the DFF attribute columns 1 through 28 (attribute category, attribute1–attribute15, and the extended attribute16–attribute28 columns).
• DISABLE_METER_READING — Disables an existing meter reading, applying the same validation and massaging discipline before carrying out the deactivation.

The metadata records a total of three documented procedures or functions for the package; the two above are the named key procedures identified in the source header and in the ETRM object registry. Parameter lists are not enumerated in the metadata and should be confirmed against the deployed package specification.

Tables Accessed

The package references the following tables through APPS synonyms:

• CSI_COUNTER_ASSOCIATIONS — associates counters (meters) with the entities they measure; used to validate the meter identified in the reading record.
• CSI_COUNTER_READINGS — the principal store of counter reading values and dates; the target of the create operation and the subject of the disable operation.
• CSI_COUNTER_RELATIONSHIPS — defines relationships between counters, supporting validation of rollup or dependency logic when a reading is captured.
• WIP_DISCRETE_JOBS — supports readings captured in a work order or discrete job context, consistent with the wip_entity_id field in the reading record.
• PLITBLM — the standard EBS PL/SQL index-by table used as a bind array for bulk DML, indicating the package performs set-based inserts or updates rather than row-at-a-time processing.

Usage Notes

EAM_METERREADING_PUB is invoked as a public API from EAM meter reading entry forms, from concurrent programs that import or mass-load readings, and from custom code that integrates external meter or sensor data into EAM. Because the procedure validates and massages parameters before writing, callers should populate the reading record fully — meter identifier, reading value, reading date, and any work order or adjustment context — and let the API apply its internal defaults and checks. The package is referenced by five other packages, indicating it is a shared dependency within the EAM meter reading stack rather than an isolated utility. Direct DML against CSI_COUNTER_READINGS should be avoided in favor of this API to preserve validation and downstream consistency. The package is documented for both Oracle EBS 12.1.1 and 12.2.2; the header revision predates 12.2, so implementers should verify the installed specification in each environment when binding to the record type or procedure signatures.