Special Function Keys and Function Codes

The following text provides information about different special functions on screens.

Reserved Function Keys

The following function keys do not trigger the PAI event, but are reserved for other functions:

• F1 calls the field help
• F4 calls the input help
• F10 positions the cursor on the menu bar

Function Keys for the Standard Toolbar

The following function keys are assigned to icons in the standard toolbar. The function code that you assign and the corresponding ABAP coding should reflect the sense of the icon.

The Enter Key

The ENTER key belongs to the  icon in the standard toolbar. This icon is always active, even if no function is assigned to it in the GUI status, or there is no GUI status set at all. The PAI event is always triggered when the user chooses ENTER. The following function codes can be passed to sy-ucomm or the OK_CODE field:

• Every entry in the command field when you press ENTER.
• If there is no entry in the command field, any function code assigned to the ENTER key in the Menu Painter.
• If the command field does not contain an entry and no function code is assigned to the ENTER key in the Menu Painter, the function code is empty and therefore not passed to sy-ucomm or the OK_CODE field.

The F2 Key

The F2 key is always linked to a mouse double-click. If a function code in the GUI status is assigned to the F2 key, the PAI event can be triggered either when the user chooses F2 or when he or she double-clicks a screen element. In both cases, the corresponding function code is passed to sy-ucomm and the OK_CODE field. If you need to use the cursor position to control what happens next, you must find it out yourself using the GET CURSOR statement.