Results for “asg_user_versions”

AI-generated from documented ETRM metadata — verify critical details on the linked pages.

Overview

The ASG_USER_VERSIONS view is a reporting and integration object owned by the APPS schema within the ASG – CRM Gateway for Mobile Devices product module. In Oracle EBS 12.1.1 and 12.2.2, this view consolidates synchronization and version metadata for mobile device users attached to one or more CRM Gateway synchronization servers. Rather than requiring developers and integrators to join the underlying device-user, synchronization server, server-publication, application, and publication tables manually, ASG_USER_VERSIONS presents a pre-joined, denormalized result set that resolves each device user to the release and compatible version information published by the server they synchronize against.

The view is especially relevant to searches for compatible_version, since that column is one of the primary values the view exposes. It allows administrators and integration developers to determine, for a given device user and mobile application, which publication version the client must be compatible with. This is fundamental to ensuring that deployed mobile clients remain interoperable with the server-side publication they consume.

Underlying Base Objects

ASG_USER_VERSIONS is defined over five documented base objects, all accessed through APPS synonyms:

• ASG_DEVICE_USERS — provides the device/user identity and server assignment (DEVICE_USER_ID, USER_ID, CLIENT_NAME, MOBILE_APPLICATION_ID, SERVER_ID, RESOURCE_ID).
• ASG_SYNCH_SERVER — supplies synchronization server attributes (SERVER_ID, SNAP_DATABASE).
• ASG_SERVER_PUBS — contributes publication version data (RELEASE_VERSION, COMPATIBLE_VERSION, PUBLICATION_ID).
• ASG_APPLICATIONS_B — base table holding mobile application definitions keyed by MOBILE_APPLICATION_ID and APPLICATION_CODE.
• ASG_PUBLICATIONS — holds publication definitions keyed by PUBLICATION_ID and NAME, which maps to the application code.

The joins enforce several relationships: the device user is matched to its synchronization server (D.SERVER_ID = S.SERVER_ID); the device user is matched to a mobile application (D.MOBILE_APPLICATION_ID = A.MOBILE_APPLICATION_ID); the server is matched to its publications (P.SERVER_ID = D.SERVER_ID); and the application code is matched to the publication name while the publication ID is matched to the server publication record. The result is a per-device-user, per-application, per-server version mapping.

Key Columns

• DEVICE_USER_ID — unique identifier of the device user record; the primary grain of the view.
• CLIENT_NAME — the registered client/device name associated with the user.
• MOBILE_APPLICATION_ID — identifier of the mobile application the user is provisioned against.
• USER_ID — the EBS application user identifier linked to the device user.
• RESOURCE_ID — resource identifier associated with the device user.
• SERVER_ID — the synchronization server the device user connects to.
• SNAP_DATABASE — the snapshot database associated with that synchronization server.
• RELEASE_VERSION — the published release version of the application/publication.
• COMPATIBLE_VERSION — the minimum compatible version the client must meet for interoperability with the published release.

Common Use Cases and Queries

A typical scenario is verifying that all deployed mobile clients meet the compatible version baseline for their assigned server and application. The following query lists each device user alongside the required compatible version:

SELECT device_user_id, client_name, server_id, release_version, compatible_version FROM apps.asg_user_versions ORDER BY server_id, client_name;

To identify clients below the compatible version for a specific server, join the view to client version data and filter on the compatible_version threshold. A common diagnostic query isolates all users for one sync server:

SELECT user_id, client_name, mobile_application_id, release_version, compatible_version FROM apps.asg_user_versions WHERE server_id = :server_id;

Because the view is read-only and exposed in the APPS schema, it is suitable for custom reports, concurrent programs, and integration extracts that must reconcile client and server publication versions across the CRM Gateway for Mobile Devices deployment.