Results for “hz_per_profiles_ext_b_u1”

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

Overview

HZ_PER_PROFILES_EXT_B is an Oracle E-Business Suite table owned by the AR (Receivables) schema that stores extensible attribute values for person profiles. Within the Oracle Trading Community Architecture (TCA) data model, person profiles capture demographic and classification information about individuals, and this table provides the flexible, descriptor-driven extension mechanism that allows customers to capture organization-specific attributes without modifying the base person profile schema. The table is fully accessible through the standard TCA person profile query surfaces and the Oracle Data Model interfaces used by Receivables and Customer Relationship Management modules.

Under a heuristic Data Vault classification, the FK relationship to HZ_PERSON_PROFILES (via PERSON_PROFILE_ID) and the presence of a surrogate primary key with wide, volatile descriptive attribute columns suggest a satellite-leaning structure. Modeling tools may therefore treat this table as a satellite attached to a person profile hub, though this is a design suggestion drawn from the shape of the schema rather than a documented Oracle classification.

Key Information Stored

The table contains 59 documented columns. The surrogate primary key is EXTENSION_ID, enforced by the index HZ_PER_PROFILES_EXT_B_PK. A second unique index, HZ_PER_PROFILES_EXT_B_U1, also covers EXTENSION_ID, which means no separate business-key candidate is documented outside the surrogate identifier. Key columns include:

• EXTENSION_ID — Surrogate primary key of each extension record.
• PERSON_PROFILE_ID — Foreign key to HZ_PERSON_PROFILES; identifies the person profile to which the extension belongs.
• ATTR_GROUP_ID — Identifier for the attribute group context, aligning stored attributes with the descriptor group configured by the implementing organization.
• OLD_EXTENSION_ID — Retained historical identifier used during migration or consolidation of extension rows.
• C_EXT_ATTR1 through C_EXT_ATTR20 — Twenty character-typed extensible attribute columns.
• N_EXT_ATTR1 through N_EXT_ATTR20 — Twenty numeric-typed extensible attribute columns.
• D_EXT_ATTR1 through D_EXT_ATTR10 — Ten date-typed extensible attribute columns.
• CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN — Standard Oracle EBS audit columns recording row provenance and change history.

Common Use Cases and Queries

The most frequent use case is resolving customer-specific attributes attached to a person profile for reporting or downstream processing. A typical join retrieves the descriptive values alongside the profile row:

• SELECT p.person_profile_id, p.profile_name, e.c_ext_attr1, e.n_ext_attr1, e.d_ext_attr1 FROM hz_person_profiles p, hz_per_profiles_ext_b e WHERE p.person_profile_id = e.person_profile_id AND e.attr_group_id = :group_id;
• Attribute-group scoped extraction: filter by ATTR_GROUP_ID to retrieve only the extension block defined for a given descriptor group, avoiding cross-group column collisions.
• Audit reconciliation queries comparing LAST_UPDATE_DATE against CREATION_DATE to identify extension rows modified after initial load.
• Migration validation using OLD_EXTENSION_ID to map legacy extension identifiers to current EXTENSION_ID values.
• Reporting counts per person profile to detect profiles with multiple extension rows, which may indicate duplicate or orphaned attribute groups.

Related Objects

The following objects are significant to this table based on the documented relationship data:

• HZ_PERSON_PROFILES — Parent table; joined on HZ_PER_PROFILES_EXT_B.PERSON_PROFILE_ID = HZ_PERSON_PROFILES.PERSON_PROFILE_ID. This is the sole documented foreign key reference.
• HZ_PER_PROFILES_EXT_B_PK — Primary key index on EXTENSION_ID.
• HZ_PER_PROFILES_EXT_B_U1 — Unique index on EXTENSION_ID, providing the documented business-key candidate.
• HZ_PERSON_PROFILE — TCA public view commonly used to expose person profile data, including extension columns, to application query surfaces.
• HZ_PERSON_PROFILE_EXT_B — Sibling extension table for person objects, useful for distinguishing profile-level versus party-level extensible attributes.
• Related descriptor and attribute-group metadata tables in the TCA schema, which define the semantics of ATTR_GROUP_ID and the typed extension columns.

Because the table contains no additional documented outgoing foreign keys, dependency analysis beyond the person profile parent is best confirmed through the TCA descriptor setup and any customer-defined views layered on top of the extension columns.