Search Results hz_cust_acct_sites_all




The HZ_CUST_ACCT_SITES_ALL table is a critical component within Oracle E-Business Suite (EBS) versions 12.1.1 and 12.2.2, serving as a foundational entity in the Trading Community Architecture (TCA) module. This table stores customer account site information, linking customer accounts (HZ_CUST_ACCOUNTS) to their respective physical or operational locations (HZ_PARTY_SITES). It plays a pivotal role in managing customer relationships, billing, shipping, and other site-specific attributes across multiple business functions such as Order Management, Receivables, and Payables. ### **Key Attributes and Structure** The table's structure includes columns that define the relationship between a customer account and its associated sites: - CUST_ACCT_SITE_ID: Primary key uniquely identifying each record. - CUST_ACCOUNT_ID: Foreign key referencing HZ_CUST_ACCOUNTS, linking to the customer account. - PARTY_SITE_ID: Foreign key referencing HZ_PARTY_SITES, associating the account with a physical address. - STATUS: Indicates whether the site is active (A) or inactive (I). - PRIMARY_FLAG: Designates if the site is the primary location for the customer account. - BILL_TO_FLAG, SHIP_TO_FLAG, MARKET_FLAG: Flags identifying the site's purpose (billing, shipping, or marketing). - ORG_ID: Supports multi-org functionality, segregating data by operating unit. ### **Functional Role in Oracle EBS** 1. **Order Management & Shipping**: The SHIP_TO_FLAG determines valid delivery locations for sales orders. When creating an order, the system validates against active sites marked for shipping. 2. **Accounts Receivable**: Billing sites (BILL_TO_FLAG = 'Y') are used for invoicing and payment processing. The table ensures accurate tax calculations and dunning processes. 3. **Multi-Org & Security**: The ORG_ID column enforces data security by restricting site access to authorized operating units, critical for compliance in decentralized enterprises. 4. **Data Hierarchy**: The table sits within TCA’s hierarchical model: HZ_PARTIES → HZ_PARTY_SITES → HZ_CUST_ACCOUNTS → HZ_CUST_ACCT_SITES_ALL. ### **Integration Points** - AR_CUSTOMER_PROFILES: Stores credit and payment terms linked to account sites. - RA_ADDRESSES_ALL: Legacy table mapping for backward compatibility. - OE_ORDER_HEADERS_ALL: References CUST_ACCT_SITE_ID for shipping/billing details. ### **Customization & Extensions** The table supports user-defined columns (ATTRIBUTE1–20) for industry-specific extensions. Triggers or APIs (e.g., HZ_CUST_ACCOUNT_SITE_V2PUB) should be used for updates to maintain TCA data integrity. ### **Performance Considerations** Indexes on CUST_ACCOUNT_ID, PARTY_SITE_ID, and ORG_ID optimize queries. Large-scale implementations should audit inactive records (STATUS = 'I') to avoid performance degradation. ### **Conclusion** The HZ_CUST_ACCT_SITES_ALL table is indispensable for managing customer site relationships in Oracle EBS. Its design ensures flexibility, scalability, and integration across financial and logistical modules, making it a cornerstone of the TCA framework. Proper utilization of this table enhances data accuracy, operational efficiency, and compliance in multi-org environments.