Search Results hz_organization_profiles




Overview
Explore in AI Chat

Overview

The HZ_ORGANIZATION_PROFILES table is a core data object within the Oracle Trading Community Architecture (TCA) model, specifically under the AR (Receivables) product schema. It serves as the central repository for detailed, profile-level information pertaining to business organizations that are defined as parties within the E-Business Suite. This table is integral to the unified customer and supplier model, enabling a single, consistent view of an organization's attributes across all Oracle Applications modules, including Order Management, Receivables, and Payables. Its primary role is to store operational and descriptive data about an organization beyond its basic party identification, linking this profile to a master party record via the PARTY_ID foreign key.

Key Information Stored

The table stores a comprehensive set of attributes that characterize an organization's business profile. The primary key, ORGANIZATION_PROFILE_ID, uniquely identifies each profile record. A critical foreign key, PARTY_ID, links the profile to its corresponding master record in the HZ_PARTIES table, ensuring data integrity within the TCA hierarchy. Other significant columns typically include business-centric information such as the organization's DUNS_NUMBER, SIC_CODE, MISSION_STATEMENT, and YEAR_ESTABLISHED. The HOME_COUNTRY column, which references the FND_TERRITORIES table, defines the organization's country of domicile. Additional columns often capture tax identifiers (e.g., FEDERAL_TAX_ID), incorporation details, and various classification codes essential for compliance, reporting, and business process segmentation.

Common Use Cases and Queries

This table is fundamental for queries requiring detailed organizational data for reporting, data validation, and integration. A common use case is generating a master list of customer organizations with their key identifiers and attributes for a data audit or external system feed. For instance, to retrieve the profile ID, party number, and business name for organizations established after a certain date, one might use a query joining HZ_PARTIES. Another frequent scenario involves validating or updating organization details via its primary key, such as locating a specific profile for maintenance. Sample SQL to find a profile by its unique identifier would be:

  • SELECT hp.party_number, hop.organization_name, hop.duns_number, hop.home_country FROM hz_organization_profiles hop, hz_parties hp WHERE hop.party_id = hp.party_id AND hop.organization_profile_id = :p_org_profile_id;

Reporting on organization demographics by country or industry classification also relies heavily on this table.

Related Objects

The HZ_ORGANIZATION_PROFILES table sits at the center of a key relational structure within TCA. Its primary relationship is with the HZ_PARTIES table, which holds the fundamental party record. It also maintains referential integrity with the FND_TERRITORIES table for the HOME_COUNTRY value. Furthermore, the table has child extension tables, namely HZ_ORG_PROFILES_EXT_B and HZ_ORG_PROFILES_EXT_TL, which hold additional flexfield and translated data, respectively, linked via the ORGANIZATION_PROFILE_ID. This table is also heavily referenced by various TCA public APIs (e.g., in the HZ_PARTY_V2PUB package) for creating and updating organization profiles programmatically, making it essential for any custom integration or data migration involving organizational entities.