Search Results asg_device_user_pub

Overview

ASG_DEVICE_USER_PUB is a public PL/SQL package owned by the APPS schema in Oracle E-Business Suite, delivered as part of the CRM Foundation and Mobile Field Service infrastructure. Its status is VALID in both 12.1.1 and 12.2.2, and it is classified as a PUBLIC (PUB) API, indicating it is intended for supported external invocation by customer extensions and integration code rather than restricted internal use. The package manages the association between application users and registered mobile devices, providing the business-level interface through which EBS records which device belongs to which user, when that device last synchronized, and how user identity maps to a device-user record identifier. This functionality underpins mobile and field service scenarios in which technicians operate disconnected clients that periodically synchronize with the E-Business Suite database. The package depends only on the SYS schema and the STANDARD package according to the ETRM dependency listing, confirming that its logic is self-contained and that it delegates to the underlying ASG_DEVICE_USER entity tables through APPS synonyms rather than through other published APIs.

Key Procedures and Functions

The documented API surface consists of eleven procedures and functions, reflecting a conventional create/read/update/delete pattern supplemented by synchronization and lookup helpers:

• CREATE_DEVICE_USER — Establishes a new association between an application user and a device.
• UPDATE_DEVICE_USER — Modifies attributes of an existing device-user association.
• DELETE_DEVICE_USER — Removes a device-user association record.
• DELETE_MOBILE_USER — Removes the mobile-user mapping, typically invoked when a user is decommissioned from mobile access.
• GET_DEVICE_USER — Retrieves the device-user information for a given user or device context.
• GET_LAST_SYNC_DATE — Returns the timestamp of the most recent successful synchronization for a device-user pairing.
• SET_LAST_SYNC_DATE — Updates the stored synchronization timestamp, usually following a completed mobile sync.
• GET_DEVICE_USER_ID — Returns the surrogate identifier of the device-user association record.
• GET_USER_ID — Resolves the application user identifier associated with a device-user record.
• GET_USER_NAME — Returns the user name for a given identifier, providing a display-ready value.
• GET_LANGUAGE — Returns the language setting associated with the user or device-user record, supporting multilingual mobile clients.

Parameter lists are not reproduced here because the ETRM metadata does not document them; callers should consult the package specification in the APPS schema for exact signatures.

Tables Accessed

The ETRM extract does not enumerate the underlying tables directly, noting only that references pass through APPS synonyms. Based on the package's function, it reads and writes the ASG device-user entity table that stores the user-to-device mapping, the last synchronization date, and the associated language and user identifiers. The GET_* and SET_* routines perform the read and write operations against this entity table, while the delete routines remove rows from it. Retrieval routines such as GET_USER_NAME may additionally resolve user identity from the FND_USER table. Because all access occurs through APPS synonyms, the package remains insulated from direct schema qualifications and follows standard EBS directory and privilege conventions.

Usage Notes

ASG_DEVICE_USER_PUB is typically invoked from mobile synchronization infrastructure and from EBS forms that administer device registrations, rather than from concurrent programs that process large data volumes. Customers building custom mobile clients or integrations with the E-Business Suite may call the package from custom PL/SQL to register a device, update synchronization state, or resolve a user name and language for display. The package is documented as being referenced by no other published package, confirming that it sits at the edge of the dependency graph as an entry point rather than an internal utility. As a PUB-classified API, its procedures and functions are supported for direct invocation, but the recommended practice remains to validate all inputs and handle exceptions raised by the underlying entity operations. Because the GET_LAST_SYNC_DATE and SET_LAST_SYNC_DATE pair governs incremental synchronization behavior, incorrect values supplied to the setter can cause clients to resynchronize unnecessary data or to miss updates entirely.