screens

[Former Member]

hi professionals,

i have to create one pushbutton namely add while click the add button it add the two input arithmetic value from two input field and display the result into new output field.

i dont know how to create and set the screens for these gui components ,properties,attributes and particularly function code .

plz give the screen shots for all the requirements specified above and send it to the <REMOVED BY MODERATOR>

if i am satisfied .

<REMOVED BY MODERATOR>

regards

surender

Edited by: Alvaro Tejada Galindo on Feb 27, 2008 3:19 PM

[Former Member]

hi professionals,

i have to create one pushbutton namely add while click the add button it add the two input arithmetic value from two input field and display the result into new output field.

i dont know how to create and set the screens for these gui components ,properties,attributes and particularly function code .

plz give the screen shots for all the requirements specified above and send it to the <REMOVED BY MODERATOR>

if i am satisfied .

<REMOVED BY MODERATOR>

regards

surender

Edited by: Alvaro Tejada Galindo on Feb 27, 2008 3:19 PM

[Former Member]

Hi,

Screens

Screens are the most general type of user dialog that you can use in ABAP programs. You do not define them in ABAP programs, but instead in the Screen Painter. A screen consists of the input/output mask and the screen flow logic. Screens can be defined for every executable program, every module pool and every function group.

The screens in a single ABAP program can be combined to form screen sequences. You can call single screens or screen sequences either using a transaction code from outside the ABAP program, or by using the CALL SCREEN statement in the corresponding ABAP program. When you call a screen or screen sequence, the screen flow logic takes control of the ABAP program execution. You can define screen sequences dynamically by setting the next screen attribute for a screen dynamically in the ABAP program.

A screen consists of the input/output mask and the flow logic. The screen flow logic is divided into the Process Before Output (PBO) event, which is processed before the screen is displayed, and the Process After Input (PAI) event, which is processed after a user action on the screen.

Check this link for more details.

http://help.sap.com/saphelp_nw70/helpdata/en/e4/2adbef449911d1949c0000e8353423/content.htm

Regards,

Priyanka.

[Former Member]

Hi Surender,

check this two standard reports.

<b>REPORT demo_sel_screen_pushbutton.

REPORT demo_sel_screen_function_key</b>

Understand the logic.

from report 1.

CASE flag.
    WHEN '1'.
      WRITE / 'Button 1 was clicked'.
    WHEN '2'.
      WRITE / 'Button 2 was clicked'.
    WHEN '3'.
      WRITE / 'Button 3 was clicked'.
    WHEN '4'.
      WRITE / 'Button 4 was clicked'.
    WHEN OTHERS.
      WRITE / 'No Button was clicked'.
  ENDCASE.

in place of write statemnt u can use ur logic.

<REMOVED BY MODERATOR>

Regards,

sunil kairam.

Edited by: Alvaro Tejada Galindo on Feb 27, 2008 3:19 PM

[Former Member]

Hi,

selection-screen begin of line.

selection-screen comment 10(15) lb2 for field a.

parameters : a(10).

selection-screen comment 50(15) lb3 for field b.

parameters : b(10).

selection-screen comment (15) lb4.

parameters : c(10).

selection-screen end of line.

selection-screen pushbutton 10(10) LB1 user-command PB1.

initialization.

lb1 = 'PRINT'.

lb2 = 'enter A value'.

lb3 = 'enter B value'.

at SELECTION-SCREEN.

case sy-ucomm.

when 'PB1'.

LEAVE TO LIST-PROCESSING.

write 😕 a, b .

endcase.

Regards,

Priya.