Search Results asg_party_site_acc




Overview
Explore in AI Chat

Overview

The ASG_PARTY_SITE_ACC table is a core data object within the Oracle E-Business Suite (EBS) 12.1.1 and 12.2.2, specifically for the CRM Gateway for Mobile Devices (ASG) product module. Its primary function is to manage and control access permissions for party sites from the mobile gateway server. The table acts as an authorization registry, storing a binary indicator for each combination of a gateway server and a party site to denote whether the server is permitted to access data related to that specific customer or supplier location. This mechanism is essential for enforcing data security and access rules in a distributed mobile deployment, ensuring that synchronized data is only accessible to authorized gateway instances.

Key Information Stored

The table's structure is defined by a composite primary key, which inherently defines the critical data points it stores. The two key columns are SERVER_ID and PARTY_SITE_ID. The SERVER_ID column stores a unique identifier that references a specific mobile gateway server instance configured within the ASG_SYNCH_SERVER table. The PARTY_SITE_ID column stores the identifier for a party site, which is a physical location of a customer, supplier, or other trading partner, as defined in the Trading Community Architecture (TCA) schema (HZ_PARTY_SITES). While the provided metadata does not list additional attribute columns, the existence of the table itself implies it stores an implicit or explicit "access granted" flag, likely managed through the presence or absence of a record for a given SERVER_ID and PARTY_SITE_ID pair.

Common Use Cases and Queries

The primary use case is to validate access during data synchronization processes for mobile field service or sales personnel. Before the gateway server transmits data for a particular party site to a mobile device, it would query this table to confirm authorization. A common query pattern would be a lookup to determine if a server has access to a specific site, or to list all sites accessible to a server for filtering synchronization sets.

  • Access Validation: SELECT COUNT(*) FROM asg_party_site_acc WHERE server_id = :p_server_id AND party_site_id = :p_party_site_id;
  • List Accessible Sites for a Server: SELECT party_site_id FROM asg_party_site_acc WHERE server_id = :p_server_id;

Administrative reporting would focus on auditing access configurations, such as generating a matrix of servers and the party sites they are permitted to access.

Related Objects

The table maintains defined foreign key relationships with other EBS objects, as documented in the metadata.

  • ASG_SYNCH_SERVER: This is the primary related table. The SERVER_ID column in ASG_PARTY_SITE_ACC is a foreign key referencing the ASG_SYNCH_SERVER table. This relationship ensures that every access record is associated with a valid, configured gateway server instance. A typical join would be: SELECT ser.server_name, acc.party_site_id FROM asg_synch_server ser, asg_party_site_acc acc WHERE ser.server_id = acc.server_id;
  • HZ_PARTY_SITES (Inferred): While not explicitly listed as a foreign key in the provided snippet, the PARTY_SITE_ID column almost certainly references the standard TCA table HZ_PARTY_SITES. This links the access control record to the actual party site details, such as address and party information.