Search Results capture_readings




Overview
Explore in AI Chat

Overview

The APPS.CSI_TIME_BASED_CTR_ENGINE_PKG package is a server-side PL/SQL component within the Oracle E-Business Suite Install Base (CSI) module. It functions as the time-based counter engine for Oracle Enterprise Asset Management (eAM) and related counter-tracking functionality. In EBS 12.1.1 and 12.2.2, counters are used to record meter readings on assets and equipment — for example, machine hours, mileage, or units produced — and downstream maintenance and service logic depends on those readings being valid and current. This package encapsulates the business logic that determines when a new counter reading should be captured automatically based on elapsed time intervals, rather than relying solely on manual or event-driven entry. It is classified in the ETRM metadata as an "OTHER" API, indicating it is an internal engine rather than a formally published public interface. The package holds a VALID status in the APPS schema and carries Oracle Proprietary, Confidential Information markings.

Key Procedures and Functions

The ETRM 12.2.2 metadata documents a single public program unit for this package: CAPTURE_READINGS.

  • CAPTURE_READINGS — This procedure embodies the core time-based logic of the package. Its purpose is to evaluate counters that are configured for periodic or time-driven capture and generate the corresponding counter readings for eligible assets. It serves as the single entry point exposed by the engine, coordinating the identification of counters due for a reading and the creation or processing of those reading records. Because the package contains no additional documented procedures or functions, CAPTURE_READINGS is the sole documented invocation surface for the time-based counter engine.

The metadata does not publish parameter lists or detailed signatures for CAPTURE_READINGS; consumers should treat the package as an internal engine and avoid assuming a stable public interface.

Tables Accessed

According to the documented dependency data, the package reads and writes the following tables through APPS synonyms:

  • CSI_COUNTERS_B — The base table defining counters, including their configuration and time-based capture attributes.
  • CSI_COUNTER_READINGS — The transactional table where generated counter readings are stored.
  • CSI_COUNTER_READINGS_S — The sequence or supporting table associated with counter reading generation.
  • CSI_COUNTER_RELATIONSHIPS — Defines the relationships between counters and the assets or entities they measure.
  • CS_CSI_COUNTER_GROUPS — Groups of counters, used to drive capture across organized sets of counters.
  • DUAL — The standard Oracle single-row utility table, typically used for expression evaluation and sequencing.
  • PLITBLM — An APPS PL/SQL index-by table type reference used in the package's internal collections.

These dependencies confirm that the engine operates directly against the core Install Base counter entity and its reading transactional tables.

Usage Notes

The package is not documented as being referenced by any other Oracle package (0 referencing packages in the metadata), which reinforces its role as a self-contained engine invoked at a higher orchestration layer. Typical invocation scenarios include:

  • Concurrent programs — A scheduled concurrent request in the Install Base or eAM module is the most likely caller, running CAPTURE_READINGS to periodically generate readings for counters configured for time-based capture.
  • Forms-based entry — Assets or counter maintenance forms may trigger the engine when users manage counter definitions or request reading capture.
  • Custom extensions — Integrators who need automated meter reading generation may call the package from custom PL/SQL, but should do so cautiously given its "OTHER" API classification and the absence of a documented public signature.

Because the package is a proprietary internal engine and exposes only CAPTURE_READINGS, Oracle does not guarantee interface stability across releases. Any custom dependency should be validated against the specific EBS level (12.1.1 or 12.2.2) in use.