Search Results oe_header_acks




Overview
Explore in AI Chat

Overview

The HZ_CUST_ACCT_SITES_ALL table is a core data repository within Oracle E-Business Suite (EBS) 12.1.1 and 12.2.2, specifically for the Receivables (AR) module. As indicated by its name and the "_ALL" suffix, it is a multi-organization (Multi-Org) enabled table that stores all customer account sites across every operating unit. Its primary role is to serve as the critical junction between a customer account (HZ_CUST_ACCOUNTS) and a physical or logical address location (HZ_PARTY_SITES). This table establishes the foundational link that enables a single customer account to have multiple distinct addresses for billing, shipping, or other business purposes, forming the basis for all site-level transactional and reporting activities in Order Management, Receivables, and related modules.

Key Information Stored

The table's structure centers on linking identifiers and storing site-specific attributes. The primary key is CUST_ACCT_SITE_ID, which uniquely identifies each customer account site record. Two essential foreign key columns form its core relationships: CUST_ACCOUNT_ID, which links to the customer account in HZ_CUST_ACCOUNTS, and PARTY_SITE_ID, which links to the physical address definition in HZ_PARTY_SITES. Another significant column is TERRITORY_ID, which links to RA_TERRITORIES for assigning a sales territory to the specific site. The table also typically includes standard Oracle EBS audit columns (CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN) and the ORG_ID column that enables Multi-Org partitioning of the data by operating unit.

Common Use Cases and Queries

This table is central to operations involving customer addresses. Common use cases include generating reports listing all addresses for a specific customer account, validating address usage in transactional interfaces, and supporting data migration scripts for customer site information. A fundamental query retrieves all sites for a customer account, often joining to related tables for descriptive information:

  • SELECT hcas.cust_acct_site_id, hca.account_number, hp.party_name, hps.address1, hps.city FROM hz_cust_acct_sites_all hcas JOIN hz_cust_accounts hca ON hcas.cust_account_id = hca.cust_account_id JOIN hz_party_sites hps ON hcas.party_site_id = hps.party_site_id JOIN hz_parties hp ON hps.party_id = hp.party_id WHERE hca.account_number = '&CUSTOMER_NUMBER' AND hcas.org_id = &ORG_ID;

Another critical pattern involves checking for the existence of site uses (via HZ_CUST_SITE_USES_ALL) linked to a given account site, which determines if the address is actively used for a purpose like 'BILL_TO' or 'SHIP_TO'.

Related Objects

As evidenced by the extensive foreign key metadata, HZ_CUST_ACCT_SITES_ALL is a highly referenced master table. Its primary relationships are as a child to HZ_CUST_ACCOUNTS and HZ_PARTY_SITES. It is a parent table to HZ_CUST_SITE_USES_ALL, which defines the functional purposes for each site. Furthermore, it is referenced by numerous transactional and setup tables across EBS modules. Key references include HZ_CUST_ACCOUNT_ROLES, HZ_CUST_CONTACT_POINTS, AR_CORRESPONDENCES_ALL, AR_STATEMENT_HEADERS, and several tables in the Service (CS) and Loans (LNS) modules, such as CS_CUSTOMER_PRODUCTS_ALL and LNS_LOAN_HEADERS_ALL. This wide integration underscores its role as a central hub for customer address data within the application's architecture.