Results for “asg_server_resources”

34 results




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

Overview

The ASG_SERVER_RESOURCES table resides in the ASG schema and belongs to the ASG - CRM Gateway for Mobile Devices product within Oracle E-Business Suite. Its documented purpose is to store all users (referred to as resources) that are assigned to a particular middle-tier server. In a mobile or disconnected CRM deployment, client devices synchronize against a middle-tier synchronization server, and this table defines precisely which field resources are authorized to use a given server. As such, it acts as the association between the pool of mobile users and the synchronization infrastructure that services them.

From a Data Vault modeling perspective, the heuristic classification derived from the foreign-key structure is satellite-leaning. This suggests the table behaves principally as an associative entity that captures attributes and relationships surrounding the core server and resource concepts rather than serving as an independent transactional hub. Modeling teams should treat this as a suggestion and validate it against their own warehouse design.

Key Information Stored

The table contains seven documented columns. The most significant are:

  • RESOURCE_ID — Identifies the resource, i.e., the mobile user or field representative associated with the middle-tier server.
  • SERVER_ID — Identifies the synchronization server (middle-tier) to which the resource is assigned; this column carries a foreign key to ASG_SYNCH_SERVER.
  • SECURITY_GROUP_ID — Associates the assignment with an Oracle EBS security group; it carries a foreign key to FND_SECURITY_GROUPS.
  • LAST_UPDATE_DATE — Standard EBS audit column recording the last modification timestamp.
  • LAST_UPDATED_BY — The application user who last modified the record.
  • CREATION_DATE — Timestamp when the record was first created.
  • CREATED_BY — The user who created the record.

The primary key is ASG_SERVER_RESOURCES_PK, defined over the composite of RESOURCE_ID and SERVER_ID. A unique index, ASG_SERVER_RESOURCES_U1, covers the same two columns and serves as the business-key candidate, enforcing that a resource can appear only once per server. The composite key design reinforces that the object models a many-to-many assignment rather than a single-column entity, which is why a Data Vault classification leans toward an associative or link-like structure with satellite attributes.

Common Use Cases and Queries

Administrators and DBAs use this table to audit and troubleshoot mobile synchronization assignments. Typical scenarios include verifying which resources are provisioned on a specific middle-tier server, identifying servers that service a given resource, and reconciling security group exposure across servers.

A representative query lists all resources for a server:

  • SELECT resource_id FROM asg_server_resources WHERE server_id = :server_id;

A join to the server definition provides readable server context:

  • SELECT r.resource_id, s.server_name FROM asg_server_resources r, asg_synch_server s WHERE r.server_id = s.server_id;

Reporting use cases include capacity planning (counting resources per server), security audits (grouping assignments by security_group_id), and synchronization diagnostics during mobile deployment rollouts. EBS audit columns such as CREATED_BY and LAST_UPDATE_DATE support change tracking and compliance reporting.

Related Objects

The most significant related objects, based on documented foreign-key relationships, include:

  • ASG_SYNCH_SERVER — Referenced by ASG_SERVER_RESOURCES.SERVER_ID; holds the middle-tier server definitions.
  • FND_SECURITY_GROUPS — Referenced by ASG_SERVER_RESOURCES.SECURITY_GROUP_ID; provides Oracle EBS security group definitions.
  • ASG_SERVER_RESOURCES_PK — The composite primary key constraint over RESOURCE_ID and SERVER_ID.
  • ASG_SERVER_RESOURCES_U1 — The unique index that enforces the business key.

Additional ASG mobile-gateway tables that reference resource or server identities typically complement this object, but the documented dependencies above are the authoritative join points for queries and impact analysis.