This is version 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 . It is not the current version, and thus it cannot be edited.

Back to current versionRestore this version

MAINTAIN MENUS#

A Menu is a list which groups a specific set of functions together and is used to help you quickly locate and select a function. Through the application, the functions and their sequential order can be tailored for your company’s needs

The Menu Definitions (IMMU) screen allows you to define and arrange the menus that users will see when they are in the application.

You do not need to create your own menus or modify the existing menus unless you are adding new functions, or need to change the order (sequence) of items. You can control which menu items show in the delivered menus with execution rights (execution type roles and (IMER) and change menu labels with languages and translations.

For a menu or sub-menu, the label in IMMU is displayed as the Title of the menu item and the purpose in IMMU is displayed as the description.

For a function in a menu, the label in IMMU is displayed as the title of the menu item and the purpose in Function Definitions (IMFN) is displayed as the description.

RECOMMENDATION: Do not create any more than three layers in the path (Menu calling a Function, or Menu calling a Sub-Menu calling a Function) as the navigation tree will not be user-friendly. Also do not mix sub-menus and functions within a menu. If a menu calls a sub-menu then it should only call other sub-menus, no functions and vice versa.

The path should be EITHER:

• Menu > Function, or
• Menu > Sub-Menu > Function

For the entire menu, do not mix and match paths. For example, the path for Maintain Personnel Actions is Human Resources > Personnel Actions > Maintain Personnel Actions (Menu > Sub-menu > Function)

This means that the function Maintain Personnel Actions has the parent menu Personnel Actions. The sub-menu Personnel Actions has the parent menu Human Resources.

Below is an in-depth discussion of the Create Menus screen and the individual fields within the screen, followed by a step-by-step set of instructions on how to maintain menus within the application.

When you create a new menu, you must log out and log back in again for the new sub-menus to show one the menu drop-down list. At the top of the form, you will see a list of all the menus in the application identified by menu code. By clicking on one of the menus listed, you will be able to see further details about that menu in the following fields.

The definition data for the Menu Definitions screen is stored in the P2K_AM_MENUS, and P2K_AM_MENU_ITEMS table.

Menu

This field is the unique abbreviation which identifies the individual menu. The code should be reflective of the type of functions found within the menu.

Description

This field provides a short description of what the menu entails.

Usage

This field identifies whether the menu was provided with the application (Pre-Loaded) or if it custom for the client (User Defined).

Parent Menu

This field is the unique abbreviation of the parent menu which the sub menu is associated to.

Usage

This field identifies if the menu was provided with the application (Pre-Loaded) or if it custom for the client (User Defined).

Seq #

The number in this field will determine the sequential order in which the functions will appear in the menu.

Item

This field displays the unique name of the menu.

Type

This field classifies the menu item into a specific type.

For example: Call Function, Sub-menu

Function

If the menu item is a function, that function will be identified in this field.

or Submenu

If the menu item calls another menu, identify that sub-menu in this field.

A menu item may call either a Sub-Menu or a Call Function but not both.

Label

This field will display the complete name of the menu item.

Label (FRE)

If the menu has an alternate language, the translation for the label will be held in this field.

Usage

This field identifies whether the menu item is pre-loaded or user defined.

A Pre-loaded usage means that the system created and controls the information and it will be overwritten with every update.

A User-Defined usage means that the user created and controls the information and it will not be overwritten when you receive a software update.

Icon Name

This field allows you to identify the icon which you would like to use. You need only enter the icon name in this field, not the path.

e.g. address_ phone.gif

The file name must be entered with the exact spelling and case as indicated in the icons folder.

The application will look to the following path for the icon indicated.

For example:

D:\ORACLE\ias10g\Apache\Apache\htdocs\HLAppResources\release\images\icons

Action Type

If the menu is used for a particular action, the action type is displayed here. For example, the HELP menu has an 'OpenWindows' action associated to it as when the Help icon is pressed, a help window is opened.

Action Value

The action called by the menu is listed here.

Purpose

This field identifies the intent and usage of the menu item.

Purpose (FRE)

If the menu has an alternate language, the translation for the purpose will be held in this field.