selection screen

[Former Member]

on my selection screen i have to enter material no. then it should call another screen with tabstrip and table control.

plz tell me how to call a next screen with tab strip and table control in that tab.

[Former Member]

Hi vivek,

For calling the next screen from the first you can just give the next screen number in the attributes.and for the tab strip in the second screen you have to create a tab strip and under each tab,you have to create a subscreen.in that subscreen ,you will have the table control.

you can declare the table control by

• TABLE CONTROL DECLARATIONS

controls tablecontrol1 type tableview using screen '402'.

controls tablecontrol2 type tableview using screen '403'.

to check which tab is active you can use the syntax

if tabstrip1-activetab = 'LINE_ITEMS'.

"necesaary code"

refer this thread,it may be helpful to u.

regards,

sravanthi

[Former Member]

Hi,

You can use the CALL SCREEN <scrn no> statement.

In the blocks of the called screen you can maintain the table control, tabstrip properties. You just need to call it.

Or create a transaction for the screemn you want to call and use CALL TRANSACTION there.

Regards,

Renjith Michael.

http://www.sourceveda.com/

[Former Member]

Vivek ,

By entering the material no. you cannot call any screens.Because no event will get trigger by entering valuse.

IN first screen create input field for material no and

push button.

IN your second screen create tabstrip cpontrol(tcode SE51) and add table control to that tab.

EX: for tabstrip

The screen flow logic for screen 100 is as follows:

PROCESS BEFORE OUTPUT.

MODULE STATUS_0100.

CALL SUBSCREEN: SUB1 INCLUDING SY-REPID '0110',

SUB2 INCLUDING SY-REPID '0120',

SUB3 INCLUDING SY-REPID '0130'.

PROCESS AFTER INPUT.

MODULE CANCEL AT EXIT-COMMAND.

CALL SUBSCREEN: SUB1,

SUB2,

SUB3.

MODULE USER_COMMAND.

The screen flow logic of subscreens 110 to 130 does not contain any module calls.

When you run the program, a screen appears on which the second tab page is active, since the program sets the ACTIVETAB component of the structure MYTABSTRIP to PUSH2 before the screen is displayed. The user can page through the tabstrip control without the PAI event being triggered. One of the three subscreens is included on each tab page.

When the user chooses Continue, the PAI event is triggered, and an information message displays the function code of the tab title of the page that is currently active.

Tabstrip control with paging on the application server.

REPORT DEMO_DYNPRO_TABSTRIP_LOCAL.

CONTROLS MYTABSTRIP TYPE TABSTRIP.

DATA: OK_CODE TYPE SY-UCOMM,

SAVE_OK TYPE SY-UCOMM.

DATA NUMBER TYPE SY-DYNNR.

MYTABSTRIP-ACTIVETAB = 'PUSH2'.

NUMBER = '0120'.

CALL SCREEN 100.

MODULE STATUS_0100 OUTPUT.

SET PF-STATUS 'SCREEN_100'.

ENDMODULE.

MODULE CANCEL INPUT.

LEAVE PROGRAM.

ENDMODULE.

MODULE USER_COMMAND INPUT.

SAVE_OK = OK_CODE.

CLEAR OK_CODE.

IF SAVE_OK = 'OK'.

MESSAGE I888(SABAPDOCU) WITH 'MYTABSTRIP-ACTIVETAB ='

MYTABSTRIP-ACTIVETAB.

ELSE.

MYTABSTRIP-ACTIVETAB = SAVE_OK.

CASE SAVE_OK.

WHEN 'PUSH1'.

NUMBER = '0110'.

WHEN 'PUSH2'.

NUMBER = '0120'.

WHEN 'PUSH3'.

NUMBER = '0130'.

ENDCASE.

ENDIF.

ENDMODULE.

The statically-defined next screen for screen 100 is itself, and its layout is the same as in the above example. However, the function codes of the three tab titles have the function type <blank> and they all share a single subscreen area SUB.

The same subscreen screens 110 to 130 are defined as in the last example.

The screen flow logic for screen 100 is as follows:

PROCESS BEFORE OUTPUT.

MODULE STATUS_0100.

CALL SUBSCREEN SUB INCLUDING SY-REPID NUMBER.

PROCESS AFTER INPUT.

MODULE CANCEL AT EXIT-COMMAND.

CALL SUBSCREEN SUB.

MODULE USER_COMMAND.

In this example, the program includes a subscreen screen in the subscreen area SUB dynamically during the PBO event.

The screen flow logic of subscreens 110 to 130 does not contain any module calls.

