SAP ABAP IMG Activity GRFN_MAINCUSTMENU (Maintain Customer-Specific Menus)
Hierarchy
☛ GRCFND_A (Software Component) GRC Foundation ABAP
   ⤷ GRC-SPC (Application Component) Process Controls
     ⤷ GRPC_CUSTOMIZING (Package) Customizing
IMG Activity
ID GRFN_MAINCUSTMENU Maintain Customer-Specific Menus  
Transaction Code S_GR4_71000079   (empty) 
Created on 20081210    
Customizing Attributes GRFN_MAINCUSTMENU   Maintain Customer-specific Menus 
Customizing Activity GRFN_MAINCUSTMENU   Maintain Customer-specific Menus 
Document
Document Class SIMG   Hypertext: Object Class - Class to which a document belongs.
Document Name GRFN_MAINCUSTMENU    

Use

In this Customizing activity, you customize the menu of your Process Control and/or Risk Management application for use in the portal. This is the structure which contains all the tabs with the individual work centers, and defines the order of work centers, worksets and the individual menu items within them. In particular, you can:

  • Extend an existing menu with respect to the work centers displayed, and
  • Create an entirely new menu, with new work centers you define.

Before proceeding to adapt your menus, read the following background information on customizing the application menus.

Background information

Within the menu structure itself, you can define the order of work centers, menu groups and the items within the groups. Each application menu contains the following elements:

  • Work center: The work center ID is used in portal worksets to identify the work center configuration that displays the content processed within one work center. The text is used as the window header.
  • Menu group: The menu group is one element in the work center, referring to a workset. It has a title description and pictogram. The pictogram must be in a format that is accepted by the user interface (for example: WD ABAP View Element Image).
  • Menu item: Menu items represent individual navigation links. The text represents the link itself; the description becomes the quick info text that displays when you pass your mouse over it. Each menu item must belong to one of the application components:
    • FN = Common component (Process Control and Risk Management)
    • PC = Process Control
    • RM = Risk Management

Note: Customer menus are stored in client-specific tables of delivery type C (Customizing). This means that entries are initially created in a development system, and are then transported to the production system using a Customizing change request. If you want your changes maintained across several clients, you must maintain or copy the entries to the other clients of your system.

Requirements

The WebDynpro application(s) you have installed must be switched on in the Customizing activity Activate Applications in Client.

Standard settings

Activities

In order to customize the WebDynpro application menu, proceed as follows:

  1. Open the IMG activity and with the cursor on the left navigation item Work Center, click on the New Entries button and enter a user-defined name and description for each work center you are creating.
  2. With your cursor on the line of the work center you created, now double-click on the Menu Group section of the left navigation pane.
  3. Again click on the New Entries button and enter a user-defined name and description for each menu group (that is, the section of the work center) that you are creating.
  4. Save your data.
  5. Next, put the cursor on a menu group and double-click on the Menu Item section of the left navigation pane.
  6. Again click on the New Entries button and enter a menu item ID, a user-defined text and description for each menu item of this menu group that you are creating.
  7. In the field Application Component, select whether you want to customize the entire GRC menu, or only the PC or RM menu.
  8. For the field Menu Item Type, specify whether you want to leave it at the default (=URL) or choose another option. The following table provides further information:

Item Type    Application    Parameters (all -> Name1= Value 1)

WD APP    Name of WD Application    Parameters

URL    Not used    URL

BW 3.5    Templ.ID/Infoprov.ID/QueryID    Additional parameters

BW 7.0    Templ.ID/Infoprov.ID/QueryID    Additional parameters

BW Report    <empty>    Mandat. param.Report=<report_id>

Note: For the item types BW 3.5 Report and BW 7.0 Report, there are defined RFC destinations for BW systems via the report GRPC_BW_RFC. In this case, the RFC is used for the RFC call to a BW system to build the target URL.

  1. In the field App. Menu Item, enter a user-defined name for this menu item, which is to be displayed in the portal.
  2. Depending on whether you have selected "URL" as the menu item type, you can enter the URL in the corresponding field. If you have selected a menu item type other than an URL, enter the parameter(s) in this field. Set the checkmark in the Launch External checkbox if you want the application to be started in a separate window.
  3. Enter a Portal Content Directory (PCD) path if necessary.
  4. In the field Entity Eval(uation), specify which entities are required. You can specify whether it is sufficient to have authorization only for one entity to enable the item, or if it is necessary to have authorization for all entities to enable the item. If there is no entity defined for the item, this means that it is always displayed.
  5. In the field Itm Auth. Class (Item Authorization Class), select the authorization class to be used.

    Note: The menu application displays the items based on the authorization of the user. The menu group is hidden if all items are hidden by the authorization check. The authorization check checks the list of entities against the entities granted by authorization roles of the user.

  6. The field Operation provides an additional authorization check. You can use an exit class for the ABAP code-based authorization check for a menu item. To do this, observe the following:
    • Use the interface IF_GRFN_MENU_ITEM_AUTH.
    • The method provided by this interface is called IS_AUTHORIZED. This method has the importing parameter IO_SESSION type, referring to class CL_GRFN_API_SESSION.
    • Another importing parameter is IV_REGULATION of type GRFN_REGULATION.
    • The third parameter is IS_ITEM of type GRFN_S_API_MENU_ITEM, with the exporting parameter EV_AUTHORIZED of type GRFN_BOOLEAN.
    • The results from the exit class can be combined with the entity-based authorization by specifying the type of operation (NO, AND, OR). Make a selection here and save your data.
  7. Remain in this screen and click on Authorizations for Menu Items. Then click on New Entries and select one of the menu items that you created previously.
  8. Select an entity from the dropdown menu to be used with this menu item.
  9. Save your entry. Proceed in the same manner with all other menu items.
  10. Finally, with your cursor on the menu item you created, click on the Menu option in the left navigation pane.
  11. Again click on New Entries. Select a work center from the dropdown list, as well as a menu group and a menu item from the corresponding column dropdown lists. In the field Group Sequence, enter a number and in the field Menu Item Sequence, enter another number, to indicate the sequence of the menu groups you have created.
  12. Save your entry. Proceed in the same manner for all other entries you created on the uppermost level.

Example

Business Attributes
ASAP Roadmap ID 201   Make global settings 
Mandatory / Optional 2   Optional activity 
Critical / Non-Critical 2   Non-critical 
Country-Dependency A   Valid for all countries 
Assigned Application Components
Documentation Object Class Documentation Object Name Current line number Application Component Application Component Name
SIMG GRFN_MAINCUSTMENU 0 GR11000001 Process Controls 
Maintenance Objects
Maintenance object type C   Customizing Object 
Assigned objects
Customizing Object Object Type Transaction Code Sub-object Do not Summarize Skip Subset Dialog Box Description for multiple selections
VC_GRFNMENUC C - View cluster SM34  
History
Last changed by/on SAP  20100615 
SAP Release Created in 300