Search Results cs_ctr_capture_reading_pub




Overview
Explore in AI Chat

Overview

The APPS.CS_CTR_CAPTURE_READING_PUB package body is a public (PUB) API within Oracle E-Business Suite's Enterprise Asset Management and Service/TeleService counter functionality. It is responsible for capturing, updating, and estimating counter readings — the periodic numeric measurements recorded against a counter (such as mileage, run-hours, cycles, or other usage metrics) that is associated with an installed asset or item instance. In Oracle EBS Release 12.1.1 and 12.2.2, this package functions as the sanctioned entry point for external callers, shielding them from lower-level private implementation logic exposed in CSI_COUNTER_READINGS_PVT. The PUB classification signals that this API is intended for direct invocation by forms, concurrent programs, and custom extensions, and its validity status confirms it is a compiled, supported database object in the APPS schema.

Key Procedures and Functions

The package exposes a documented set of procedures that together cover the full counter-reading lifecycle. The metadata lists nine members, seven of which are named explicitly:

  • CAPTURE_COUNTER_READING — The primary interface for recording a new counter reading against a counter, validating and persisting the value through the counter readings data model.
  • UPDATE_COUNTER_READING — Modifies an existing counter reading, typically used to correct or amend previously captured values.
  • PRE_CAPTURE_CTR_READING — A pre-processing hook that performs validation and setup before the actual capture, often used to enforce business rules or derive dependent values.
  • CAPTURE_CTR_PROP_READING — Captures readings for counter properties, extending the capture logic to counter-associated property attributes.
  • POST_CAPTURE_CTR_READING — Post-processing logic invoked after capture completes, such as propagating readings to dependent entities (for example, updating meter-linked transactions).
  • UPDATE_CTR_PROP_READING — Updates previously captured counter property readings.
  • ESTIMATE_COUNTER_READING — Derives or projects a reading when an actual measurement is unavailable, supporting forecast-based usage tracking.

Two additional documented members round out the set of nine. No parameter lists are asserted, as these are not provided in the source metadata.

Tables Accessed

Through APPS synonyms, the package reads and writes several core Oracle Service/CSI objects:

  • CSI_COUNTER_ASSOCIATIONS — Defines the relationship between counters and the items or assets they measure, establishing which readings are valid.
  • CSI_COUNTER_PROPERTIES_B — The base table holding counter property definitions used to resolve property-level readings.
  • CSI_TRANSACTIONS — Records transactions against counters, supporting linkage of readings to asset usage events.
  • PLITBLM — The standard PL/SQL table (index-by table) utility used internally for bulk operations.

The package also depends on CSI_COUNTER_READINGS_PUB, CSI_COUNTER_READINGS_PVT, CSI_CTR_DATASTRUCTURES_PUB, CSI_CTR_GEN_UTILITY_PVT, CSI_DATASTRUCTURES_PUB, FND_API, and FND_MSG_PUB, consistent with EBS API conventions for error messaging and data-structure handling.

Usage Notes

This public API is typically invoked from Oracle Service and Asset forms when end users enter counter or meter readings, and from concurrent programs or interface programs that load readings in bulk. Because it is classified PUB and is referenced by ten other packages, custom code and integrations should call CS_CTR_CAPTURE_READING_PUB rather than the private counter-readings package. Standard FND_API message handling applies, so callers should check the returned API status. The package is not referenced by any database object, confirming it is a top-level entry point rather than a dependent subroutine.