Ansicht
Dokumentation

ABENDYNPRO_GUI_STATUS_ABEXA - DYNPRO GUI STATUS ABEXA

General Data in Customer Master   ROGBILLS - Synchronize billing plans  
This documentation is copyright by SAP AG.

- GUI Statuses and Function Codes

This example demonstrates how to set the GUI status and evaluate function codes.

Source Code

Execute

Description

The static next dynpro number of dynpro 100 is 100. The screen field of output is defined as not ready for input in Screen Painter. The module init_screen_0100 sets the GUI status status_0100 and the title 100 in the PBO event. All function codes exist as menu entries, but not all of them are assigned to function keys. The function codes in the standard toolbar activate the icons and are automatically assigned to their function keys. Some of the additional function keys are assigned to the application toolbar. The module user_command_0100 first assigns the content of the field ok_code to the helper variable save_ok and initializes ok_code. This procedure is always recommended since it also initializes the dynpro field ok_code again in the PBO event and does not contain any unwanted values. Then the function code chosen is assigned to the field output and displayed in the corresponding screen field, except for BACK, EXIT, and CANCEL. The latter terminates the program. The function code SELE can be passed to the ABAP program in the following ways:

• Choosing Choose in the Edit menu

• Choosing the Choose pushbutton in the application toolbar

• Choosing F2 on the keyboard

• Pressing the right mouse button and choosing Choose

• Double-clicking the screen field of output

• Entering SELE in the command field and choosing ENTER

The other function codes are passed in accordance with their definition, but without a double-click.

BAL Application Log Documentation   rdisp/max_wprun_time - Maximum work process run time  
This documentation is copyright by SAP AG.

Length: 2589 Date: 20240426 Time: 083916     sap01-206 ( 50 ms )