Search Results hz_locations_ext_tl




Overview
Explore in AI Chat

Overview

The HZ_LOCATIONS_EXT_TL table is a core data object within the Oracle E-Business Suite (EBS) 12.1.1 and 12.2.2, specifically under the Receivables (AR) module. Its primary function is to provide multilingual support for extensible attributes associated with location data. This table enables the storage of translated text for custom attributes that extend the standard location information stored in the Trading Community Architecture (TCA) model. It is a critical component for global implementations where location details must be presented in multiple languages, ensuring that extended attributes adhere to the same localization standards as the base application data.

Key Information Stored

The table stores translated values for user-defined location attributes. Its structure is designed to support the multilingual model common in Oracle EBS. The primary key is a composite of the EXTENSION_ID and LANGUAGE columns, ensuring a unique translation entry per attribute per language. The LOCATION_ID column is a foreign key that links the translation to a specific master location record in the HZ_LOCATIONS table. The LANGUAGE column stores the language code (e.g., 'US' for American English) and is a foreign key to FND_LANGUAGES, the application's language registry. Other key columns typically include the translated text value itself (often named similarly to the source attribute) and standard WHO columns (CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN) for auditing.

Common Use Cases and Queries

This table is primarily accessed when generating localized reports or user interfaces that display extended location information. A common use case is retrieving a location's custom attributes in a user's session language for display in a form or a printed document. A typical query pattern involves joining this table to the base extension table (HZ_LOCATIONS_EXT_B) and the location master.

  • Sample Query for Session Language:
    SELECT hl.location_id,
    hlet.<translated_attribute_column>
    FROM hz_locations hl,
    hz_locations_ext_b hleb,
    hz_locations_ext_tl hlet
    WHERE hl.location_id = hleb.location_id
    AND hleb.extension_id = hlet.extension_id
    AND hlet.language = USERENV('LANG');
  • Data migration and translation upload processes for custom location attributes also interact directly with this table, often using the standard TCA APIs for data integrity.

Related Objects

The HZ_LOCATIONS_EXT_TL table has defined foreign key relationships with core application tables, as documented in the ETRM metadata.

  • HZ_LOCATIONS: The master location table. The relationship is established via HZ_LOCATIONS_EXT_TL.LOCATION_ID = HZ_LOCATIONS.LOCATION_ID. This links the translated extensible attribute to its specific location record.
  • FND_LANGUAGES: The application table that defines installed and available languages. The relationship is HZ_LOCATIONS_EXT_TL.LANGUAGE = FND_LANGUAGES.LANGUAGE_CODE, ensuring data integrity for language values.
  • HZ_LOCATIONS_EXT_B: While not listed in the provided foreign keys, this is the base table for location extensions. The EXTENSION_ID in the TL table originates from this base table, forming the core of the extension translation model.