Search Results hz_party_sites_ext_tl_pk

Overview

HZ_PARTY_SITES_EXT_TL is a translation (TL) table in the Oracle E-Business Suite Receivables (AR) schema. It provides multilingual support for extensible party site attributes, meaning that user-defined (DDF/descriptive flexfield) attribute values associated with a party site can be stored and rendered in more than one installed language. The object is registered as VALID and owned by the AR schema, with the base (non-translated) extensible data residing in the corresponding HZ_PARTY_SITES_EXT entity.

From a Data Vault modeling perspective, the metadata suggests a link classification, inferred heuristically from the foreign key structure. This reflects the table's role as an associative structure joining party site extensibility records to language context, rather than a pure descriptive hub or satellite.

The table is central to the Trading Community Architecture (TCA) party site model. Party sites represent addresses and locations associated with parties (customers, prospects, suppliers, and other entities). When customers extend the party site record with additional attributes, the values are stored in the EXT structure, and their translated variants are persisted here, keyed by extension identifier and language.

Key Information Stored

The documented schema contains 30 columns. The most significant for integration and reporting are:

• EXTENSION_ID — Identifier of the extensible party site attribute record; part of the composite primary key and the foreign key to the base ext table.
• LANGUAGE — The installed language of the translated row; foreign key to FND_LANGUAGES and part of the composite primary key.
• PARTY_SITE_ID — Foreign key to HZ_PARTY_SITES, identifying the parent party site.
• ATTR_GROUP_ID — Identifies the attribute group to which the extensible attributes belong.
• SOURCE_LANG — The source language of the record, used by the TCA translation model to identify the originating language.
• TL_EXT_ATTR1 through TL_EXT_ATTR20 — Translatable extensible attribute columns holding the language-specific values.
• CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN — Standard EBS audit columns.

HZ_PARTY_SITES_EXT_TL_PK (EXTENSION_ID, LANGUAGE) is the primary key. A unique index, HZ_PARTY_SITES_EXT_TL_U1 (EXTENSION_ID, LANGUAGE), mirrors the same combination and represents the business-key candidate for the translation record. There is no separate single-column surrogate beyond EXTENSION_ID combined with LANGUAGE.

Common Use Cases and Queries

Typical scenarios include retrieving multi-language attribute values for a given party site, validating translation completeness, and joining the translation back to the base record and to HZ_PARTY_SITES for address reporting.

A representative query joins translations to the base structure:

• Join HZ_PARTY_SITES_EXT_TL t to HZ_PARTY_SITES_EXT b on t.EXTENSION_ID = b.EXTENSION_ID — retrieve all language variants for an extension.
• Join HZ_PARTY_SITES_EXT_TL t to HZ_PARTY_SITES s on t.PARTY_SITE_ID = s.PARTY_SITE_ID — resolve the owning party site.
• Join HZ_PARTY_SITES_EXT_TL t to FND_LANGUAGES l on t.LANGUAGE = l.LANGUAGE_CODE — filter to a specific installed language.
• Filter WHERE t.LANGUAGE = userenv('LANG') to present values in the session language.

Reporting uses include auditing which party sites have translated extensible attributes, checking for missing translations (base record exists without a TL row), and extracting attribute values for downstream CRM or integration interfaces.

Related Objects

The following objects are most significant relative to HZ_PARTY_SITES_EXT_TL:

• HZ_PARTY_SITES — Referenced via HZ_PARTY_SITES_EXT_TL.PARTY_SITE_ID; the parent party site record.
• FND_LANGUAGES — Referenced via HZ_PARTY_SITES_EXT_TL.LANGUAGE; the language definition source.
• HZ_PARTY_SITES_EXT — The base extensible attribute table that the translation augments via EXTENSION_ID.
• HZ_PARTIES — The parent party record linked through the party site.
• HZ_LOCATIONS — The location definition underlying a party site.
• TCA party APIs (for example, HZ_PARTY_SITE_V2PUB) — manage party site and extension lifecycles that populate this table.

Together these objects form the extensible party site address model within the AR/TCA schema, with HZ_PARTY_SITES_EXT_TL supplying the multilingual layer.