Results for “device_user_id”

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

Overview

The ASG_ERROR table, owned by the ASG schema, is a component of the CRM Gateway for Mobile Devices product within Oracle E-Business Suite (available in both 12.1.1 and 12.2.2). Its documented purpose is to store information of error logs. In practical terms, ASG_ERROR functions as an operational error repository for the mobile device synchronization framework. When a mobile client attempts to synchronize CRM data to the EBS instance through the ASG gateway, conditions such as failed record publication, authentication problems, connectivity interruptions, or validation failures on an application or responsibility context are written into this table as discrete error rows for later review and remediation.

From a dimensional modeling perspective, the mined Data Vault classification for this table is satellite-leaning. This is a heuristic suggestion rather than a documented design statement: because ASG_ERROR carries descriptive attributes and foreign references to parent entities rather than aggregating multiple business hubs itself, it is most naturally modeled as a satellite attached to the device-user hub (and, where enabled, the security-group construct). The table is registered as VALID in the EBS data dictionary and exposes 16 documented columns.

Key Information Stored

The primary key of ASG_ERROR is defined by ASG_ERROR_PK, which covers the MOBILE_ERROR_ID column. A unique index, ASG_ERROR_U1, also exists on MOBILE_ERROR_ID, making that column the documented surrogate key and effective business-key candidate for one-row-per-error lookups. The most significant columns are as follows:

• MOBILE_ERROR_ID — surrogate identifier for the error record; primary key and unique-index column.
• DEVICE_USER_ID — foreign key to ASG_DEVICE_USERS, identifying the mobile user whose synchronization generated the error.
• SECURITY_GROUP_ID — foreign key to FND_SECURITY_GROUPS, applying the standard EBS multi-tenant security group filter.
• TYPE and PRIORITY — classification and severity of the logged error.
• STATUS — lifecycle state of the error record (for example, open, resolved, or archived).
• APPLICATION_ID and RESPONSIBILITY_ID — the application and responsibility context in which the error occurred.
• SYNCHRONOUS_EVENT — indicates whether the error arose during a synchronous gateway call.
• ERROR_DAYS_DEFAULT and ERROR_TIME_DEFAULT — the effective date and time of the error.
• ERROR_DESCRIPTION — free-text description of the failure.
• CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, LAST_UPDATED_BY — the standard WHO audit columns present on EBS tables.

Common Use Cases and Queries

The principal operational use case is mobile synchronization troubleshooting: support personnel query ASG_ERROR by device user to identify recurring failures and confirm whether a client's error queue is draining. A representative pattern retrieves recent unresolved errors joined to the device user:

• SELECT e.MOBILE_ERROR_ID, e.TYPE, e.PRIORITY, e.STATUS, e.ERROR_DESCRIPTION, e.ERROR_TIME_DEFAULT, u.DEVICE_USER_ID FROM ASG.ASG_ERROR e, ASG.ASG_DEVICE_USERS u WHERE e.DEVICE_USER_ID = u.DEVICE_USER_ID AND e.STATUS = 'OPEN' ORDER BY e.ERROR_TIME_DEFAULT DESC;
• Trend analysis by type and priority for a given date range, using ERROR_DAYS_DEFAULT and ERROR_TIME_DEFAULT.
• Application/responsibility impact reporting using APPLICATION_ID and RESPONSIBILITY_ID to isolate errors originating in a specific module context.
• Security-scoped extracts filtered by SECURITY_GROUP_ID for multi-organization or hosted deployments.

Reporting is typically read-only; the gateway inserts and updates rows as synchronization proceeds, so queries should avoid locking and should be scheduled against non-peak synchronization windows.

Related Objects

The following objects are most significant to ASG_ERROR:

• ASG_DEVICE_USERS — joined via ASG_ERROR.DEVICE_USER_ID; the parent registration of each mobile user.
• FND_SECURITY_GROUPS — joined via ASG_ERROR.SECURITY_GROUP_ID; governs row-level security visibility.
• FND_APPLICATION and FND_RESPONSIBILITY — logical parents of APPLICATION_ID and RESPONSIBILITY_ID, used to resolve names in reports.
• ASG_ERROR_PK and ASG_ERROR_U1 — the primary key constraint and unique index enforcing identifier integrity.
• FND_USER — resolves CREATED_BY and LAST_UPDATED_BY to the operating user identity.

Because the documentation for this table is limited to the ETRM metadata above, join semantics beyond the documented foreign keys should be validated against the delivered ASG gateway code before being relied upon in production reporting.