Results for “asg_party_acc”

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

Overview

The ASG_PARTY_ACC table resides in the ASG schema and belongs to the ASG - CRM Gateway for Mobile Devices product within Oracle E-Business Suite 12.1.1 and 12.2.2. It stores information that indicates whether the gateway server can access a given party, effectively acting as an access-control mapping between mobile synchronization servers and customer or contact records. Each row represents a permission grant linking one party to one server, allowing the CRM gateway to filter which party records are exposed to a specific mobile device or synchronization endpoint.

From a Data Vault modeling perspective, the mined FK structure suggests this object is satellite-leaning. It carries descriptive and control attributes surrounding a composite business key rather than acting as a pure hub of unique business entities or a link resolving many-to-many relationships between independent hubs. Its composite primary key and auditing columns reinforce this classification as a supporting satellite attached to the party and server domains.

Key Information Stored

The table is defined with eight documented columns and is uniquely identified by the primary key constraint ASG_PARTY_ACC_PK, which spans SERVER_ID and PARTY_ID. A second unique index, ASG_PARTY_ACC_U1, enforces uniqueness on the reversed column order of PARTY_ID and SERVER_ID, confirming the composite pair as the true business key.

• PARTY_ID — Identifier of the party (customer, contact, or organization) whose accessibility is being controlled.
• SERVER_ID — Foreign key to ASG_SYNCH_SERVER, identifying the gateway or synchronization server granted access.
• SECURITY_GROUP_ID — Foreign key to FND_SECURITY_GROUPS, enforcing Oracle EBS multi-org and data-security partitioning for the record.
• COUNTER — A numeric control column, typically used for synchronization or concurrency tracking by the gateway.
• CREATION_DATE — Timestamp when the access record was first created.
• CREATED_BY — User identifier responsible for inserting the row.
• LAST_UPDATE_DATE — Timestamp of the most recent modification, used by concurrent programs for incremental processing.
• LAST_UPDATED_BY — User identifier responsible for the latest change.

The surrogate primary key is represented by the constraint ASG_PARTY_ACC_PK over (SERVER_ID, PARTY_ID), while the business-key candidate is the unique index ASG_PARTY_ACC_U1 over (PARTY_ID, SERVER_ID). The two are functionally equivalent in uniqueness but differ in index column ordering, which affects query performance depending on predicate selectivity.

Common Use Cases and Queries

Typical scenarios include determining which parties a specific synchronization server may expose, auditing access grants for a party, and driving incremental extracts for mobile clients.

• List all parties accessible to a given server:

SELECT party_id, counter
FROM   asg.asg_party_acc
WHERE  server_id = :p_server_id;

• Find all servers authorized for a specific party:

SELECT server_id, last_update_date
FROM   asg.asg_party_acc
WHERE  party_id = :p_party_id;

• Detect recently granted access for change-based synchronization:

SELECT party_id, server_id
FROM   asg.asg_party_acc
WHERE  last_update_date > :p_since;

Reporting use cases include access-audit reports, security-group reconciliation, and validation that every gateway server has at least one accessible party before deployment.

Related Objects

• ASG_SYNCH_SERVER — Referenced via ASG_PARTY_ACC.SERVER_ID; defines the gateway servers that consume these access grants.
• FND_SECURITY_GROUPS — Referenced via ASG_PARTY_ACC.SECURITY_GROUP_ID; supplies the security partitioning context for each row.
• HZ_PARTIES — Implicit parent of PARTY_ID, supplying party names and classifications for joins.
• ASG_PARTY_ACC_PK / ASG_PARTY_ACC_U1 — Constraints enforcing primary and business-key uniqueness.
• FND_USER — Joined via CREATED_BY and LAST_UPDATED_BY for audit reporting.
• HZ_CUST_ACCOUNTS — Related customer context, joined through PARTY_ID when reporting on customer accessibility.