Results for “fnd_menu_entries”

50+ results




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

Overview

FND_MENU_ENTRIES is a core Oracle E-Business Suite Applications Object Library (FND) table owned by the APPLSYS schema. It stores the individual entries that compose navigate-window menus, defining how menus are assembled from other menus and from executable form functions. Each row represents one ordered entry within a given menu, identified by the composite business key of MENU_ID and ENTRY_SEQUENCE. In releases 12.1.1 and 12.2.2 the table remains VALID and is central to the way EBS renders the hierarchical navigation that end users traverse to reach forms, concurrent programs, and other functions.

Because each row records a parent-child association between a menu and either a sub-menu or a function, the table functions as a junction or link construct in Data Vault terms. The 11-column physical schema and its satellite-leaning classification (satellite-leaning per the mined FK structure) suggest that MENU_ID plus ENTRY_SEQUENCE form the durable hub-style key, while descriptive and flag attributes behave as satellite content. This classification is a modeling suggestion rather than an EBS-imposed constraint.

Key Information Stored

  • MENU_ID — The menu to which the entry belongs; part of the primary key FND_MENU_ENTRIES_PK and a foreign key to FND_MENUS.
  • ENTRY_SEQUENCE — The ordinal position of the entry within the menu; second component of the primary key and the field that establishes display order.
  • SUB_MENU_ID — When the entry references a nested menu rather than a function, this column points to the child menu in FND_MENUS.
  • FUNCTION_ID — When the entry exposes a function, this column references FND_FORM_FUNCTIONS.
  • GRANT_FLAG — A flag indicating whether the entry may be granted to a responsibility; used in menu security and responsibility assignment logic.
  • ZD_EDITION_NAME — The edition-designator column used by EBS online patching to distinguish editions; part of the unique index FND_MENU_ENTRIES_U1.
  • LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN — Standard audit columns recording when and by whom the row was last modified.
  • CREATION_DATE, CREATED_BY — Standard audit columns recording row creation.

Two candidate business keys are documented: FND_MENU_ENTRIES_PK (MENU_ID, ENTRY_SEQUENCE) and the unique index FND_MENU_ENTRIES_U1 (MENU_ID, ENTRY_SEQUENCE, ZD_EDITION_NAME). The latter is the edition-aware business key required under the 12.2 online patching model.

Common Use Cases and Queries

Typical uses include menu hierarchy reporting, responsibility-to-menu tracing, and impact analysis before menu changes. A common reporting pattern resolves nested menus by self-joining through SUB_MENU_ID:

  • List all entries for a specific menu: SELECT menu_id, entry_sequence, sub_menu_id, function_id, grant_flag FROM fnd_menu_entries WHERE menu_id = :menu_id AND (zd_edition_name IS NULL OR zd_edition_name = 'SET1') ORDER BY entry_sequence;
  • Trace entries that expose functions: join to FND_FORM_FUNCTIONS on FUNCTION_ID to retrieve function names, form names, and parameters.
  • Trace nested menus: join SUB_MENU_ID to FND_MENUS to walk the hierarchy and detect recursion or depth.
  • Identify grantable entries: filter on GRANT_FLAG to audit which menu items can be assigned through responsibility setup.

These queries support menu audit, navigation troubleshooting, and migration or upgrade validation, particularly when confirming that entry sequences and grant flags survive patching cycles.

Related Objects

  • FND_MENUS — Referenced via MENU_ID and SUB_MENU_ID; defines the parent menu and any nested child menu.
  • FND_FORM_FUNCTIONS — Referenced via FUNCTION_ID; supplies the form function exposed by an entry.
  • FND_MENU_ENTRIES_TL — The translation (multilingual) table; references FND_MENU_ENTRIES on MENU_ID and ENTRY_SEQUENCE, holding language-specific prompt text.
  • FND_RESPONSIBILITY / FND_COMPILED_MENU_FUNCTIONS — Compiled menu structures derive from menu entries and drive what a responsibility can access.
  • FND_MENU_ENTRIES_PK / FND_MENU_ENTRIES_U1 — The primary key and edition-aware unique index enforcing uniqueness of menu entry identities.

Together these objects form the menu definition and translation layer that underpins EBS navigation and responsibility security in both 12.1.1 and 12.2.2.