Search Results capture_ctr_prop_reading_post




Overview
Explore in AI Chat

Overview

The APPS.JTM_CTR_CAPTURE_READING_VUHK package is a PL/SQL API belonging to the Oracle E-Business Suite Transportation Management (formerly ETRM / Oracle Transportation Management) module. Its name partitions into clear semantic segments: JTM denotes the Transportation Management schema prefix, CTR refers to "counter," CAPTURE and READING describe the business activity, and the VUHK suffix identifies the specific implementation subtype (a naming convention Oracle historically applied to regional or functional variants of the same logical API). The package exists to record and maintain counter readings — the odometer, meter, or usage measurements captured against transportation equipment and assets — and to post or update those readings through a standardized, message-list-driven API contract.

The package is declared with AUTHID CURRENT_USER, meaning it executes with the privileges of the calling user rather than the definer, which is a common pattern for API packages intended to be invoked from multiple schemas or through concurrent processing contexts. Its header carries the standard Oracle version string and is marked noship, indicating it is an internal, non-shipped artifact not intended for direct customer modification.

Key Procedures and Functions

The documented package exposes six procedures across four distinct names (two names are overloaded):

  • CAPTURE_COUNTER_READING_POST — Records a new counter reading for a counter group after successful validation. This is the primary "post" handler for capturing readings.
  • UPDATE_COUNTER_READING_PRE — Pre-update processing invoked before a counter reading record is committed. Two overloaded signatures exist, differing in whether an object version number is supplied for optimistic locking.
  • UPDATE_COUNTER_READING_POST — Post-update processing executed after a counter reading has been modified. Like the PRE variant, it is overloaded with and without an object version parameter.
  • CAPTURE_CTR_PROP_READING_POST — Captures a counter property reading, extending the base capture operation to property-level measurements rather than a simple counter value.

All procedures share a common API contract: an API version number, an initialization message list, a commit flag, a validation level, a counter group log identifier, and three standard output parameters (X_Return_Status, X_Msg_Count, X_Msg_Data). This is the classic EBS PL/SQL API error-handling pattern, allowing callers to inspect status and accumulated messages.

Tables Accessed

Per the documented metadata, the package references two objects through APPS synonyms:

  • JTF_HOOKS_DATA — Part of the JTF (Java Tools Framework) extensibility layer, used to store hook or extension data. Its presence suggests the package participates in a hook-based extension point, likely allowing custom logic to augment counter-reading processing.
  • DBMS_SQL — The Oracle-supplied dynamic SQL package, indicating that at least one procedure constructs and executes SQL dynamically rather than through static statements. This is typically used for flexible query construction against counter and reading tables whose columns vary by configuration.

Usage Notes

This package is not a public, documented EBS API and is marked noship; it is referenced by zero other packages according to the metadata. It is therefore best understood as an internal helper invoked during counter-reading capture workflows — most plausibly from Transportation Management equipment/counter forms or from the concurrent programs that process captured readings in batch. Because it relies on AUTHID CURRENT_USER and dynamic SQL, any custom code invoking it must ensure the executing user has appropriate grants on the underlying counter tables and on JTF_HOOKS_DATA. Developers should treat the signature as fixed for the documented release (12.1.1 / 12.2.2) and wrap calls in standard message-list handling to interpret X_Return_Status and X_Msg_Data.