Search Results hz_per_profiles_ext_b_pk

Overview

The HZ_PER_PROFILES_EXT_B table is a core extensibility data object within the Oracle E-Business Suite (EBS) 12.1.1 and 12.2.2 architecture. As documented in the ETRM, it resides in the AR (Receivables) schema and is part of the AR - Receivables product module. Its primary role is to store extensible, or user-defined, attributes for person entities within the Trading Community Architecture (TCA) framework. This table enables organizations to extend the standard person profile data model to capture unique business information without requiring custom modifications to core application tables. It functions as a child table to the base person profile entity, providing a structured repository for supplementary data.

Key Information Stored

The table's structure is designed to support the flexible storage of extended attributes. The most critical column is the EXTENSION_ID, which serves as the table's primary key (HZ_PER_PROFILES_EXT_B_PK) and uniquely identifies each record of extended data. The key relational column is PERSON_PROFILE_ID, which is a foreign key linking each extensible attribute record to its corresponding base person profile in the HZ_PERSON_PROFILES table. Beyond these documented structural columns, the table typically contains numerous attribute columns (often named ATTRIBUTE1 through ATTRIBUTE*N*) and corresponding category columns to organize the extended data. These columns hold the actual user-defined values for a person, such as custom demographic details, compliance flags, or industry-specific classifications.

Common Use Cases and Queries

This table is central to reporting and data integration scenarios involving custom person attributes. A common use case is generating a list of persons with their extended attribute values for a CRM or segmentation analysis. The standard query pattern involves joining this table to the base profile and party tables. For example, to retrieve a person's name and a custom attribute, a query would join HZ_PER_PROFILES_EXT_B to HZ_PERSON_PROFILES via PERSON_PROFILE_ID, and then to HZ_PARTIES to get the party name. Another critical use case is data migration, where custom person data from legacy systems is loaded into these extensible columns. Support and development teams frequently query this table to troubleshoot data issues or validate the population of custom attributes by personalization or API calls.

Related Objects

The table has a direct and documented foreign key relationship with the core TCA table for person profiles, as specified in the provided metadata.

• HZ_PERSON_PROFILES: This is the primary parent table. The foreign key constraint on HZ_PER_PROFILES_EXT_B.PERSON_PROFILE_ID references the primary key in HZ_PERSON_PROFILES. This relationship ensures that every extensible attribute record is associated with a valid base person profile.

In practice, this table is also closely related to the HZ_PARTIES table (for the person's name and core details) and is accessed via public TCA APIs, such as those in the HZ_PARTY_V2PUB package, which handle the creation and update of extended attribute data. Views like HZ_PER_PROFILES_EXT_V may exist to provide a simplified access layer to this data.