Search Results hz_party_sites




Overview
Explore in AI Chat

Overview

AS_ACCESSES_ALL_ALL is a Sales Foundation (AS) table owned by the OSM schema that stores employee and partner access records for customers, sales leads, and opportunities. It functions as the central authorization and assignment registry for the Oracle Sales and Telesales modules, determining which salesforce resources, sales groups, and partners may view or work a given customer, address, lead, or opportunity. Each row ties an access holder (a salesforce resource, person, or partner contact) to a target entity (customer party, party site, or lead) together with role, relationship, and freeze or reassignment indicators.

The table carries 67 documented columns in ETRM 12.2.2 and a single-column surrogate primary key, AS_ACCESSES_ALL_PK, defined on ACCESS_ID. Two additional unique indexes, AS_ACCESSES_U1 (ACCESS_ID, ORG_ID) and AS_ACCESSES_U2 (SALESFORCE_ID, CUSTOMER_ID, SALES_GROUP_ID, ADDRESS_ID, LEAD_ID, SALES_LEAD_ID, ORG_ID, SALESFORCE_ROLE_CODE, DELETE_FLAG), act as business-key candidates. Under a heuristic Data Vault classification, the table leans toward a satellite: it is keyed by a surrogate ACCESS_ID and carries descriptive, versioned access attributes rather than serving purely as a hub or link, though its foreign keys to HZ_PARTIES and HZ_PARTY_SITES give it link-like characteristics as well.

Key Information Stored

The most significant columns include:

Common Use Cases and Queries

Typical scenarios include determining which sales representatives can see a customer, validating partner access to an address, and auditing reassignment or freeze history. Because the table references HZ_PARTY_SITES through ADDRESS_ID (and PARTNER_ADDRESS_ID), the user's search term "hz_party_sites" commonly appears in joins resolving access records to physical locations.

Example query returning all accesses for a given party site:

  • SELECT a.ACCESS_ID, a.SALESFORCE_ID, a.SALESFORCE_ROLE_CODE, a.ACCESS_TYPE FROM AS_ACCESSES_ALL_ALL a WHERE a.ADDRESS_ID = :party_site_id AND NVL(a.DELETE_FLAG,'N') = 'N';

A join pattern linking accesses to the underlying party and site:

  • SELECT hp.PARTY_NAME, hps.ADDRESS1, a.SALESFORCE_ROLE_CODE FROM AS_ACCESSES_ALL_ALL a JOIN HZ_PARTY_SITES hps ON a.ADDRESS_ID = hps.PARTY_SITE_ID AND a.ORG_ID = hps.ORG_ID JOIN HZ_PARTIES hp ON a.CUSTOMER_ID = hp.PARTY_ID AND a.ORG_ID = hp.ORG_ID WHERE NVL(a.DELETE_FLAG,'N') = 'N';

Reporting use cases include access coverage reports by sales group, partner access audits, reassignment tracking, and reconciliation of access records during territory realignment.

Related Objects

The following objects are most significant to AS_ACCESSES_ALL_ALL:

  • HZ_PARTIES – joined via CUSTOMER_ID and PARTNER_CUSTOMER_ID.
  • HZ_PARTY_SITES – joined via ADDRESS_ID and PARTNER_ADDRESS_ID.
  • JTF_RS_RESOURCE_EXTNS – joined via SALESFORCE_ID.
  • JTF_RS_GROUPS_B – joined via SALES_GROUP_ID.
  • AS_LEADS_ALL – joined via LEAD_ID.
  • AS_SALES_LEADS – joined via SALES_LEAD_ID.
  • AS_TERRITORY_ACCESSES – references ACCESS_ID.
  • PV_ACCESS_MIGRATION_LOG – references ACCESS_ID.
  • FND_SECURITY_GROUPS – joined via SECURITY_GROUP_ID.
  • RA_CUSTOMERS / RA_ADDRESSES_ALL – legacy joined via CUSTOMER_ID and ADDRESS_ID.