Search Results jtm_mob_apps_enabled

Overview

CS_CTR_CAPTURE_READING_VUHK is an Oracle E-Business Suite PL/SQL package body owned by APPS and classified as an "OTHER" API within the ETRM (Enterprise Territory and Channel Management) module. Its principal business function is to support the capture and update of counter readings and property readings associated with service contracts, field service activities, and installed base assets. In the EBS 12.1.1 and 12.2.2 environments, this package acts as a thin wrapper or hook layer around the public API CS_CTR_CAPTURE_READING_PUB, providing pre- and post-processing logic that executes before and after the core public API calls.

The "VUHK" suffix indicates this is a version-specific or customer-oriented implementation of the counter reading capture logic. The header comment ($Header: jtmcncpb.pls 120.2 2005/08/24) confirms the file is an older source member carried forward into the modern EBS release, with a last modification date well before the 12.x code line. The package therefore represents stable, long-lived instrumentation around counter and property reading transactions, and is referenced by zero other packages, indicating it is invoked directly by external callers rather than being a shared dependency.

Key Procedures and Functions

The package exposes sixteen documented procedures, organized as pre/post hook pairs around major counter and property reading business events:

• CAPTURE_COUNTER_READING_PRE — Pre-processing hook executed before a new counter reading is captured. In the documented source it simply initializes the return status to FND_API.G_RET_STS_SUCCESS.
• CAPTURE_COUNTER_READING_POST — Post-processing hook executed after a counter reading is captured. This is the primary functional routine, containing logic to read the JTM_MOB_APPS_ENABLED-style profile setting, build a dynamic SQL buffer, and log messages through JTM_MESSAGE_LOG_PKG.
• UPDATE_COUNTER_READING_PRE / UPDATE_COUNTER_READING_POST — Pre- and post-processing hooks that bracket updates to existing counter readings.
• PRE_CAPTURE_CTR_READING_PRE / PRE_CAPTURE_CTR_READING_POST — Hooks invoked around the preliminary capture phase of counter reading data, typically used before the main capture transaction begins.
• CAPTURE_CTR_PROP_READING_PRE / CAPTURE_CTR_PROP_READING_POST — Hooks surrounding the capture of counter and property readings together, supporting assets that carry both meter and attribute reading data.
• POST_CAPTURE_CTR_READING_PRE / POST_CAPTURE_CTR_READING_POST — Hooks that execute after the primary capture processing, used for downstream validation, logging, or interface hand-off.
• UPDATE_CTR_PROP_READING_PRE / UPDATE_CTR_PROP_READING_POST — Hooks that bracket updates to combined counter and property reading records.

Each procedure follows the standard EBS API signature conventions, accepting an API version number, initialization message list, commit flag, validation level, and the relevant CTR_GRP_LOG, CTR_RDG, and PROP_RDG record or table types, while returning status, message count, and message data out-parameters.

Tables Accessed

The documented tables referenced through APPS synonyms are limited to DBMS_SQL. The package does not directly read or write contract counter reading base tables; instead it relies on the Oracle-supplied DBMS_SQL built-in package to construct and execute dynamic SQL at runtime. This design is consistent with a post-processing hook that must log diagnostic information or invoke profile-dependent logic without a hard-coded object dependency. Message logging is delegated to JTM_MESSAGE_LOG_PKG, which in turn writes to the JTM message log infrastructure rather than to a contract table directly. Because the package is a hook layer, the actual counter and property reading rows are persisted by CS_CTR_CAPTURE_READING_PUB and its underlying tables, not by this unit.

Usage Notes

CS_CTR_CAPTURE_READING_VUHK is not referenced by any other package, so it must be invoked either from an Oracle Forms trigger, a concurrent program, or custom integration code that calls the counter reading capture flow. The "VUHK" naming and the older header record suggest it may have originated as a field service or telemetry interface adapter. Practitioners searching on "jtm_mob_apps_enabled" will find that this package reads a similarly named profile value in its post-processing routine and uses it to gate dynamic SQL execution, indicating deployment in mobile-enabled or telemetry-driven counter reading scenarios. When troubleshooting counter or property reading capture failures in 12.1.1 or 12.2.2, the JTM message log entries written by CAPTURE_COUNTER_READING_POST should be inspected first, as they capture SQLERRM output. Because the pre-hooks are largely pass-through and return success unconditionally, validation failures are more likely surfaced by the public API or by the post-processing log.