Search Results hz_party_sites_ext_b




Overview
Explore in AI Chat

Overview

HZ_PARTY_SITES_EXT_B is an Oracle E-Business Suite table owned by the AR (Receivables) schema that stores extensible attributes for party sites. In the EBS Trading Community Architecture (TCA) model, a party site represents a physical location associated with a party, such as a customer address. While HZ_PARTY_SITES holds the core address and location data, HZ_PARTY_SITES_EXT_B provides the configurable descriptor flexfield storage that allows implementers to capture organization-specific information without altering the base table structure. The "_B" suffix denotes that this is the base table of an extensible attribute pair, typically accompanied by a corresponding "_TL" table for translated or language-specific content.

The table is registered as VALID in the ETRM documentation for 12.1.1 and 12.2.2 and contains 58 documented columns. From a Data Vault modeling perspective, the heuristic classification is satellite-leaning: the table extends HZ_PARTY_SITES with descriptive attributes keyed by a surrogate identifier, rather than representing an independent business entity or an associative relationship between two hubs.

Key Information Stored

The table is organized around a surrogate primary key and a foreign key to the parent party site, with the remaining columns dedicated to extension attribute storage. The most significant columns are:

Note that the documented unique index covers EXTENSION_ID only; PARTY_SITE_ID functions as the business-key candidate for joining back to the parent site.

Common Use Cases and Queries

The principal use case is retrieving organization-specific attributes for a customer or party site alongside the base address data. A typical query joins the extension table to its parent:

  • SELECT ps.party_site_id, ps.party_site_name, ext.c_ext_attr1, ext.n_ext_attr1, ext.d_ext_attr1 FROM hz_party_sites ps, hz_party_sites_ext_b ext WHERE ps.party_site_id = ext.party_site_id;
  • Filtering by context using ATTR_GROUP_ID to isolate a particular descriptor group: WHERE ext.attr_group_id = :group_id.
  • Reporting on date-based extensions, for example identifying sites whose D_EXT_ATTR values fall within a compliance window.
  • Integration and migration scripts that populate extension attributes after the base party site is created, since the foreign key requires the parent row to exist first.
  • Audit queries using CREATION_DATE and LAST_UPDATE_DATE to track recently modified extension data.

Because the extension columns are generic, reports must map each C_/N_/D_ attribute to its business meaning through the descriptor setup, typically configured in the TCA extensible attribute definition screens.

Related Objects

The following objects are most significant in relation to HZ_PARTY_SITES_EXT_B:

  • HZ_PARTY_SITES — The parent table; joined via HZ_PARTY_SITES_EXT_B.PARTY_SITE_ID = HZ_PARTY_SITES.PARTY_SITE_ID. This is the only documented foreign key relationship.
  • HZ_PARTY_SITES_EXT_B_PK — The primary key constraint on EXTENSION_ID.
  • HZ_PARTY_SITES_EXT_B_U1 — The unique index on EXTENSION_ID, serving as the business-key candidate.
  • HZ_LOCATIONS — Holds the underlying address details referenced by party sites; indirectly related through HZ_PARTY_SITES.
  • HZ_PARTIES — The party master; reachable through HZ_PARTY_SITES for reporting that combines party and site extension data.
  • HZ_PARTY_SITE_USES — Defines the business purposes for which a party site is used, useful when extension attributes are purpose-specific.
  • HZ_CUST_ACCT_SITES_ALL — Links party sites to customer accounts, providing the path from extension attributes to Receivables transactions.
  • TCA extensible attribute APIs — The public application programming interfaces that maintain extension rows and enforce descriptor validation.