topic Dynamic Text on Pushbutton in Application Development and Automation Discussions

Dynamic Text on Pushbutton

Former Member — Mon, 09 Apr 2007 06:15:29 GMT

Hi Experts,

I have created a push button in PF-STATUS being used in a module pool screen..

Now, I want that depending on various conditions, the text on the pushbutton gets changed.e.g. If say condition1 is true, then button text = 'TEST' else button text = 'TEST1'.

Please help me out on how to achieve this.

Points are guaranteed.

Thanks in advance.

Himanshu

Re: Dynamic Text on Pushbutton

athavanraja — Mon, 09 Apr 2007 06:31:19 GMT

check the answer by kesi rahul in this thread

Regards

Raja

Re: Dynamic Text on Pushbutton

Former Member — Mon, 09 Apr 2007 06:44:33 GMT

Hi Aggarwal,

Read this ...... i.e., putting text on the pushbuttons dynamically....

Pushbuttons have a label - the text that you specify statically in the attributes - and can also have icons. If you set the Output field attribute for a pushbutton, you can also set its text dynamically in the ABAP program. To do this, you must create a field in the ABAP program with the same name as the pushbutton. You must then assign the required text to the field before the screen is displayed. You can also assign icons to dynamic texts on pushbuttons by including the icon code in the text. The icon codes are all contained in the include program <ICON>. For example, the ICON_CANCEL () icon has the code @0W@.

In each PAI event, the function code, as long as it is not empty, is placed in the system field SYST-UCOMM (SY-UCOMM) and assigned to the OK_CODE field. Empty function codes are placed in neither the SY-UCOMM field nor the OK_CODE field. The function code of a pushbutton is empty if you have not entered it in the corresponding attribute in the Screen Painter. Before you can work with the OK_CODE field, you must assign a name to it in the Screen Painter. For further information, refer to Reading Function Codes.

The main way of allowing users to choose functions that trigger the PAI event and send function codes to the program is through the GUI status. The main reason is one of space - the GUI status can contain many more functions than you would be able to place on the screen as pushbuttons.

However, you should use pushbuttons in the following cases:

Very important and frequently-used function codes that should appear on the screen as well as in the GUI status, for example, the Execute, Display, and Change functions on the initial screen of the ABAP Editor.

Applications that only use pushbuttons, where function codes in the GUI status make no sense - for example, in a calculator application. The function codes of the corresponding pushbuttons have no corresponding function in the GUI status elements, and only exist as attributes of screen elements.

When you have a GUI status that is used for a large number of screens, but use it on screens that have a particular function that is not required anywhere else. In this case, you should place it on the screen as a pushbutton.

Hope your problem is solved.

Reward if helpful,

Regards,

V.Raghavender.

Re: Dynamic Text on Pushbutton

SantoshKallem — Mon, 09 Apr 2007 06:54:20 GMT

u can achive u r requirement with EXCLUDING

CHECK OUT THIS SAP HELP.

SET PF-STATUS - Screen

Syntax

SET PF-STATUS status [OF PROGRAM prog] [EXCLUDING fcode].

Extras:

1. ... OF PROGRAM prog

2. ... EXCLUDING fcode

Effect:

During screen processing, this statement defines the GUI status defined in status for the subsequent screen layouts. The components of the set status are active in the user interface from the next time a screen layout is sent, and remain active until the end of the program or until the next SET PF-STATUS statement. The name of the current GUI status can be read from the system field sy-pfkey .

For status, a character-type data object must be specified that contains either the name of the GUI status of the main program of the current program group, or the program specified in upper case in prog, or it only contains blank characters. If the status is not available, an empty status is displayed, in which no control elements are active except for the predefined system functions. Of these functions, only the Enter key, to which an empty function code is assigned in this case, triggers the event PAI. If the data object status contains only blank characters, the standard list status is set and the additions have no effect.

Note

If a switch is assigned to an element of the GUI status in the Menu Painter, this controls the activation of this element.

Addition 1

... OF PROGRAM prog

Effect:

By default, a GUI status defined in the current main program is used. The addition OF PROGRAM can be used to set the GUI status of the program specified in prog. A character-type data object that contains the name of the ABAP program in upper case is expected for prog.

Addition 2

... EXCLUDING fcode

Effect:

The addition EXCLUDING can be used to deactivate functions of the set GUI status. An inactive function cannot be selected in the user interface. For fcode, either a character-type data object or an internal table with a flat character-type data type can be specified. The functions, whose function codes are contained in the field or in the rows of the internal table, are deactivated. Only one function code can be specified for each row of the table. The codes are not case-sensitive. Function codes specified in fcode, for which there is no function in the GUI status, are ignored.

Notes:

The GUI status of a screen must be set at the latest during the event PBO. If no GUI status is set for a screen, the empty status described above is used.

If the set GUI status contains dynamic function texts, the function texts are read from the assigned global data objects of the program in which the GUI status is defined. If these do not exist, question marks (?) are displayed. For dynamic function texts, an explicitly specified program prog is loaded into the current program group if it does not already exist in the internal session. This enables access its global data objects.

The statement SET PF-STATUS has a variant for the GUI status of lists.

Example:

Setting the GUI status STATUS_0100 of the main program in a PBO module, whereby the functions with the function codes "CHANGE" and "SAVE" are deactivated.

DATA fcode TYPE TABLE OF sy-ucomm.

...

MODULE status_0100 OUTPUT.

APPEND 'CHANGE' TO fcode.

APPEND 'SAVE' TO fcode.

SET PF-STATUS 'STATUS_0100' EXCLUDING fcode.

ENDMODULE.

REWARD IF USEFUL

REGARDS.

SANTHOSH REDDY

Re: Dynamic Text on Pushbutton

Former Member — Mon, 09 Apr 2007 06:55:34 GMT

I guess it is not possible to change the text dynamically, correct me if I am wrong.

But, I can see a work-around.

Maybe you can have different buttons and based on your logic, may render them visible or invisible.

This can be done by looping at the sceen and setting the invisible attribute corresponding to the field.

For more info:

http://help.sap.com/saphelp_nw2004s/helpdata/en/9f/dbab6f35c111d1829f0000e829fbfe/content.htm

Let me know if it helps.

Regards,

Divya

Re: Dynamic Text on Pushbutton

Former Member — Mon, 09 Apr 2007 06:57:16 GMT

You can all possible Buttons , and you can display them which ever you want according to the condition that has attained using Exclude f code addition.

Regards,

Senthil N S

Re: Dynamic Text on Pushbutton

Former Member — Mon, 09 Apr 2007 07:00:54 GMT

Hi Himnashu,

Declare variabe in your program

data : lv_scr type GUI_DYNTXT.

Step 1:Go to the PF-STATUS button and edit. In the Function attributes, select the push Button 'Change Text Type'. In the 'Dynamic Function text' screen area, do an F4 to get the variable from the program/table where you will set the variable text for the button(In your case lv_scr). Save the PF-STATUS and come out.

Step 2: Before setting the PF-STATUS in the PBO, set the text in the variable you have chosen in step 1 above.

e.g.

if 1 eq 1

lv_scr = 'My New Text'.

else

lv_scr = 'My old text'.

endif.

SET PF-STATUS 'ZPF'.

Re: Dynamic Text on Pushbutton

Former Member — Mon, 09 Apr 2007 07:02:32 GMT

Message was edited by:

Harish K Srivastava