Search Results fnd_menus_s

Overview

FND_MENUS_PKG is a server-side PL/SQL package body owned by the APPS schema that encapsulates the data-management logic for Oracle E-Business Suite menu definitions. Menus are the hierarchical containers that group functions (forms, concurrent programs, and web pages) into navigable application structures, and they form the backbone of both the standard Navigator and the role-based menu assignments used by function security. The package provides the low-level insert, update, lock, load, delete, and translation operations that keep the FND_MENUS, FND_MENUS_TL, and FND_MENUS_S tables consistent, and it centralizes validation of menu type and entry sequencing so that menu hierarchies remain well formed across all supported languages.

Within the 12.1.1 and 12.2.2 releases the package operates as an internal infrastructure layer rather than a public end-user API. Its documented dependencies include APP_EXCEPTION, FND_MESSAGE, FND_LOAD_UTIL, FND_LANGUAGES, FND_LOOKUPS, and FND_FUNCTION_SECURITY_CACHE, which indicates that it participates in both the loader framework (used by FNDLOAD for menu migration between environments) and the function security cache that EBS builds and invalidates when menu or function grants change. The ETRM registry classifies the API class as OTHER and records twelve documented procedures or functions. The body is VALID in the documented environment and, notably, is not referenced by any other database object under the recorded dependency set.

Key Procedures and Functions

• INSERT_ROW — Creates a new menu row in the base table, establishing the menu identifier used by dependent translation and security records.
• LOCK_ROW — Obtains a row-level lock on an existing menu record to serialize concurrent modification during update transactions.
• UPDATE_ROW — Applies changes to an existing menu definition, including its descriptive attributes and hierarchy metadata.
• LOAD_ROW — Supports the FNDLOAD/loader interface by inserting or updating a menu row from a definition file, typically in a migration or patch context.
• DELETE_ROW — Removes a menu definition and its associated child records when the menu is no longer required.
• ADD_LANGUAGE — Creates the translated row for a menu in a target language so that the menu can be displayed in that locale.
• TRANSLATE_ROW — Populates or refreshes the language-specific text of a menu entry in FND_MENUS_TL.
• SET_NEW_MENU — Initializes a new menu context, establishing the identity and defaults used by subsequent entry operations.
• NEXT_ENTRY_SEQUENCE — Returns the next available sequence number for a menu entry, preserving the ordered presentation of functions within a menu.
• VALIDATE_MENU_TYPE — Confirms that the supplied menu type is a valid lookup value before the definition is persisted.

The remaining documented procedures complete the twelve-entry inventory and follow the same internal maintenance pattern. Parameter lists are not published in the ETRM metadata and are intentionally omitted here.

Tables Accessed

• FND_MENUS — The primary table holding menu definitions and their attributes; the target of INSERT_ROW, UPDATE_ROW, LOAD_ROW, LOCK_ROW, and DELETE_ROW.
• FND_MENUS_TL — The translation table storing language-specific menu text; written by ADD_LANGUAGE and TRANSLATE_ROW.
• FND_MENUS_S — The sequence/identifier support table referenced in the dependency list, used to generate or track menu identifiers. Users searching for "fnd_menus_s" are typically looking for this object in the context of FND_MENUS_PKG's insert path.
• FND_LANGUAGES — Consulted to determine installed languages and to validate the target language for translation operations.
• DUAL — Used for single-row evaluations and sequence or value retrieval within the package logic.

Usage Notes

FND_MENUS_PKG is normally invoked indirectly. The standard application forms that maintain menus and menu entries call its procedures when a user saves changes, and the FNDLOAD concurrent program uses LOAD_ROW and the language procedures when uploading menu definitions from .ldt files during patching, cloning, or environment migration. Function security processing may trigger cache maintenance through the dependency on FND_FUNCTION_SECURITY_CACHE, so changes committed through this package can require a security cache rebuild before they take effect for end users.

Because the package is undocumented as a public API and is not referenced by other database objects, custom code should treat it as internal. Direct invocation is generally limited to controlled data-fix or migration scripts, and such scripts must supply valid menu types, maintain sequence integrity through NEXT_ENTRY_SEQUENCE, and honor the locking discipline provided by LOCK_ROW to avoid corrupting menu hierarchies or leaving orphaned translation rows.