Search Results capture_counter_reading_post

Overview

APPS.CSI_COUNTER_READINGS_VUHK is a vertical-hook (VUHK) stub package body in the Oracle E-Business Suite 12.1.1 / 12.2.2 Customer Intelligence (CSI) schema. It provides an extension point in the counter reading capture and update workflow, allowing customers and integrators to insert custom business logic without modifying Oracle-owned code. The package belongs to the CSI counter readings API family, whose public interfaces (such as Capture_Counter_Reading and Update_Counter_Reading) are exposed through the CSI_CTR_DATASTRUCTURES_PUB data structures and the CSIVHCRB file header lineage (release 120.0, dated 2005/06/10). In the delivered form, the procedures are intentionally empty: each simply initializes x_return_status to FND_API.G_RET_STS_SUCCESS, so the pre- and post-hooks succeed without side effects unless a customer extends them. The object is classified as OTHER API in ETRM and is marked "noship," confirming it is a seeded, non-transactional hook rather than a functional business API.

Key Procedures and Functions

The package body documents four extension procedures, arranged as pre/post pairs around the counter reading lifecycle:

• CAPTURE_COUNTER_READING_PRE — the pre-processing hook invoked before a counter reading is captured. It accepts the standard API parameters plus the transaction, counter readings, and counter property readings tables, and returns the standard FND_API return status, message count, and message data.
• CAPTURE_COUNTER_READING_POST — the post-processing hook executed after capture completes. It exposes the same transaction and readings table parameters and return values, enabling validation, enrichment, or downstream notification logic.
• UPDATE_COUNTER_READING_PRE — the pre-processing hook for counter reading updates, receiving the counter readings table and standard API arguments.
• UPDATE_COUNTER_READING_POST — the post-processing hook for updates, mirroring the pre-hook signature and returning the standard API status values.

All four procedures follow the FND_API error-handling convention. No custom validation, messaging, or table manipulation is delivered in the seeded body.

Tables Accessed

ETRM metadata records no direct table references for this package body via APPS synonyms, which is consistent with a hook package that operates purely on PL/SQL collection types. The parameters reference csi_datastructures_pub.transaction_tbl, csi_ctr_datastructures_pub.counter_readings_tbl, and csi_ctr_datastructures_pub.ctr_property_readings_tbl, which carry transaction and counter reading data in memory between the caller and the hook. Because the delivered body contains no DML, no base tables are read or written; any persistent access would be introduced only by customer customization logic.

Usage Notes

The package is invoked automatically by the CSI counter reading APIs through the vertical-hook mechanism whenever a counter reading is captured or updated, provided the hook is registered/enabled. It is not called directly by end users. Typical extension scenarios include adding custom validation in the pre-hooks, updating or deriving counter property values, writing to custom audit tables, or triggering downstream integrations in the post-hooks. The package is referenced by two other packages, indicating it participates in a wider CSI API call chain. Because the delivered procedures are empty and safely return success, customization should preserve the FND_API return-status contract and raise errors through the standard message stack. Customizations should be documented and reapplied after patching, since "noship" seed objects may be overwritten during upgrades.