Search Results hr_locations_all_tl




Overview

HR_LOCATIONS_ALL_TL is the translated (TL) child table of the HR_LOCATIONS_ALL base entity within the Oracle E-Business Suite 12.1.1 and 12.2.2 releases. It resides in the HR schema and belongs to the PER (Human Resources) product family. Its documented purpose is to hold translated location codes and descriptions, meaning that for each location row in the base table, one translated row exists per installed language. This design enables multilingual display of location names without duplicating the operational attributes (address, effective dates, inventory associations) that are stored once in HR_LOCATIONS_ALL. The table is registered as VALID and is exposed through seeded location-related user interfaces, concurrent programs, and many downstream EBS modules that render location information.

From a data modeling perspective, the mined Data Vault classification for this object is standalone. Treating HR_LOCATIONS_ALL_TL as a standalone attribute container is therefore a suggested modeling position rather than a formally declared Data Vault construct. In practice, the row is best understood as a language-specific descriptive satellite attached to the location business key, keyed by location identifier and language.

Key Information Stored

The table documents 10 physical columns. The most significant are described below.

  • LOCATION_ID — Surrogate identifier of the parent location record. It is the first column of the composite primary key HR_LOCATIONS_ALL_TL_PK.
  • LANGUAGE — Language code for the translated row. It is the second column of the primary key, so the pair (LOCATION_ID, LANGUAGE) uniquely identifies each record and constitutes the documented business key.
  • SOURCE_LANG — Identifies the language of the source text, used by the translation framework to track the origin of the translated content.
  • LOCATION_CODE — The translated short code or mnemonic by which the location is known to users in the given language.
  • DESCRIPTION — The translated descriptive name of the location, which is the primary presentation attribute shown in list-of-values, reports, and forms.
  • LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN — Standard audit columns recording when the translated row was last changed and by whom. These drive audit reporting and change-data-capture logic.
  • CREATED_BY, CREATION_DATE — Standard creation audit columns capturing the user and timestamp that first inserted the translated row.

The composite primary key (LOCATION_ID, LANGUAGE) is the only documented unique index, and there is no surrogate single-column key. The base, non-translated attributes of a location are not stored here; only code and description are translated.

Common Use Cases and Queries

Typical usage retrieves the translated code and description for a location in the session language, joined to the base table for operational details.

  • Returning the display name of a location for a reporting query: join HR_LOCATIONS_ALL on LOCATION_ID and filter the translation by the active language.
  • Detecting missing translations for a language so that translation administrators can complete the setup.
  • Building multilingual location list reports and address directories.

A representative query pattern joining the base and translated tables, filtered by language code, would select the location identifier, translated code, and translated description where the language matches the reporting requirement. Because HR_LOCATIONS_ALL_TL is a child of the base location table, all joins are performed on LOCATION_ID.

Related Objects

  • HR_LOCATIONS_ALL — The base location table that provides the non-translated operational attributes and the parent LOCATION_ID key.
  • HR_LOCATIONS_ALL_TL — This object's own management through the Oracle translation (TCA/TL) framework, which maintains SOURCE_LANG rows.
  • HR_LOCATIONS — The commonly used view that resolves the session language and exposes location code and description for form and report use.
  • HR_LOCATION_ASSOCIATIONS — Associates locations with business groups; joins through LOCATION_ID.
  • HR_ORGANIZATION_UNITS — Organizational units reference locations, linking through the location identifier.
  • HR_ALL_ORGANIZATION_UNITS_TL — A parallel translated table for organization units, illustrating the consistent TL pattern used across HR.
  • PER_ADDRESSES / HR_LOCATION_DETAILS — Address and detail records that depend on the location definition and share the LOCATION_ID key.

These relationships confirm that HR_LOCATIONS_ALL_TL is a descriptive companion to the location entity and is consulted wherever a user-facing, language-specific location label is required.