Search Results hz_parties




Overview
Explore in AI Chat

Overview

The HZ_PARTIES table is the fundamental data repository for all entities, or "parties," within the Oracle E-Business Suite Trading Community Architecture (TCA). It serves as the central master table for storing core information about organizations, people (individuals), and groups. As part of the AR (Receivables) product family, its primary role is to establish a single, non-redundant source of truth for any entity with whom the enterprise conducts business, supports, or tracks. This foundational design enables integrated operations across all EBS modules, from Order Management and Receivables to Human Resources and Service, by providing a unified party identifier (PARTY_ID).

Key Information Stored

The table's structure is designed to capture the essential attributes common to all party types. The primary key, PARTY_ID, is a unique system-generated identifier that links to numerous related tables holding detailed information. Key columns include PARTY_TYPE to distinguish between 'ORGANIZATION', 'PERSON', or 'GROUP'; PARTY_NAME for the primary name of the entity; and STATUS to indicate if the party is 'A'ctive or 'I'nactive. It also stores basic demographic and geographic data points, such as LANGUAGE_NAME and HOME_COUNTRY, which reference the FND_LANGUAGES and FND_TERRITORIES tables, respectively. Other critical columns include PARTY_NUMBER (a user-facing identifier), CREATION_DATE, and LAST_UPDATE_DATE for audit purposes.

Common Use Cases and Queries

This table is central to any process requiring party identification or data retrieval. Common technical and reporting use cases include identifying duplicate party records, generating master customer or supplier lists, and serving as the driving table for data quality audits. A fundamental query pattern involves joining HZ_PARTIES to related TCA tables, such as HZ_PARTY_SITES or HZ_CUST_ACCOUNTS, to build a complete profile. For example, to retrieve all active person-type parties created in a specific timeframe, a query would be: SELECT party_id, party_name FROM hz_parties WHERE party_type = 'PERSON' AND status = 'A' AND TRUNC(creation_date) BETWEEN :p_start_date AND :p_end_date;. It is also critical for data migration scripts where legacy party data must be validated and inserted into the TCA model.

Related Objects

HZ_PARTIES is the cornerstone of the TCA model and has extensive relationships. As indicated by the metadata, its primary key, PARTY_ID, is referenced by a vast number of foreign keys across virtually all EBS modules, including Advanced Pricing (QP), Complex Maintenance (AHL), and Marketing (AMS). Key dependent tables within TCA itself include HZ_ORGANIZATION_PROFILES and HZ_PERSON_PROFILES for type-specific details, HZ_PARTY_SITES for location data, and HZ_RELATIONSHIPS for defining associations between parties. For programmatic access and data integrity, developers should utilize the public TCA APIs (e.g., HZ_PARTY_V2PUB) rather than direct DML on this table.