Results for “asg_server_pubs”

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

Overview

ASG_SERVER_PUBS is a table in the ASG schema, owned by the CRM Gateway for Mobile Devices product module within Oracle E-Business Suite 12.1.1 and 12.2.2. It functions as an association or intersection table that links synchronization servers to the publications they serve. In the mobile CRM architecture, a synchronization server distributes one or more publications (data subsets) to disconnected or mobile clients, and ASG_SERVER_PUBS records which publications are assigned to which servers.

The ETRM metadata classifies this object heuristically as a link in a Data Vault modeling sense. This reflects its structural role: it resolves a many-to-many relationship between servers and publications and carries foreign keys to both parent entities plus a security group reference. The table's status is VALID and it contains 12 documented columns.

Key Information Stored

The table's surrogate primary key is SERVER_PUBS_ID, enforced by the SERVER_PUBS_ID_PK constraint. This column uniquely identifies each server-to-publication assignment row. The principal business-key candidates are the foreign key columns SERVER_ID and PUBLICATION_ID, which together define the relationship being modeled.

• SERVER_PUBS_ID — Surrogate primary key for the assignment record.
• SERVER_ID — Foreign key to ASG_SYNCH_SERVER; identifies the synchronization server.
• PUBLICATION_ID — Foreign key to ASG_PUBLICATIONS; identifies the publication assigned to the server.
• SECURITY_GROUP_ID — Foreign key to FND_SECURITY_GROUPS; enforces row-level security partitioning.
• STATUS — Indicates the active/inactive state of the server-publication association.
• RELEASE_VERSION and COMPATIBLE_VERSION — Track release and compatibility versioning for the assignment.
• APACHE_URL — Stores the Apache web URL associated with the server-publication configuration.
• LAST_UPDATE_DATE, LAST_UPDATED_BY, CREATION_DATE, CREATED_BY — Standard EBS audit columns recording who created and last modified the row and when.

The audit columns follow the conventional Oracle EBS WHO-column pattern and are important for change tracking and troubleshooting.

Common Use Cases and Queries

Typical use cases include determining which publications a given synchronization server distributes, identifying all servers serving a particular publication, and checking status or version compatibility for mobile synchronization setups.

• Listing publications per server:

  SELECT sp.server_id, sp.publication_id, sp.status
  FROM   asg.asg_server_pubs sp
  WHERE  sp.server_id = :server_id;

• Finding servers for a publication:

  SELECT sp.server_id, sp.status, sp.release_version
  FROM   asg.asg_server_pubs sp
  WHERE  sp.publication_id = :publication_id
  AND    sp.status = 'ACTIVE';

• Joining to parent entities for reporting:

  SELECT s.server_name, p.publication_name, sp.status
  FROM   asg.asg_server_pubs sp,
         asg.asg_synch_server s,
         asg.asg_publications p
  WHERE  sp.server_id = s.server_id
  AND    sp.publication_id = p.publication_id;

Reporting scenarios often validate that every active publication has at least one assigned server, and verify security group alignment across mobile gateway configuration.

Related Objects

The most significant related objects are the parent tables referenced by its foreign keys, along with security and versioning dependencies:

• ASG_PUBLICATIONS — Referenced via PUBLICATION_ID; defines publication definitions.
• ASG_SYNCH_SERVER — Referenced via SERVER_ID; defines synchronization servers.
• FND_SECURITY_GROUPS — Referenced via SECURITY_GROUP_ID; controls row-level security.
• ASG_SERVER_PUBS primary key SERVER_PUBS_ID_PK — anchors the link to both parents.

Because the metadata documents only these FK relationships, additional downstream dependencies are not enumerated here. Administrators should consult the ASG module data model for any publication-server configuration views or APIs built on this table.