Search Results csi_counter_readings_pub




Overview
Explore in AI Chat

Overview

CSI_COUNTER_READINGS_PUB is the public PL/SQL API for managing counter readings within the Oracle E-Business Suite Enterprise Asset Management (EAM) and asset tracking modules. Its business purpose is to provide a supported, encapsulated interface for capturing, creating, and updating counter readings and the property readings associated with them. Counters are used to record accumulated usage values on assets, meters, or other tracked entities — for example, odometer values, run hours, or production quantities. The package name is classified as a PUB API and is owned by APPS, meaning it is intended for direct invocation by external callers, forms, concurrent programs, and custom code rather than being an internal implementation detail. The package carries the display name "Manage Counter Readings," an active lifecycle, and a compatibility rating of S. It operates within the CSI product family and is concerned with the BUSINESS_ENTITY of CSI_COUNTER. Because the API encapsulates the creation and update logic, callers are insulated from the underlying table structures and business rules for counter processing.

Key Procedures and Functions

The documented API exposes two procedures:

  • CAPTURE_COUNTER_READING — Processes a supplied counter reading. The reading may represent a regular counter reading, an adjustment, a reset, or an automatic rollover. In addition to storing the counter reading itself, the procedure captures the property readings of the underlying properties of the counter and computes formula and target counter readings. The procedure receives parameters that include API version, commit and message-initialization flags, validation level, a transaction table, a counter reading table conveying the nature of the reading, and a corresponding property reading table, together with the standard return status, message count, and message data outputs.
  • UPDATE_COUNTER_READING — Modifies an existing counter reading through the same public API surface. This is the procedure most commonly targeted by users searching for "update_counter_reading," and it should be used in preference to direct DML against the underlying readings table.

Both procedures follow the standard EBS API conventions, including the return status and message stack outputs that allow callers to detect and handle errors.

Tables Accessed

The package reads and writes several CSI tables through APPS synonyms:

  • CSI_COUNTER_READINGS — the primary store of counter reading values that the API creates and updates.
  • CSI_CTR_PROPERTY_READINGS — holds property readings captured alongside the counter reading.
  • CSI_COUNTERS_B — the base counter definition, used to validate and resolve the counter being processed.
  • CSI_COUNTER_PROPERTIES_B — the base property definitions underlying the counter, used when capturing property readings.
  • CSI_COUNTER_RELATIONSHIPS — counter-to-counter relationships used by formula and target computation.
  • PLITBLM — the standard EBS message/PL-SQL table used by the API for message handling.

Usage Notes

CSI_COUNTER_READINGS_PUB is normally invoked from Oracle EAM and asset tracking forms, from concurrent programs that process meter or counter data, or from custom PL/SQL code that needs to record counter readings. It is referenced by six other packages, which confirms its role as a foundational API within the CSI schema. When integrating, callers should respect the API call sequence: set the initialization and commit flags appropriately, set the validation level, and inspect x_return_status and the message stack on return. Direct DML against CSI_COUNTER_READINGS should be avoided because the API enforces the business rules for adjustments, resets, rollovers, formula computation, and property readings that the underlying tables do not enforce on their own.