Search Results jai_ap_etds_t




Overview

The HZ_PARTY_SITES table is a core component of the Trading Community Architecture (TCA) within Oracle E-Business Suite 12.1.1 and 12.2.2. Under the AR (Receivables) schema, its primary function is to establish and manage the relationship between a party (an organization or person) and its physical locations. It serves as a critical junction table, linking the master party definition in HZ_PARTIES to the address details stored in HZ_LOCATIONS. This structure enables a single party to have multiple addresses, each with specific site uses (e.g., Bill To, Ship To, Legal Address), which are fundamental for transaction processing across all EBS modules.

Key Information Stored

The table's structure centers on its foreign key relationships and attributes that define the party-site association. The primary key is PARTY_SITE_ID, a unique identifier for each party-site link. Two essential foreign keys are PARTY_ID, referencing HZ_PARTIES, and LOCATION_ID, referencing HZ_LOCATIONS. Other significant columns include STATUS, which indicates if the site is active ('A') or inactive ('I'), and IDENTIFYING_ADDRESS_FLAG, which denotes the primary address for a party. The table also contains standard WHO columns (CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN) for auditing and the OBJECT_VERSION_NUMBER for optimistic locking.

Common Use Cases and Queries

This table is central to operations requiring address resolution for a party. Common use cases include generating invoices, shipping orders, and defining sales territories. A fundamental query retrieves all active sites for a specific party, often joining to HZ_LOCATIONS for full address lines:

  • SELECT ps.party_site_id, ps.status, loc.address1, loc.city FROM hz_party_sites ps, hz_locations loc WHERE ps.party_id = :p_party_id AND ps.location_id = loc.location_id AND ps.status = 'A';

Another critical pattern is identifying the primary (identifying) address for a customer organization, which is essential for legal and communication purposes. Developers also frequently query this table to validate a PARTY_SITE_ID referenced in transactional tables like ASO_QUOTE_HEADERS_ALL before processing.

Related Objects

HZ_PARTY_SITES is a hub with extensive dependencies. Its two principal parent tables are HZ_PARTIES and HZ_LOCATIONS. As indicated by the metadata, it is referenced as a foreign key by numerous transactional tables across the application suite, including AP_INVOICE_PAYMENTS_ALL (for invoicing party site), ASO_QUOTE_HEADERS_ALL (for sold-to and invoice-to sites), ASO_SHIPMENTS (for ship-to site), and many tables in the AS (Sales) module for lead and opportunity management. This widespread usage underscores its role as the definitive source for party address linkages in the EBS data model.

  • Table: HZ_PARTY_SITES 12.2.2

    owner:AR,  object_type:TABLE,  fnd_design_data:AR.HZ_PARTY_SITES,  object_name:HZ_PARTY_SITES,  status:VALID,  product: AR - Receivablesdescription: Links party to physical locations ,  implementation_dba_data: AR.HZ_PARTY_SITES

  • Table: HZ_PARTY_SITES 12.1.1

    owner:AR,  object_type:TABLE,  fnd_design_data:AR.HZ_PARTY_SITES,  object_name:HZ_PARTY_SITES,  status:VALID,  product: AR - Receivablesdescription: Links party to physical locations ,  implementation_dba_data: AR.HZ_PARTY_SITES

  • Table: HZ_PARTIES 12.1.1

    owner:AR,  object_type:TABLE,  fnd_design_data:AR.HZ_PARTIES,  object_name:HZ_PARTIES,  status:VALID,  product: AR - Receivablesdescription: Information about parties such as organizations, people, and groups ,  implementation_dba_data: AR.HZ_PARTIES

  • Table: HZ_PARTIES 12.2.2

    owner:AR,  object_type:TABLE,  fnd_design_data:AR.HZ_PARTIES,  object_name:HZ_PARTIES,  status:VALID,  product: AR - Receivablesdescription: Information about parties such as organizations, people, and groups ,  implementation_dba_data: AR.HZ_PARTIES