Search Results next_entry_sequence

Overview

FND_MENUS_PKG is a core Oracle E-Business Suite (EBS) Application Object Library (FND) package owned by the APPS schema. In Oracle EBS 12.1.1 and 12.2.2 it provides the maintenance interface for the menu definitions that comprise the navigational structure of the EBS application. Menus defined through this package drive the EBS Navigator, the menu-based access control enforced by function and responsibility assignments, and the hierarchical navigation trees exposed to end users. The package encapsulates the data manipulation and language-handling logic required to create, update, load, delete, and translate menu records, together with row-locking and identifier-management utilities. Because the objects are stored in the APPS schema and the package is a VALID object per the ETRM record, it is fully enabled for callers holding appropriate privileges. The package is classified as OTHER in the ETRM API metadata; it is a supporting utility and maintenance (DML) package rather than a formal public business API with a published concurrency contract.

Key Procedures and Functions

The documented metadata lists twelve procedures and functions within FND_MENUS_PKG. Their names indicate standard AD-style row-maintenance behavior:

• INSERT_ROW — inserts a new menu definition row.
• LOCK_ROW — acquires a lock on an existing menu row to serialize concurrent updates.
• UPDATE_ROW — modifies attributes of an existing menu row.
• LOAD_ROW — loads or seeds a menu row, typically during setup data installation or migration.
• DELETE_ROW — removes a menu row.
• ADD_LANGUAGE — creates the translated-language row in the menu translation structure.
• TRANSLATE_ROW — populates or updates the translated text for a menu row.
• SET_NEW_MENU — establishes context for a newly created menu identifier.
• NEXT_ENTRY_SEQUENCE — computes the next sequence position for an entry within a menu.
• VALIDATE_MENU_TYPE — verifies the menu type value against valid values.

The ETRM record does not document parameter lists, so exact signatures are not reproduced here. All procedures are conventionally invoked through the standard FND maintenance pattern: LOCK_ROW followed by UPDATE_ROW for updates, and INSERT_ROW / LOAD_ROW for creation.

Tables Accessed

The ETRM dependency information lists the following tables, accessed via APPS synonyms: FND_MENUS (the base menu definition table), FND_MENUS_TL (the translation table for menu display names), FND_MENUS_S (the sequence/audit shadow structure associated with the translated table), FND_LANGUAGES (the installed-language reference), and DUAL. The package operates on the translated base/translation pair, which is why ADD_LANGUAGE and TRANSLATE_ROW exist alongside INSERT_ROW and UPDATE_ROW. FND_LANGUAGES is read to determine valid language targets for translation operations, and DUAL is used for scalar evaluations such as next-sequence derivation.

Usage Notes

FND_MENUS_PKG is referenced by four other APPS packages: FND_IREP_LOADER_PRIVATE, FND_MENU_ENTRIES_PKG, JTFB_DCF, and PAY_IP_UTILITY, plus a self-reference. This indicates it is consumed by menu-entry maintenance, i-Repository loading, and payroll utility code, confirming its role as a shared foundation routine. It is typically invoked by:

• EBS setup forms that maintain menu definitions, which call the DML procedures under the form's transaction control.
• Concurrent programs and setup loaders that seed or migrate menu data via LOAD_ROW.
• Custom code, provided the caller commits after LOCK_ROW and does not bypass the language-handling procedures when translation is required.

Because the package mixes row maintenance and translation handling, callers must preserve the base/translation integrity: inserts should be paired with ADD_LANGUAGE and TRANSLATE_ROW for every installed language. Changes to menus affect responsibility-level navigation, so testing should be performed in a non-production environment before any bulk update.