Search Results jtm_handheld_wrapper_pkg




Overview
Explore in AI Chat

Overview

JTM_HANDHELD_WRAPPER_PKG is an Oracle E-Business Suite PL/SQL package body owned by the APPS schema that serves as a wrapper interface between the mobile field service handheld synchronization layer and the backend EBS database tables. It is part of the service mobility infrastructure, historically associated with the CRM Service (CSM) and Field Service (JTM) product families. The package provides the server-side entry points that are invoked when data originating from a mobile field service device must be applied to the backend using public APIs rather than direct table manipulation.

The package body is documented in ETRM with an API classification of OTHER. The header comment indicates the body was generated from the standard SQL Navigator PKGBODY template, and the source line carries the version tag $Header: jtmhwrpb.pls 120.1 2006/01/13, marking it as a shipped, long-standing component of the EBS codebase. The internal constant g_object_name is set to 'CSM_SERVICEP_WRAPPER_PKG', reflecting the package's lineage in the CSM Service application. In EBS 12.1.1 and 12.2.2 the package resides in the APPS schema and is subject to the standard editioning and online patching model of those releases.

Key Procedures and Functions

The documented package exposes four procedures or functions:

  • APPLY_CLIENT_CHANGES — This procedure is called by ASG_APPLY.PROCESS_UPLOAD when a publication item for the publication SERVICEL becomes dirty. This condition arises when a mobile field service device performs DML against an updatable table and executes a fast synchronization. The procedure is intended to detect which publication items became dirty and then invoke wrapper procedures that insert the mobile-originated data into backend tables through public APIs.
  • POPULATE_ACCESS_RECORDS — Described as the bootstrap procedure called by MDG upon CSM user creation. Its documented purpose is to iterate over the responsibilities assigned to a given CSM user and call CSM_WF_PKG.User_Resp_Post_Ins for each user/responsibility combination, thereby establishing the access records required for the mobile user.
  • DELETE_ACCESS_RECORDS — The counterpart bootstrap procedure to POPULATE_ACCESS_RECORDS. It is documented as being called by MDG upon CSM user deletion. Its stated purpose is likewise to iterate over the responsibilities assigned to the CSM user and invoke CSM_WF_PKG.User_Resp_Post_Ins, reflecting the symmetric user provisioning and de-provisioning workflow in the service mobility model.
  • CHECK_OLITE_SCHEMA — Listed in the ETRM inventory of documented objects for this package. Its specific parameters and logic are not detailed in the excerpted source, but its name indicates a schema validation or verification routine associated with the lightweight (OLite) mobile runtime environment.

Tables Accessed

ETRM records a single referenced table for this package: ALL_SYNONYMS, accessed via APPS synonyms. This reference is consistent with the CHECK_OLITE_SCHEMA routine, which would query the data dictionary to confirm that required object synonyms exist and resolve correctly before mobile synchronization proceeds. No other backend tables are documented as being directly referenced through this wrapper body; the design intent is that actual data population is delegated to wrapper procedures and public APIs rather than performed directly within this package.

Usage Notes

JTM_HANDHELD_WRAPPER_PKG is not an end-user-facing package. It is invoked programmatically in three principal circumstances:

  • During mobile field service fast synchronization, when ASG_APPLY.PROCESS_UPLOAD detects dirty publication items for publication SERVICEL and calls APPLY_CLIENT_CHANGES.
  • During CSM user provisioning, when MDG invokes POPULATE_ACCESS_RECORDS upon user creation.
  • During CSM user de-provisioning, when MDG invokes DELETE_ACCESS_RECORDS upon user deletion.

Because ETRM records zero packages referencing this object and no dependents, customizations should avoid direct calls and instead rely on the documented invocation paths. When debugging the search term "delete_access_records", the relevant entry point is the DELETE_ACCESS_RECORDS procedure described above, which is triggered by the MDG user-deletion bootstrap flow and is paired with POPULATE_ACCESS_RECORDS for the corresponding creation flow.