Calling GRAPH_ACTION (CNET_GRAPH_ACTION) 

This function module sends additional CUA information to the graphics program.

GRAPH_ACTION is not available for SAP Business Graphics and SAP Structural Graphics.

You can define additional CUA items as follows:

  1. Call GRAPH_ACTION (or CNET_GRAPH_ACTION for SAP Network Graphics) with the desired CUA information.
  2. Call the function module for the graphics program running in the window to be extended.

Your call to this function module must request a screen refresh (with STAT='3' or '5') in order to display the new CUA items in the window.

When using GRAPH_ACTION: The ABAP program should ensure that no calls to other graphics programs intervene between the call to GRAPH_ACTION and the call to the graphics program for the window being extended. If another call does intervene, the CUA buttons will appear in the wrong window.

For example, if you want to extend an SAP Statistics window with CUA items, but call GRAPH_GANTT before the statistics function module, the items will appear in the GANTT window.

An exception to the above rule is SAP Business Graphics, which does not respond to the CUA information. You can call as many BUSG function modules as you like without causing the button information to be deleted from static storage. (Note, however, that this may change in future releases.)

When using CNET_GRAPH_ACTION: Only SAP Network Editor function modules react to CUA information registered with CNET_GRAPH_ACTION. No function calls to other graphics programs will interfere.

In general: You may call GRAPH_ACTION or CNET_GRAPH_ACTION to update a new window or one that is already open. CUA items can be added or changed anytime you call a function module for that graphics program. If you have multiple windows open for a single graphics program, only the very next window updated is affected.

GRAPH_ACTION and CNET_GRAPH_ACTION use the same parameters. The following table contains a list of these parameters.

For a detailed description of parameters and exceptions, see the R/3 system documentation (Tools ® ABAP Workbench, Function library button, or transaction code SE37).

Parameters used with GRAPH_ACTION and CNET_GRAPH_ACTION

Name

Status

Initial Value

ACTBAR

Internal table

  

ACTION

Internal table

  

HELP

Internal table

  

These three table parameters do not use any reference tables defined in the ABAP Dictionary. However, your declarations for these parameters must match exactly the structures described in the parameter description.

After Calling GRAPH_ACTION

Graphics function modules called after GRAPH_ACTION report user selection of CUA items in a type parameter (called B_TYP, G_TYP, S_TYP, and so on, depending on the graphics program) and the CUA_ID parameter. If the type parameter contains:

'0': The user selected a menu-entry. CUA_ID contains the contents of the field ACTBAR-<Action-ID>.

'1': The user requested help for a menu-entry. CUA_ID contains the contents of the field ACTBAR-<Help-ID>.

'2': The user clicked on a function key. CUA_ID contains the contents of the field ACTION-<Action-Text>.

After Calling CNET_GRAPH_ACTION

SAP Network Graphics function modules report user selection of CUA items in the GR_MES export parameter.

GR_MES can report back many kinds of user actions, both fixed and variable. (Fixed values are listed in "The SAP Network Graphics Function Modules".) If GR_MES contains anything other than one of the fixed values, it must be one of the CUA-related values declared when calling CNET_GRAPH_ACTION. The CUA-related values are those found in the parameter fields:

ACTBAR-<Action-ID>

ACTBAR-<Help-ID>

ACTION-<Action-Text>