Search Results asg_cons_qpkg




Overview
Explore in AI Chat

Overview

ASG_CONS_QPKG is the consolidated callback package body in the Oracle E-Business Suite Field Service / TeleService mobile synchronization infrastructure. Its stated purpose, per the embedded header comment, is to contain callbacks registered with Oracle Lite. In practical terms, the package supplies the server-side PL/SQL entry points that the Oracle Lite (consolidated) client invokes during synchronization of a mobile device: download initialization, upload completion, conflict detection, purge handling, and login validation. The header history dates the bulk of the logic to the 11.5.x to 12.1 transition (2002–2008), with the header revision noted as 12.1 and a last change date of 21-May-2008 (12.1 Auto Sync), so the object is present and functionally stable in both 12.1.1 and 12.2.2.

The package is classified as "OTHER" in ETRM, which reflects that it is a callback/utility package rather than a formal Open Interface or public API. It is referenced by one other package, consistent with its role as a lower-level synchronization engine invoked by a controlling sync driver.

Key Procedures and Functions

The 23 documented procedures and functions group into four functional areas:

Tables Accessed

The package operates against APPS synonyms for the Mobile Server synchronization schema:

Usage Notes

ASG_CONS_QPKG is not intended for direct invocation by end users or custom code. It is called as a callback by the Oracle Lite consolidated synchronization mechanism, which registers these procedures so the server executes them at defined points in the sync cycle (download init, download complete, upload complete). Administrators may observe its activity indirectly through concurrent programs and mobile administration forms that manage user synchronization and conflict resolution. Customizations should avoid modifying this package; extension points lie in the published-item and conflict metadata rather than in the callback body. Because the header revision remains at 12.1, behavior is identical in 12.1.1 and 12.2.2, and any diagnostic review should begin with the ASG_USER sync-status and sync-error columns updated by VALIDATE_LOGIN and UPLOAD_COMPLETE.