Results for “hr_navigation_units_tl”
50+ results
AI-generated from documented ETRM metadata — verify critical details on the linked pages.
Overview
HR_NAVIGATION_UNITS_TL is the translation (multi-language) table that stores the language-dependent attributes of navigation units defined in the Oracle E-Business Suite Human Resources (PER) module. Navigation units are the configurable menu and page grouping elements used by the Oracle HRMS self-service and professional forms user interfaces to present function menus, responsibilities, and personalized navigation flows. While the base table HR_NAVIGATION_UNITS holds the language-independent definition of each navigation unit, HR_NAVIGATION_UNITS_TL holds the translatable text — principally the display label shown to end users — for each supported language.
The object resides in the HR schema and is classified as VALID in the 12.1.1 and 12.2.2 releases. From a Data Vault modeling perspective, the ETRM relationship mining classifies this object heuristically as standalone, meaning it carries no outbound foreign keys within the documented constraint set. In Data Vault terms it is best understood as a satellite attached to the HR_NAVIGATION_UNITS hub, keyed by the navigation unit identifier and language code. The presence of the ZD_EDITION_NAME column reflects the editioning and Online Patching infrastructure introduced in the EBS 12.2.2 architecture.
Key Information Stored
The table is defined with ten columns. The most significant are:
- NAV_UNIT_ID — the surrogate identifier of the parent navigation unit; part of the primary key and the join key to HR_NAVIGATION_UNITS.
- LANGUAGE — the NLS language code for the translated row; the second component of the primary key.
- SOURCE_LANG — the language from which the current translation was derived, supporting translation-workflow auditing and the "translatable" flag logic used by Oracle's TL-table maintenance forms.
- DEFAULT_LABEL — the translated display label presented to the user for the navigation unit in the given language. This is the primary business payload of the table.
- CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN — the standard Oracle Applications WHO columns providing audit and concurrency tracking.
- ZD_EDITION_NAME — the edition identifier used by the 12.2 Online Patching (adop) framework, included in the unique index HR_NAVIGATION_UNITS_TL_PK (NAV_UNIT_ID, LANGUAGE, ZD_EDITION_NAME).
The documented primary key is HR_NAVIGATION_UNITS_TL_PK, spanning NAV_UNIT_ID, LANGUAGE, and ZD_EDITION_NAME. The business-key candidate is the combination of NAV_UNIT_ID and LANGUAGE, since ZD_EDITION_NAME is an infrastructure artifact rather than a business attribute.
Common Use Cases and Queries
Typical use cases include localization validation, translation-gap analysis, and menu label reporting. A common pattern retrieves the English and localized label for each navigation unit:
- Translation coverage reporting — identify navigation units that lack a translated row for a given language by outer-joining HR_NAVIGATION_UNITS to HR_NAVIGATION_UNITS_TL on NAV_UNIT_ID and LANGUAGE.
- Label verification — query DEFAULT_LABEL for a specific NAV_UNIT_ID across all languages to confirm consistent terminology.
- Audit reporting — examine LAST_UPDATED_BY and LAST_UPDATE_DATE to determine when a label was last changed and by whom.
- Edition-aware queries — on 12.2.2, filter or group on ZD_EDITION_NAME to isolate current-edition rows during patching windows.
A representative SQL statement is:
SELECT t.nav_unit_id, t.language, t.default_label, t.source_lang
FROM hr.hr_navigation_units_tl t
WHERE t.language = 'US'
ORDER BY t.nav_unit_id;
Related Objects
The following objects are significant to the operation and interpretation of this table:
- HR_NAVIGATION_UNITS — the base (language-independent) table; join on NAV_UNIT_ID.
- HR_NAVIGATION_UNITS_TL_PK — the unique index enforcing the (NAV_UNIT_ID, LANGUAGE, ZD_EDITION_NAME) key.
- FND_LANGUAGES — reference for valid LANGUAGE and SOURCE_LANG values.
- FND_LANGUAGE_TL variants and standard TL maintenance forms — used to manage translated rows.
- PER_NAVIGATION_UNITS and related PER menu/function navigation objects — participatory in the same UI configuration chain.
- FND_APPLICATION — for context on the application owning the associated navigation structures.
Because the object is classified as standalone, no outbound foreign keys are documented; relationships to the parent navigation unit and to language reference data are implicit rather than constrained.
-
Translated fields for hr_navigation_units
-
Translated fields for hr_navigation_units