Used to define a new menu or modify an existing menu.
A menu is a hierarchical arrangement of functions and menus of functions. Each responsibility has a menu assigned to it.
You can build a custom menu for that responsibility using predefined forms. However, we recommend that you do not disassociate a form from its developer-defined menus.
After you save your changes in this form, a request is submitted to compile the menu data.
See:
Implementing Function Security
Before you define your menu, perform the following:
Register your application using adsplice. See: AD Splicer and My Oracle Support Knowledge Document 1577707.1, Creating a Custom Application in Oracle E-Business Suite Release 12.2.
Register any forms you wish to access from your menu with Oracle Application Object Library using the Forms window.
Define any functions you intend to call from your menu.
Define any menus that you intend to call from your menu. Define the lowest-level submenus first. A submenu must be defined before it can be called by another menu.
Tip: By calling submenus from your menu, you can group related windows together under a single heading on your menu. You can reuse your menu on other menus.
Menu entries detail the options available from your menu.
Choose a name that describes the purpose of the menu. Users do not see this menu name.
Note: Once the menu is saved, this menu name cannot be updated.
Once you have defined a menu, you can see its hierarchical structure using the "View Tree..." button. See: Menu Viewer.
You use the user menu name when a responsibility calls a menu or when one menu calls another.
Specify a menu type to describe the purpose of your menu. Options include:
Standard - for menus that would be used in the Navigator form
Tab - for menus used in self service applications tabs
Security - for menus that are used to aggregate functions for data security or specific function security purposes, but would not be used in the Navigator form
In addition, see the section on Oracle Application Framework menu types.
If this menu will be an item on a "Level 1" menu, provide the name of a seeded icon to assign to the menu. This icon displays when the profile FND: Top-Level Menu Display Mode is set to display the "Level 1" menu as icons and links.
Fields include the following:
Enter a sequence number to specify where a menu entry appears relative to other menu entries in a menu. The default value for this field is the next whole sequence number.
Important: You can only use integers as sequence numbers.
A menu entry with a lower sequence number appears before a menu entry with a higher sequence number.
You cannot replace a menu entry sequence number with another sequence number that already exists. If you want to add menu entries to a menu entry sequence, carefully renumber your menu entries to a sequence range well outside the sequence range you want, ensuring that you do not use existing sequence numbers. If you want to renumber an entry, then delete the entire row and save your work; and then insert a new row with the desired sequence number and same prompt and submenu/function as the previous one.
Enter a user-friendly, intuitive prompt your menu displays for this menu entry. You see this menu prompt in the hierarchy list of the Navigator window.
Tip: Enter menu prompts that have unique first letters so that power users can type the first letter of the menu prompt to choose a menu entry.
Call another menu and allow your user to select menu entries from that menu.
Call a function you wish to include in the menu. A form function (form) appears in the Navigate window and allows access to that form. Other non-form functions (subfunctions) allow access to a particular subset of form functionality from this menu.
Descriptions appear in a field at the top of the Navigate window when a menu entry is highlighted.
The Grant check box should usually be checked. Checking this box indicates that this menu entry is automatically enabled for the user. If this is not checked then the menu entry must be enabled using additional data security rules.
For more information on grants, see Overview of Data Security and Grants.