Search Results fnd_menus_u2

Overview

APPLSYS.FND_MENUS is a core Oracle E-Business Suite function security table that defines the menu structure presented in the Navigator window of the EBS HTML and Forms interfaces. Each row represents a menu or submenu belonging to an application, and the System Administrator associates these menus with responsibilities to control which functions a user can access. In EBS 12.1.1 and 12.2.2 the table resides in the APPS_TS_SEED tablespace, is flagged VALID in ETRM, and is owned by APPLSYS under the FND design data synonym FND.FND_MENUS. The object carries nine documented columns and is a heavily referenced parent table, with the ETRM relationship data identifying it as a hub in Data Vault modeling terms — a durable business entity referenced by many dependent link and satellite-style tables.

Key Information Stored

The table distinguishes a surrogate primary key from two business-key candidates:

• MENU_ID (NUMBER, mandatory) — the surrogate primary key defined by FND_MENUS_PK; the unique value that identifies a menu row internally.
• MENU_NAME (VARCHAR2(30)) — the user-facing menu identifier used by administrators and by dependent objects such as FND_MENU_ENTRIES and AK_REGION_ITEMS.
• TYPE (VARCHAR2(30)) — classifies the menu (for example standard versus other menu types recognized by function security).
• ZD_EDITION_NAME (VARCHAR2(30)) — the edition column introduced with 12.2 online patching, participating in both unique indexes.
• LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN, CREATION_DATE, CREATED_BY — the standard Who columns that record auditing information for each menu definition.

Two unique indexes enforce business uniqueness: FND_MENUS_U1 on (MENU_ID, ZD_EDITION_NAME) and FND_MENUS_U2 on (MENU_NAME, ZD_EDITION_NAME). The user search term "fnd_menus_u1" therefore resolves to the primary-key unique index guarding MENU_ID within an edition. In practice, only the seeded rows are populated; most custom menus are created through the Application Developer responsibility rather than direct inserts.

Common Use Cases and Queries

Typical scenarios include auditing responsibility-to-menu mappings, tracing why a function is absent from a Navigator, and validating upgrade or patching state. A representative query joins the menus to their responsibility assignments:

• SELECT m.menu_id, m.menu_name, m.type, r.responsibility_name FROM fnd_menus m, fnd_responsibility r WHERE r.menu_id = m.menu_id AND r.responsibility_key IS NOT NULL;
• SELECT menu_id, menu_name FROM fnd_menus WHERE menu_name LIKE 'FND%' ORDER BY menu_name;
• SELECT e.menu_id, e.sub_menu_id, e.function_id FROM fnd_menu_entries e, fnd_menus m WHERE e.menu_id = m.menu_id AND m.menu_id = :p_menu_id;
• SELECT menu_id, menu_name, type FROM fnd_menus WHERE zd_edition_name = 'ORA$BASE';

Reporting use cases include function security matrices, menu-to-responsibility impact analysis before changing or disabling a seeded menu, and reconciliation after an ADOP patching cycle in 12.2. Because the table is seeded and rarely updated at runtime, it is a stable dimension for such reports.

Related Objects

FND_MENUS is referenced by a large number of tables. The most significant dependencies include:

• FND_MENU_ENTRIES — the child table linking MENU_ID and SUB_MENU_ID back to FND_MENUS, defining the menu hierarchy and function assignments.
• FND_MENUS_TL — the translation table, joined on MENU_ID, holding menu descriptions in multiple languages.
• FND_RESPONSIBILITY — joins on MENU_ID to attach a menu to each responsibility.
• FND_RESP_FUNCTIONS — references ACTION_ID, connecting menus to excluded or included functions.
• FND_COMPILED_MENU_FUNCTIONS — the runtime cache of menu/function combinations, keyed on MENU_ID.
• FND_GRANTS — grants based on MENU_ID for delegated administration.
• ICX_SESSIONS and ICX_TRANSACTIONS — join on MENU_ID to record the menu context of a self-service session or transaction.
• AK_REGION_ITEMS — references both MENU_ID and MENU_NAME for region-level menu integration.

Additional referencing tables such as PER_RI_WORKBENCH_ITEMS, PO_COMMODITY_GRANTS, PA_PROJECT_ROLE_TYPES and PA_DIST_LIST_ITEMS extend menu usage into HR, Purchasing and Projects. Together these relationships confirm FND_MENUS as a central hub in the function security data model.