Skip to end of metadata
Go to start of metadata

Goto -> SE38 -> Create a Report Program 'ZTEST1'

Writing the name of the GUI status in the program as: SET PF-STATUS <ZTEST1> and double clicking on the
<ZTEST1>, when the system navigates to the menu painter screen for creating a new or for editing an existing one.Then Click 'YES'

Write a short Text and Select the STATUS TYPE "Normal Screen"

create pushbuttons/function codes in the: - Menu Bar, Application Toolbar and provisions for Function key settings.
Dialog Box helps to create a dialog status with provisions for Application Toolbar and Function key settings
The next screen will be as follows:-

Write the Display Standards as FUNCTIONS.

Write the title of an individual option of a menu bar and double click on it.

Write one function code and the text for it and double click on the code
The following screen will appear before U:-

Needless to say, all the icon related information's and tooltip texts are not required for the options
at the menu bar. But , U can fill them if U want to use the same function code(EXIT over here)
in the application toolbar , where it will come with the icon .In that case
U just write the function code at the application toolbar and all the relevant information's come over there

If U want to create a sub options under some option in the menu, proceed as follows:-

Double Click on the SE11.

The below screen will appears.In this screen Choose Text type as 'Static text'.

Enter the function codes and texts over there and proceed as usual.
In the runtime, when U will access the Menu Path:- Functions Dictionary.
Tables, the function code SE11 will be displayed.

Goto -> SE38 write the Following Code, in the START-OF-SELECTION.

Press F8.Then following Screen will appears.

Now, let us create some function codes in the application toolbar:-

Write the function code on the options of Application Toolbar and double click on it:-

Fill in the screen by writing the function text, selecting the icon and tooltip text at the info text.

Goto -> SE38 Press F8.

Setting the GUI Status
To assign a GUI status to a screen, use the ABAP statement
This statement defines the user interface for all subsequent screens of a screen sequence until another is set using a new SET PF-STATUS statement. The GUI status <stat> must be a component of the current ABAP program, unless you use the OF PROGRAM addition in the SET PF-STATUS statement to set a GUI status of another program <prog>.
The EXCLUDING function allows you to change the appearance and function of a GUI status dynamically. This is useful if the individual user interfaces for a range of screens are very similar. You can define a single global status, and then just deactivate the functions you do not need using EXCLUDING. Specify <f> to deactivate the function code stored in field <f>. Specify <itab> to deactivate all function codes stored in the internal table <itab>. Field <f> and the lines of table <itab> should be of type C, and have length 20.
You should set the GUI status for a screen in the PBO event. If you do not specify a GUI status for a screen, it is displayed with the interface of the previous screen. If you do not specify a GUI status for the first screen of a program, it has no user interface, and the user may not be able to leave the screen.
If U are using the GUI status in some executable program , U can catch the function codes in AT USER-COMMAND event , analyzing various function

  • No labels


  1. Unknown User (s9mm13i)

    The presentation was very good and simple to comprehend. I have a question, How does one exclude more than one functionality using the excluding function of SET PF-Status function.

  2. ...EXCLUDING <f>: the <f> can be an internal table: TYPE TABLE OF sy-ucomm. See help for keyword SET PF-STATUS in SAP ABAP for more information.