Search Results pa_role_status_menu_map

Overview

FND_MENUS is a core setup table in the FND (Application Object Library) product of Oracle E-Business Suite, owned by the APPLSYS schema. It stores the definitions of menus used throughout the EBS navigation framework. Its ETRM description identifies it as the "new menu table for Release 10SC," reflecting its role as the authoritative registry of menu objects that drive the Navigator, responsibility assignments, and function/security hierarchies. Each row represents a distinct menu, identified by a surrogate key and a user-facing menu name that is unique within the application.

Because FND_MENUS is referenced by a large number of downstream tables across multiple modules (FND, ICX, PA, PO, PER, FRM, AMW, QP, BSC), the mined Data Vault classification of hub is appropriate. The table acts as a central business-key anchor, with MENU_ID serving as the stable surrogate identifier and MENU_NAME serving as the natural business key referenced by several dependent objects.

Key Information Stored

• MENU_ID — surrogate primary key (FND_MENUS_PK); the internal identifier propagated to all child and referencing tables.
• MENU_NAME — the business-key menu name, enforced by unique index FND_MENUS_UK1/U2; referenced by AK_REGION_ITEMS via MENU_NAME.
• TYPE — indicates the menu classification (for example, standard versus other menu types), used to control how the menu is rendered and traversed.
• ZD_EDITION_NAME — editioning column supporting Online Patching in 12.2.2; combined with MENU_ID and MENU_NAME in unique indexes FND_MENUS_U1 and FND_MENUS_U2.
• LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN — standard WHO audit columns capturing change history and the session context of the last modification.
• CREATION_DATE, CREATED_BY — standard WHO audit columns recording menu creation metadata.

The surrogate key (MENU_ID) and the business-key candidates (MENU_NAME, together with the editioning column) are the columns most relevant for joins and lookups. The unique indexes FND_MENUS_U1 and FND_MENUS_U2 ensure both identity and name uniqueness under the editioning model.

Common Use Cases and Queries

FND_MENUS is typically queried when auditing responsibility-menu assignments, troubleshooting navigation visibility, or migrating menu structures between environments. A representative join to responsibilities reads:

SELECT fr.responsibility_name, fm.menu_id, fm.menu_name
FROM   fnd_responsibility fr, fnd_menus fm
WHERE  fr.menu_id = fm.menu_id;

To resolve menu entries and their order, analysts join FND_MENU_ENTRIES to FND_MENUS on MENU_ID (and to itself on SUB_MENU_ID for nested submenus). Translating menu content for a specific language requires a join to FND_MENUS_TL on MENU_ID. Security reviews often combine FND_MENUS with FND_GRANTS, FND_COMPILED_MENU_FUNCTIONS, and FND_RESP_FUNCTIONS to reconcile granted versus compiled function access. Reporting on the total set of defined menus simply selects MENU_ID, MENU_NAME, and TYPE from FND_MENUS.

Related Objects

• FND_RESPONSIBILITY — joins on MENU_ID; links each responsibility to its assigned menu.
• FND_MENU_ENTRIES — joins on MENU_ID and SUB_MENU_ID; defines the functions and submenus within a menu.
• FND_MENUS_TL — joins on MENU_ID; provides translatable menu descriptions.
• FND_RESP_FUNCTIONS — joins via ACTION_ID; maps functions granted through menus.
• FND_COMPILED_MENU_FUNCTIONS — joins on MENU_ID; stores the flattened, compiled menu-function hierarchy.
• FND_GRANTS — joins on MENU_ID; records menu-level grants.
• ICX_SESSIONS — joins on MENU_ID; captures the active menu for a user session.
• AK_REGION_ITEMS — joins on MENU_NAME (and MENU_ID); associates menus with regions.
• PA_PROJECT_ROLE_TYPES — joins on MENU_ID; links project roles to menus.

These relationships confirm FND_MENUS as a foundational hub referenced broadly across EBS functional and security schemas.