Results for “asg_incident_acc”

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

Overview

ASG_INCIDENT_ACC is a table owned by the ASG schema within the Oracle E-Business Suite 12.1.1 and 12.2.2 environments. It belongs to the ASG - CRM Gateway for Mobile Devices product, a module that brokers service request and incident data between the EBS Service (TeleService) application and mobile or disconnected clients. The table stores information that indicates whether the gateway server can access a given service request. In practice it functions as an access-control and synchronization map: each row associates a service request (incident) with a specific gateway server and records whether that server is permitted to service, download, or update the incident.

From a dimensional modeling perspective, the physical structure is heuristic-classified as satellite-leaning. The composite primary key combines INCIDENT_ID and SERVER_ID, and all descriptive or state-bearing attributes (timestamps, audit columns, counters, security group) hang off that pair. This suggests modeling the table as a satellite attached to the hub/link formed by the incident and synchronization-server relationship rather than as an independent hub.

Key Information Stored

The table comprises eight documented columns. The most significant are:

• INCIDENT_ID — Identifier of the service request. Part of the composite primary key.
• SERVER_ID — Identifier of the gateway synchronization server. Also part of the composite primary key and the FK to ASG_SYNCH_SERVER.
• COUNTER — A numeric counter used to track synchronization or access sequencing between the incident and server.
• SECURITY_GROUP_ID — Security group discriminator, with an FK to FND_SECURITY_GROUPS, enforcing multi-org data segregation.
• LAST_UPDATE_DATE, LAST_UPDATED_BY — Standard EBS audit columns for the last modification.
• CREATION_DATE, CREATED_BY — Standard EBS audit columns for row creation.

The primary key, ASG_INCIDENT_ACC_PK, is defined on (INCIDENT_ID, SERVER_ID). The unique index ASG_INCIDENT_ACC_U1 mirrors these same columns, confirming the natural business key is the incident-plus-server pairing rather than a single surrogate column. There is no independent surrogate key; identity is composite.

Common Use Cases and Queries

Typical usage centers on synchronization eligibility and gateway access auditing. To determine which servers may access a given incident, query by INCIDENT_ID:

• SELECT server_id, counter FROM asg.asg_incident_acc WHERE incident_id = :p_incident_id;
• To enumerate all incidents accessible to a server: filter on SERVER_ID combined with SECURITY_GROUP_ID.
• To reconcile synchronization activity, join COUNTER and LAST_UPDATE_DATE to detect stale or unrefreshed access records.
• Reporting on access coverage by security group supports multi-org compliance checks.

Related Objects

• ASG_SYNCH_SERVER — Referenced via ASG_INCIDENT_ACC.SERVER_ID; defines the gateway servers receiving access grants.
• FND_SECURITY_GROUPS — Referenced via SECURITY_GROUP_ID; governs organization-level access.
• The base service request tables (CS_INCIDENTS_ALL and related) join on INCIDENT_ID to resolve request detail.
• ASG gateway synchronization tables and concurrent programs in the mobile CRM module consume this table during data exchange.