Results for “hz_organization_profiles”

50+ results




AI-generated from documented ETRM metadata — verify critical details on the linked pages.

Overview

HZ_ORGANIZATION_PROFILES is the primary registry table in Oracle E-Business Suite (EBS) 12.1.1 and 12.2.2 that stores detailed descriptive, demographic, and financial information about organizations registered as parties in the Trading Community Architecture (TCA). It is owned by the AR schema and is documented in ETRM with status VALID. Where HZ_PARTIES holds the canonical identity of a party, HZ_ORGANIZATION_PROFILES holds the extended "profile" attributes specific to organizations — corporate identifiers, credit and risk scores, fiscal data, ownership classification, and contact metadata.

Under the ETRM relationship metadata, this table is heuristically classified as satellite-leaning. In Data Vault modeling terms, it functions as a satellite attached to the HZ_PARTIES hub: it carries a foreign key to HZ_PARTIES (PARTY_ID), a surrogate primary key (ORGANIZATION_PROFILE_ID), and a dense set of descriptive and type-specific attributes. This classification is a modeling suggestion, not a physical constraint — the table remains a standard EBS transactional/master data object.

The table contains 185 documented columns in the 12.2.2 physical schema, reflecting its dual role as both a core TCA profile store and a repository for third-party business intelligence data (DUNS, Paydex, failure and credit scoring).

Key Information Stored

Common Use Cases and Queries

The table is central to customer and supplier data quality reporting, credit risk assessment, and TCA data extraction. Typical patterns include joining the profile to HZ_PARTIES to resolve party identity, and to HZ_ORG_PROFILES_EXT_B and HZ_ORG_PROFILES_EXT_TL for extended and translated attributes.

A representative query retrieving organizational profiles for active parties:

  • Join HZ_ORGANIZATION_PROFILES.ORGANIZATION_PROFILE_ID to HZ_ORG_PROFILES_EXT_B.ORGANIZATION_PROFILE_ID to surface extension attributes.
  • Filter by STATUS and EFFECTIVE_START_DATE/EFFECTIVE_END_DATE for current records.
  • Aggregate by HOME_COUNTRY or SIC_CODE for geographic and industry segmentation.
  • Select CREDIT_SCORE and FAILURE_SCORE for credit-risk dashboards, combining with HZ_PARTIES for the legal party name.

Because 185 columns exist and many are reserved ATTRIBUTE1–ATTRIBUTE20 and GLOBAL_ATTRIBUTE1–GLOBAL_ATTRIBUTE20 flexfields, reporting scripts should always project explicit columns rather than SELECT *.

Related Objects

  • HZ_PARTIES — parent party table; joined on HZ_ORGANIZATION_PROFILES.PARTY_ID = HZ_PARTIES.PARTY_ID.
  • FND_TERRITORIES — territory lookup; joined on HZ_ORGANIZATION_PROFILES.HOME_COUNTRY = FND_TERRITORIES.TERRITORY_CODE.
  • HZ_ORG_PROFILES_EXT_B — extension table referencing ORGANIZATION_PROFILE_ID; stores additional descriptive attributes.
  • HZ_ORG_PROFILES_EXT_TL — translated extension table referencing ORGANIZATION_PROFILE_ID; stores language-specific attributes.
  • HZ_ORGANIZATION_PROFILES_PK / HZ_ORGANIZATION_PROFILES_U1 — the primary key constraint and unique index on ORGANIZATION_PROFILE_ID.
  • HZ_CUST_ACCOUNTS and related TCA customer tables — while not directly FK-linked in the supplied metadata, they resolve parties to customer accounts that depend on organization profile data for credit and billing context.

Together these objects form the TCA organization data model, with HZ_ORGANIZATION_PROFILES acting as the satellite holding organization-specific descriptive and scoring data for each party in HZ_PARTIES.