Results for “asg_task_acc”

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

Overview

ASG_TASK_ACC is a table owned by the ASG schema within the Oracle E-Business Suite CRM Gateway for Mobile Devices product family. Its documented purpose is to store information indicating whether the gateway server can access a given task. In effect, the table functions as an access-control bridge: it records the authorization relationship between a synchronization server and the tasks that server is permitted to serve to mobile clients. This makes it a small but security-relevant object, since it governs which device-facing tasks are reachable through a particular gateway server instance.

The table resides in the ASG product, which underpins mobile and disconnected CRM synchronization in EBS 12.1.1 and 12.2.2. It carries the standard EBS audit trail columns (CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, LAST_UPDATED_BY) and a SECURITY_GROUP_ID column for multi-org/security-group filtering. Based on the foreign-key topology documented in the metadata, the heuristic Data Vault classification is satellite-leaning, meaning the table is best modeled as descriptive access metadata attached to the parent server and task entities rather than as an independent hub or a pure link.

Key Information Stored

The documented schema contains eight columns. The most significant are:

• SERVER_ID — Identifies the gateway/synchronization server for which access is being granted. This is the FK to ASG_SYNCH_SERVER.
• TASK_ID — Identifies the task to which the server is granted access.
• SECURITY_GROUP_ID — FK to FND_SECURITY_GROUPS, scoping the row to a security group for data segregation.
• COUNTER — A numeric counter column, typically used for sequencing or incremental processing within the synchronization flow.
• CREATED_BY / CREATION_DATE — Audit columns recording who inserted the access row and when.
• LAST_UPDATED_BY / LAST_UPDATE_DATE — Audit columns recording the last modification of the row.

The primary key is ASG_TASK_ACC_PK on (SERVER_ID, TASK_ID), which enforces one access record per server-task combination. A separate unique index, ASG_TASK_ACC_U1 on (TASK_ID, SERVER_ID), provides the reverse-ordered business-key candidate. The composite nature of both keys means the table has no single surrogate key column; the server/task pair serves as the effective identifier.

Common Use Cases and Queries

Typical uses involve verifying or reporting server-to-task authorization, troubleshooting mobile synchronization failures caused by missing access grants, and auditing the spread of tasks across servers.

• List all tasks accessible to a given server:

  SELECT task_id FROM asg.asg_task_acc WHERE server_id = :server_id;

• Find servers authorized for a specific task:

  SELECT server_id FROM asg.asg_task_acc WHERE task_id = :task_id;

• Audit recently modified access grants:

  SELECT server_id, task_id, last_updated_by, last_update_date
  FROM asg.asg_task_acc
  WHERE last_update_date > SYSDATE - 30;

Because the SECURITY_GROUP_ID participates in multi-org security, reporting queries should include the standard security-group predicate when run outside a privileged context.

Related Objects

• ASG_SYNCH_SERVER — parent of SERVER_ID; join on asg_task_acc.server_id = asg_synch_server.server_id.
• FND_SECURITY_GROUPS — referenced by SECURITY_GROUP_ID for security-group scoping.
• ASG tasks table (task register) — the TASK_ID column points to the corresponding task definition used by the mobile gateway.
• Mobile gateway synchronization APIs — the package logic that reads ASG_TASK_ACC to decide whether a server may serve a task.
• Standard EBS audit/concurrent-request views — used to trace insert/update activity on the audit columns.