Search Results set_last_sync_date




Overview

ASG_DEVICE_USER_PUB is a public PL/SQL API package owned by the APPS schema in Oracle E-Business Suite 12.1.1 and 12.2.2. It belongs to the Applications Synchronization/Field Service technology stack (ASG product prefix) and provides the programmatic interface for managing the association between an EBS application user and a registered mobile or synchronization device. In practical terms, the package governs "device user" records: the mapping that allows a specific user to synchronize data through a handheld, laptop, or field device, and it exposes supporting lookups for the synchronizing user's identity, language, and synchronization timestamps. The header comment embedded in the source identifies the original purpose as "Procedure to create synch server," reflecting the package's origin in the mobile synchronization infrastructure. The API is classified as PUB, meaning it is intended for external invocation by other EBS modules or custom code rather than being restricted to internal package use. The documented revision, $Header: asgpusrb.pls 120.1 2005/08/12, indicates a relatively stable body with no major structural changes since the mid-2000s release cycle, and the package is referenced by zero other packages, confirming it is a top-level interface rather than a shared internal utility.

Key Procedures and Functions

The package exposes eleven documented program units, all following standard EBS API conventions with the common p_api_version, p_init_msg_list, p_commit, p_validation_level, and x_return_status/x_msg_count/x_msg_data parameters. The core data-maintenance procedures are:

The query and utility functions include:

  • GET_DEVICE_USER — retrieves the device user record for a given user or device.
  • GET_DEVICE_USER_ID — returns the unique identifier of the device user association.
  • GET_USER_ID — returns the EBS application user identifier tied to a device user record.
  • GET_USER_NAME — returns the application user name associated with the device user.
  • GET_LANGUAGE — returns the language assigned to the device user, used to drive locale-specific synchronization payloads and UI rendering on the device.
  • GET_LAST_SYNC_DATE — returns the timestamp of the most recent successful synchronization.
  • SET_LAST_SYNC_DATE — updates that timestamp after a synchronization completes.

Notably, the source excerpt shows the create, update, delete, and delete-mobile bodies implemented as stubs containing only NULL, which indicates these routines are placeholders or were later overridden; the retrieve-oriented getters carry the functional weight.

Tables Accessed

The ETRM metadata does not enumerate underlying tables for this package, and no APPS synonyms are listed. Given the functional scope, the package operates against the ASG device/user synchronization tables (the ASG_DEVICE_USERS family and related ASG setup tables) that store device registrations, user-to-device mappings, language assignments, and the last-synchronization timestamp column. Because the mutation procedures are stubbed, the getter functions are the primary readers of these tables.

Usage Notes

ASG_DEVICE_USER_PUB is typically invoked from mobile synchronization server processes, Oracle Forms-based device administration screens, and custom PL/SQL handlers that need to resolve a device user's identity, language, or last sync date before exchanging data. The GET_LANGUAGE function in particular is called when the synchronization layer must determine the correct NLS language for a user's device session, ensuring that downloaded data and messages are presented in the appropriate locale. As the package is not referenced by other packages, callers are application-level components rather than dependent APIs. Customizations should call these procedures through the standard EBS API error-handling pattern, inspecting x_return_status and the message stack, and should not assume that CREATE/UPDATE/DELETE routines persist data unless the shipped body has been populated or replaced.