Search Results update_counter_reading_pre

Overview

CSI_COUNTER_READINGS_VUHK is a PL/SQL package body owned by APPS within the Oracle E-Business Suite, classified under the Enterprise Asset Management (EAM) and Asset Tracking domain. Its name reflects its role as a "VUHK" — a View User Hook — that is, a package of placeholder API entry points invoked at defined stages of the counter reading business flow to allow customer-specific or extension logic to be layered onto standard EBS processing without modifying Oracle-owned code. In Oracle EBS 12.1.1 and 12.2.2, this pattern is used pervasively to expose pre- and post-processing hooks around public APIs while preserving upgrade safety. The package supports the core Enterprise Asset Management sub-processes of capturing new counter readings and updating existing counter readings, which record accumulated meter or usage values for assets and asset activities. Its documented header ($Header: csivhcrb.pls 120.0) confirms it is a seeded, non-shipped ("noship") customer-extensible hook package that was intentionally delivered with empty implementations.

Key Procedures and Functions

ETRM documents four procedures, all following the Oracle Application Object Library API convention with p_api_version, p_commit, p_init_msg_list, p_validation_level, and standard x_return_status/x_msg_count/x_msg_data output parameters.

• Capture_Counter_Reading_Pre — The pre-processing hook fired before a counter reading is captured. Emptied at delivery; it simply sets x_return_status to FND_API.G_RET_STS_SUCCESS. Receives the transaction table and the counter reading and counter property reading tables as input.
• Capture_Counter_Reading_Post — The corresponding post-processing hook invoked after capture completes. Also returns success by default and takes the same transaction and reading table inputs.
• Update_Counter_Reading_Pre — The pre-processing hook fired before an existing counter reading is updated. This is the object of interest for searches on "update_counter_reading_pre."
• Update_Counter_Reading_Post — The post-processing hook fired after the update completes, receiving the counter reading table.

Tables Accessed

The package body itself performs no direct SQL against base tables. Instead, it passes strongly typed PL/SQL collections supplied by the public data structure packages: csi_datastructures_pub.transaction_tbl for transaction context, and csi_ctr_datastructures_pub.counter_readings_tbl and ctr_property_readings_tbl for the reading and associated property values. Because the shipped implementations are empty, no INSERT, UPDATE, or DELETE statements are issued by this package; the actual DML against the underlying CSI counter reading tables is performed by the calling public API (CSI_COUNTER_READINGS_PUB or its EAM counterparts), with this package serving only as an extension seam around that work.

Usage Notes

Because the procedures are placeholder hooks, they are typically invoked from within the standard counter reading public API flow rather than directly by end users. The ETRM metadata indicates the package is referenced by two other packages, confirming it is called programmatically during capture and update operations triggered from EAM asset workbench forms, the mobile/field service entry screens, or concurrent programs that import meter readings. Customers and partners extend it by adding code to the _Pre and _Post bodies — for example to validate readings, derive additional properties, trigger notifications, or synchronize with external systems. Any customization should avoid changing the documented signatures, as those are fixed by the calling API contract, and should respect the standard API error-handling protocol by populating x_return_status and the FND message stack. In 12.2.2, use the online patching-aware deployment model when modifying this package, since it resides in the APPS schema.