Results for “fnd_menus_tl”

AI-generated from documented ETRM metadata — verify critical details on the linked pages.

Overview

FND_MENUS_TL is the translation table for FND_MENUS in the Oracle E-Business Suite Applications Object Library (FND) schema, owned by APPLSYS. Every menu definition stored in FND_MENUS has one or more corresponding rows in FND_MENUS_TL, one per installed language, holding the language-specific user menu name and description. The table is central to the multi-language menu architecture of EBS 12.1.1 and 12.2.2, because the navigable menu tree presented to a user is assembled from the base menu row joined with the translated row matching the session language.

The structure of FND_MENUS_TL is a classic master-detail translation pattern: it is a dependent child of FND_MENUS and a parent of FND_MENU_ENTRIES_TL. Based on the mined foreign-key structure, the table is classified heuristically as satellite-leaning, meaning it is best modeled as a satellite attached to the FND_MENUS hub, keyed by menu and language, with descriptive attributes rather than as an independent hub or link.

Key Information Stored

The documented physical schema contains eleven columns. The most significant are:

• MENU_ID – surrogate identifier of the parent menu; part of the composite primary key FND_MENUS_TL_PK together with LANGUAGE, and the foreign key to FND_MENUS.
• LANGUAGE – the installed language code for the translated row; the second component of the primary key.
• USER_MENU_NAME – the translated display name of the menu as presented to end users; also a business-key candidate through the unique index FND_MENUS_TL_U2 (USER_MENU_NAME, LANGUAGE, ZD_EDITION_NAME) and the documented unique key FND_MENUS_TL_UK1 (LANGUAGE, USER_MENU_NAME).
• DESCRIPTION – the translated description of the menu.
• SOURCE_LANG – the language in which the row was originally authored; used by the translation (MLS) framework to determine whether a row has been translated.
• ZD_EDITION_NAME – the editioning column introduced in 12.2 for online patching; it participates in the unique indexes FND_MENUS_TL_U1 (MENU_ID, LANGUAGE, ZD_EDITION_NAME) and FND_MENUS_TL_U2.
• LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN – standard Who columns recording the last modification of the translated row.
• CREATION_DATE, CREATED_BY – standard Who columns recording row creation.

Note that FND_MENUS_TL_PK remains the surrogate primary key over MENU_ID and LANGUAGE, while FND_MENUS_TL_U1 and FND_MENUS_TL_U2 are the documented unique (business-key) candidates.

Common Use Cases and Queries

The primary use case is resolving the translated label of a menu for a given language. A typical query joins the base and translation tables:

• SELECT m.menu_id, t.user_menu_name, t.description FROM fnd_menus m, fnd_menus_tl t WHERE m.menu_id = t.menu_id AND t.language = USERENV('LANG');

Reporting scenarios include auditing which menus have been translated into which languages, identifying menus still held in their source language (SOURCE_LANG = LANGUAGE with no translated counterpart), and reconciling menu names against responsibility and function assignments. Translation maintenance is normally performed through the Application Object Library menu form rather than by direct DML, since the MLS framework manages the SOURCE_LANG and translation status flags.

Related Objects

The FK metadata identifies the following primary relationships:

• FND_MENUS – parent table; joined on FND_MENUS_TL.MENU_ID = FND_MENUS.MENU_ID.
• FND_MENU_ENTRIES_TL – child translation table for menu entries; joined on MENU_ID and LANGUAGE.
• FND_MENU_ENTRIES – base menu entry table that consumes the menu via MENU_ID.
• FND_RESPONSIBILITY – responsibilities reference menus, linking translated names to the runtime navigation.
• FND_APPLICATION – the owning application that groups menus within the navigator.

Together these objects form the menu definition and translation layer used by the EBS navigator and the FND security model.