Search Results fnd_menu_entries_pkg




Overview

The APPS.FND_MENU_ENTRIES_PKG package is an Oracle Application Object Library (FND) utility responsible for managing the rows that make up Oracle E-Business Suite menus. In Oracle EBS, the navigable menu structure presented to users is defined by menu definitions stored in FND_MENUS and their constituent entries stored in FND_MENU_ENTRIES and FND_MENU_ENTRIES_TL. This package encapsulates the insert, update, delete, load, lock, and translation logic required to maintain those entries consistently, including the seed-data and language-installation paths used when menus are populated from loader files. It is classified as an "OTHER" APIdatabase object in the ETRM repository, meaning it is a repository-internal or administrative utility rather than a large public business API, but it remains central to menu maintenance operations. In both 12.1.1 and 12.2.2 the package is reported VALID in the APPS schema, and the documented metadata records ten procedures/functions.

Key Procedures and Functions

The documented callable units cover the full DML and lifecycle of a menu entry record:

  • INSERT_ROW — creates a new menu entry row, establishing the parent menu, the referenced submenu or function, and the prompt/sequence attributes.
  • LOCK_ROW — obtains a row-level lock on an existing menu entry, typically used to serialize concurrent maintenance before an update.
  • UPDATE_ROW — modifies the attributes of an existing menu entry (for example prompt, description, or ordering).
  • DELETE_ROW — removes a menu entry, cleaning up the base and translated records.
  • LOAD_ROW — loads a menu entry from a seed/loader data source; this is the path used by menu migration and repository loaders.
  • ADD_LANGUAGE — creates the translated (_TL) row for a menu entry when a new language is installed or a translation is introduced.
  • TRANSLATE_ROW — maintains the translated prompt and description text for an existing menu entry in a target language.
  • SUBMIT_COMPILE — submits the compilation step that refreshes the menu structure so that menu changes become effective in the runtime navigation cache.

The remaining two documented units are the package specification and body themselves. Note that the metadata does not expose parameter lists, so no signatures are asserted here.

Tables Accessed

All table access occurs through APPS synonyms. The package reads and writes:

  • FND_MENUS — the parent menu definition validated when an entry is created or updated.
  • FND_MENU_ENTRIES — the base (untranslated) menu entry records.
  • FND_MENU_ENTRIES_TL — the translated prompt/description rows, managed by ADD_LANGUAGE and TRANSLATE_ROW.
  • FND_FORM_FUNCTIONS — referenced to validate that a menu entry points to a legitimate function.
  • FND_LANGUAGES — used to determine installed/valid languages during translation handling.
  • DUAL — used for scalar evaluation in the PL/SQL logic.

Usage Notes

This package is normally invoked indirectly rather than called by user code. It is referenced by eight other packages, notably FND_IREP_LOADER_PRIVATE and FRM_REPOSITORY_MAINTENANCE, which drive menu loading and repository refresh, and by migration/utility packages such as CSD_MIGRATE_FROM_12X_PKG8, IEX_CHECKLIST_UTILITY, JTFB_DCF, PAY_IP_STARTUP_UTIL, PAY_IP_UTILITY, and PQP_RIW_WEBADI_UTILS. Menu maintenance is typically executed through the Application Developer responsibility forms, patching (AD utilities), and menu migration processes; those tools call the loader and maintenance packages that in turn call FND_MENU_ENTRIES_PKG. Because changes to menu definitions affect the runtime navigation hierarchy, entries should be added or altered only through supported loaders or forms, and any direct invocation should conclude with SUBMIT_COMPILE to propagate the change. Direct custom calls are discouraged, as the package logic is tightly coupled to seed-data loaders and language installation.