Search Results hz_cust_site_uses_all




Overview
Explore in AI Chat

Overview

The HZ_CUST_SITE_USES_ALL table is a core data object within the Oracle E-Business Suite (EBS) Receivables (AR) module, specifically in the Trading Community Architecture (TCA) schema. It serves as the master repository for storing the business purposes assigned to customer account sites. In practical terms, this table defines how a physical customer location (stored in HZ_CUST_ACCT_SITES_ALL) is utilized, such as for billing, shipping, marketing, or as a paying site. Its role is critical for enabling complex customer relationship management, ensuring transactions like invoices, receipts, and shipments are correctly associated with the appropriate functional site use of a customer. The '_ALL' suffix indicates it is a multi-organization table, storing data partitioned by the ORG_ID column for installations operating in a Multi-Org environment.

Key Information Stored

The table's primary key is the SITE_USE_ID, a unique identifier for each site use record. Essential foreign keys include CUST_ACCT_SITE_ID, which links the site use to its parent customer account site in HZ_CUST_ACCT_SITES_ALL. Key columns defining the business purpose are SITE_USE_CODE (e.g., 'BILL_TO', 'SHIP_TO', 'MARKETING') and the STATUS flag (e.g., 'A' for Active, 'I' for Inactive). The table also stores location-specific operational parameters, such as TERRITORY_ID for sales territory assignment, LOCATION_ID for geographic details, and CONTACT_ID to link a primary contact from HZ_CUST_ACCOUNT_ROLES. The ORG_ID column is vital for data security in Multi-Org, and standard WHO columns (CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN) track audit information.

Common Use Cases and Queries

A primary use case is retrieving all active bill-to sites for a specific customer account to generate invoices. Developers and functional consultants frequently query this table to validate site setup, troubleshoot transaction posting errors, or generate operational reports. Common SQL patterns include joining to the customer account and party tables to get a complete customer site profile. For example, to find all ship-to sites for a customer number '1000':

  • SELECT hp.party_name, hca.account_number, hcsua.site_use_code, hcasa.address1
  • FROM hz_cust_site_uses_all hcsua,
  • hz_cust_acct_sites_all hcasa,
  • hz_cust_accounts hca,
  • hz_parties hp
  • WHERE hcsua.cust_acct_site_id = hcasa.cust_acct_site_id
  • AND hcasa.cust_account_id = hca.cust_account_id
  • AND hca.party_id = hp.party_id
  • AND hca.account_number = '1000'
  • AND hcsua.site_use_code = 'SHIP_TO'
  • AND hcsua.status = 'A';

Another critical scenario involves identifying the paying site use linked to cash receipts during the application of payments.

Related Objects

HZ_CUST_SITE_USES_ALL is a central hub with extensive relationships across AR and other modules. Its primary parent is HZ_CUST_ACCT_SITES_ALL, joined via CUST_ACCT_SITE_ID. It is referenced as a foreign key in numerous transaction and setup tables, demonstrating its operational importance. Key documented relationships from the provided metadata include: