Results for “client_number”

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

Overview

ASG_DEVICE_USERS is a core table in the ASG product family — CRM Gateway for Mobile Devices — which is delivered as part of the Oracle E-Business Suite 12.1.1 and 12.2.2 technology stack. The table stores information about a resource, such as a service engineer or a salesman, that is associated with a mobile application. In practical terms, it functions as the master enrollment record that links a back-office EBS identity (an FND_USER) and a Field Service or Sales resource (a JTF_RS_RESOURCE_EXTNS row) to the mobile application and synchronization server that the device uses. Each row therefore represents one registered device user, capturing both the identity of the person and the technical characteristics of the handheld or laptop they synchronize from.

Because the table is narrow in business meaning and heavily dependent on the surrounding hubs (users, resources, applications, servers), the heuristic Data Vault classification mined from its foreign-key structure is satellite-leaning. This suggests that, in a dimensional or Data Vault model, ASG_DEVICE_USERS is best treated as a descriptive satellite attached to the USER, RESOURCE, and APPLICATION business keys, rather than as a hub or a link in its own right.

Key Information Stored

The table is owned by the ASG schema and contains 34 documented columns in the 12.2.2 physical schema. The most operationally significant columns are:

• DEVICE_USER_ID — the surrogate primary key, enforced by ASG_DEVICE_USERS_PK, uniquely identifying each device-user enrollment.
• USER_ID — foreign key to FND_USER, tying the device user to an EBS application user account.
• RESOURCE_ID — foreign key to JTF_RS_RESOURCE_EXTNS, identifying the underlying service engineer or salesperson resource.
• MOBILE_APPLICATION_ID — foreign key to ASG_APPLICATIONS_B, indicating which mobile application this user is entitled to run.
• SERVER_ID — foreign key to ASG_SYNCH_SERVER, identifying the synchronization server the device communicates with.
• CLIENT_NUMBER, CLIENT_NAME, and REMOTE_DEVICE_NAME — business-key candidates, each protected by a unique index (ASG_DEVICE_USERS_U3, U4, U5 respectively) and used to identify the physical device.
• DEVICE_TAG — a descriptive tag applied to the device record.
• ENABLED, UPGRADE, ONAIR_FLAG, DEVICE_LOCKED, and FLASH_MESSAGE_FLAG — status and control flags governing whether the device may connect, synchronize, or receive flash messages.
• LAST_SYNC_DATE, LAST_WIRELESS_CONTACT_DATE, RETRY_DATE, and LAST_SYNCH_MODE — synchronization telemetry used for monitoring device activity and scheduling retries.
• BYTES_SENT_WIRELESS and BYTES_RECEIVED_WIRELESS — volume metrics for wireless traffic per device.
• ACCESS_CODE and COOKIE — authentication and session artifacts used by the mobile client.
• ORG_ID and ORGANIZATION_ID — multi-org operating unit context.
• SECURITY_GROUP_ID — foreign key to FND_SECURITY_GROUPS for function security scoping.

Standard WHO columns (CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, LAST_UPDATED_BY) are also present. The composite unique index ASG_DEVICE_USERS_U2 (RESOURCE_ID, MOBILE_APPLICATION_ID) prevents a resource from being enrolled more than once for the same mobile application.

Common Use Cases and Queries

Typical reporting and diagnostic scenarios include identifying which devices have gone silent, auditing which resources are entitled to a given mobile application, and reconciling device users against active EBS users.

• List active device users joined to their EBS user and resource: SELECT du.DEVICE_USER_ID, fu.USER_NAME, jre.NAME, du.CLIENT_NAME FROM ASG.ASG_DEVICE_USERS du JOIN FND_USER fu ON fu.USER_ID = du.USER_ID JOIN JTF_RS_RESOURCE_EXTNS jre ON jre.RESOURCE_ID = du.RESOURCE_ID WHERE du.ENABLED = 'Y';
• Devices that have not synchronized recently: filter on LAST_SYNC_DATE < SYSDATE - N where ENABLED is 'Y'.
• Wireless volume trending by device using BYTES_SENT_WIRELESS and BYTES_RECEIVED_WIRELESS grouped by CLIENT_NUMBER.
• Reconciliation of orphaned device users against FND_USER and JTF_RS_RESOURCE_EXTNS to detect de-provisioned staff.
• Error and flash-message reporting by joining to ASG_ERROR and ASG_FLASH_RECIPIENTS on DEVICE_USER_ID.

Related Objects

The table participates in the following significant relationships:

• FND_USER — joined via ASG_DEVICE_USERS.USER_ID; identifies the EBS user account.
• JTF_RS_RESOURCE_EXTNS — joined via ASG_DEVICE_USERS.RESOURCE_ID; the underlying service engineer or salesperson.
• ASG_APPLICATIONS_B — joined via ASG_DEVICE_USERS.MOBILE_APPLICATION_ID; the mobile application definition.
• ASG_SYNCH_SERVER — joined via ASG_DEVICE_USERS.SERVER_ID; the synchronization server.
• FND_SECURITY_GROUPS — joined via ASG_DEVICE_USERS.SECURITY_GROUP_ID; function security scoping.
• ASG_ERROR — references ASG_DEVICE_USERS.DEVICE_USER_ID; captured synchronization errors per device user.
• ASG_FLASH_RECIPIENTS — references ASG_DEVICE_USERS.DEVICE_USER_ID; flash message delivery targets.

Together these objects form the surrounding constellation that makes ASG_DEVICE_USERS the enrollment and telemetry anchor for mobile device users in the ASG CRM Gateway.