Search Results hz_party_sites_ext_tl_n1




Overview
Explore in AI Chat

Overview

AR.HZ_PARTY_SITES_EXT_TL is a translation (TL) table in the Oracle E-Business Suite 12.1.1 and 12.2.2 Trading Community Architecture (TCA) data model. It provides multilingual support for the extensible, user-defined attributes attached to party sites. Party sites are the physical locations associated with a party record, such as a customer's billing or shipping address. Because the TCA extensible attribute framework allows customers to configure their own descriptive fields, those fields frequently require language-specific content. This table stores that translated content, keyed by extension and language, so the same party site can present different attribute text to users operating in different languages.

Object details record the owner as AR (the Receivables schema, which historically hosts much of the TCA foundation) and the status as VALID. Storage is in the APPS_TS_TX_DATA tablespace with a PCTFREE of 10, while its indexes reside in APPS_TS_TX_IDX. Based on the foreign key structure, the object is best treated, as a modeling suggestion, as a link table in Data Vault terms: it connects the party site extension entity to the language dimension, resolving a many-to-many style relationship through its composite key.

Key Information Stored

The table is defined with 30 documented columns. The most significant are:

The primary key is HZ_PARTY_SITES_EXT_TL_PK (EXTENSION_ID, LANGUAGE). The unique index HZ_PARTY_SITES_EXT_TL_U1, the object the user searched for, enforces uniqueness on the same business-key candidate combination of (EXTENSION_ID, LANGUAGE) in the APPS_TS_TX_IDX tablespace. A nonunique index, HZ_PARTY_SITES_EXT_TL_N1, supports access by (PARTY_SITE_ID, LANGUAGE).

Common Use Cases and Queries

Typical use cases include multilingual reporting on party site extensible attributes, data migration and interface work where translations must be loaded, and troubleshooting where a user sees the wrong attribute text for a given language. A frequent query pattern joins the translation row back to its extension and site using the composite key:

  • Retrieve translated attributes for a site: SELECT t.extension_id, t.language, t.tl_ext_attr1 FROM hz_party_sites_ext_tl t WHERE t.party_site_id = :site_id AND t.language = USERENV('LANG');
  • Confirm uniqueness/authored language coverage: SELECT extension_id, language FROM hz_party_sites_ext_tl WHERE extension_id = :ext_id;
  • Compare source and translated values by joining on SOURCE_LANG to the base extension row.
  • Validate that each EXTENSION_ID has a row in every installed language required by FND_LANGUAGES.

Related Objects

The foreign keys and key relationships tie this table to the core TCA entities:

  • AR.HZ_PARTY_SITES_EXT_TL.PARTY_SITE_ID → HZ_PARTY_SITES — the parent party site record.
  • AR.HZ_PARTY_SITES_EXT_TL.LANGUAGE → FND_LANGUAGES — the installed language definition.
  • HZ_PARTY_SITES_EXT and its base extension table — the untranslated extension rows that provide EXTENSION_ID and ATTR_GROUP_ID context.
  • HZ_PARTY_SITES — the owning site entity used in joins for site-level reporting.
  • FND_LANGUAGES — the language dimension referenced by LANGUAGE and SOURCE_LANG.
  • HZ_PARTY_SITES_V (or equivalent TCA views) — commonly used to present combined base and translated party site data.
  • Oracle TCA / Customer APIs such as the HZ_PARTY_SITE APIs — used to insert or update these translation rows programmatically.