This example has the same function as the previous example, but the paging within the tabstrip control is implemented on the application server. Each time the user chooses a tab title, the function code from the OK_CODE field is assigned to the ACTIVETAB component of structure MYTABSTRIP. At the same time, the variable NUMBER is filled with the screen number of the subscreen that has to be displayed in the subscreen area SUB of the tabstrip control.

[Former Member]

but i dont have to do it in module pool i have to do it in selection screen

[Former Member]

Hi,

After selection screen... you may write a START-OF-SELECTION

Inside that you can call the other screen or CALL TRANSACTION

Regards,

Renjith Michael.

http://www.sourceveda.com/

[Former Member]

hi

good

check with CALL SCREEN statement.

thanks

mrutyun^

[Former Member]

plz send me sample code for it

[Former Member]

hi,

IN first screen create input field for material no and

push button.

IN your second screen create tabstrip cpontrol(tcode SE51) and add table control to that tab.

EX: for tabstrip

The screen flow logic for screen 100 is as follows:

PROCESS BEFORE OUTPUT.

MODULE STATUS_0100.

CALL SUBSCREEN: SUB1 INCLUDING SY-REPID '0110',

SUB2 INCLUDING SY-REPID '0120',

SUB3 INCLUDING SY-REPID '0130'.

PROCESS AFTER INPUT.

MODULE CANCEL AT EXIT-COMMAND.

CALL SUBSCREEN: SUB1,

SUB2,

SUB3.

MODULE USER_COMMAND.

The screen flow logic of subscreens 110 to 130 does not contain any module calls.

When you run the program, a screen appears on which the second tab page is active, since the program sets the ACTIVETAB component of the structure MYTABSTRIP to PUSH2 before the screen is displayed. The user can page through the tabstrip control without the PAI event being triggered. One of the three subscreens is included on each tab page.

When the user chooses Continue, the PAI event is triggered, and an information message displays the function code of the tab title of the page that is currently active.

Tabstrip control with paging on the application server.

REPORT DEMO_DYNPRO_TABSTRIP_LOCAL.

CONTROLS MYTABSTRIP TYPE TABSTRIP.

DATA: OK_CODE TYPE SY-UCOMM,

SAVE_OK TYPE SY-UCOMM.

DATA NUMBER TYPE SY-DYNNR.

MYTABSTRIP-ACTIVETAB = 'PUSH2'.

NUMBER = '0120'.

CALL SCREEN 100.

MODULE STATUS_0100 OUTPUT.

SET PF-STATUS 'SCREEN_100'.

ENDMODULE.

MODULE CANCEL INPUT.

LEAVE PROGRAM.

ENDMODULE.

MODULE USER_COMMAND INPUT.

SAVE_OK = OK_CODE.

CLEAR OK_CODE.

IF SAVE_OK = 'OK'.

MESSAGE I888(SABAPDOCU) WITH 'MYTABSTRIP-ACTIVETAB ='

MYTABSTRIP-ACTIVETAB.

ELSE.

MYTABSTRIP-ACTIVETAB = SAVE_OK.

CASE SAVE_OK.

WHEN 'PUSH1'.

NUMBER = '0110'.

WHEN 'PUSH2'.

NUMBER = '0120'.

WHEN 'PUSH3'.

NUMBER = '0130'.

ENDCASE.

ENDIF.

ENDMODULE.

The statically-defined next screen for screen 100 is itself, and its layout is the same as in the above example. However, the function codes of the three tab titles have the function type <blank> and they all share a single subscreen area SUB.

The same subscreen screens 110 to 130 are defined as in the last example.

The screen flow logic for screen 100 is as follows:

PROCESS BEFORE OUTPUT.

MODULE STATUS_0100.

CALL SUBSCREEN SUB INCLUDING SY-REPID NUMBER.

PROCESS AFTER INPUT.

MODULE CANCEL AT EXIT-COMMAND.

CALL SUBSCREEN SUB.

MODULE USER_COMMAND.

In this example, the program includes a subscreen screen in the subscreen area SUB dynamically during the PBO event.

The screen flow logic of subscreens 110 to 130 does not contain any module calls.

This example has the same function as the previous example, but the paging within the tabstrip control is implemented on the application server. Each time the user chooses a tab title, the function code from the OK_CODE field is assigned to the ACTIVETAB component of structure MYTABSTRIP. At the same time, the variable NUMBER is filled with the screen number of the subscreen that has to be displayed in the subscreen area SUB of the tabstrip control.

<REMOVED BY MODERATOR>

GAURAV J.

Edited by: Alvaro Tejada Galindo on Aug 15, 2008 3:37 PM

[Former Member]

Again??...