Application Development and Automation Discussions
Join the discussions or start your own on all things application development, including tools and APIs, programming models, and keeping your skills sharp.
cancel
Showing results for 
Search instead for 
Did you mean: 
Read only

Error in Screen program

Former Member
0 Likes
532

Error:Screen !TABSTRIP 0110 must be an include screen(screen error)

code:

CONTROLS TABSTRIP TYPE TABSTRIP.

CALL SCREEN 100.

CALL SCREEN 110.

CALL SCREEN 130.

PROCESS BEFORE OUTPUT.

MODULE STATUS_0100.

CALL SUBSCREEN SUB1 INCLUDING SY-REPID '0110'.

CALL SUBSCREEN SUB2 INCLUDING SY-REPID '0130'.

PROCESS AFTER INPUT.

MODULE USER_COMMAND_0100.

CALL SUBSCREEN SUB1.

CALL SUBSCREEN SUB2.

I think error is occuring PBO of 100 screen.100 screen layout consits of tabstrip with 2 tabs TAB1 and TAB2.110 screen layout consists of few fields and 130 als with few fields.I dont know why the error is occuring.

Help me please

3 REPLIES 3
Read only

Former Member
0 Likes
495

hi Gopi,

I understand your main screen is 100 and it contains two subscreens 110 and 130. One for each tab.

Ensure you have set screen 110 and 130 as "Subscreens" in type of screen in attribute.

Also, in the flow logic of screen 100 - you should not put the code

CONTROLS TABSTRIP TYPE TABSTRIP.

CALL SCREEN 100.

CALL SCREEN 110.

CALL SCREEN 130.

It should be something like:

PROCESS BEFORE OUTPUT.

MODULE STATUS_0100.

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

SUB2 INCLUDING SY-REPID '0130'.

PROCESS AFTER INPUT.

MODULE CANCEL AT EXIT-COMMAND.

CALL SUBSCREEN: SUB1,

SUB2.

MODULE USER_COMMAND.

Please have a look at the sample program DEMO_DYNPRO_TABSTRIP_LOCAL to get an idea.

You do not call a subscreen 110 or 130 by CALL SCREEN statement.

Please revert in case of doubt.

Regards,

Aditya

Edited by: Aditya Laud on Jan 16, 2008 8:07 AM

Read only

0 Likes
495

this error is coming, as you said I selected sub screen for 110 and 130

Invalid field format(Screen error)

&----


*& Report ZTABSTRIP *

*& *

&----


*& *

*& *

&----


REPORT ZTABSTRIP .

DATA:NUMBER1 TYPE I,

NUMBER2 TYPE I,

RESULT TYPE I,

N1 TYPE I,

N2 TYPE I,

OK_CODE LIKE SY-UCOMM.

CONTROLS TABSTRIP TYPE TABSTRIP.

CALL SCREEN 100.

CALL SCREEN 110.

CALL SCREEN 130.

&----


*& Module STATUS_0100 OUTPUT

&----


  • text

----


MODULE STATUS_0100 OUTPUT.

  • SET PF-STATUS 'BACK'.

ENDMODULE. " STATUS_0100 OUTPUT

&----


*& Module USER_COMMAND_0100 INPUT

&----


  • text

----


MODULE USER_COMMAND_0100 INPUT.

CASE OK_CODE.

WHEN 'TAB1'.

TABSTRIP-ACTIVETAB = 'TAB1'.

WHEN 'TAB2'.

TABSTRIP-ACTIVETAB = 'TAB2'.

RESULT = NUMBER1 + NUMBER2.

WHEN 'BACK'.

LEAVE PROGRAM.

ENDCASE.

ENDMODULE. " USER_COMMAND_0100 INPUT

&----


*& Module USER_COMMAND_0130 INPUT

&----


  • text

----


MODULE USER_COMMAND_0130 INPUT.

RESULT = NUMBER1 + NUMBER2.

ENDMODULE. " USER_COMMAND_0130 INPUT

&----


*& Module USER_COMMAND_0110 INPUT

&----


  • text

----


MODULE USER_COMMAND_0110 INPUT.

N1 = NUMBER1.

N2 = NUMBER2.

ENDMODULE. " USER_COMMAND_0110 INPUT

&----


*& Module STATUS_0110 OUTPUT

&----


  • text

----


MODULE STATUS_0110 OUTPUT.

  • SET PF-STATUS 'xxxxxxxx'.

  • SET TITLEBAR 'xxx'.

ENDMODULE. " STATUS_0110 OUTPUT

&----


*& Module STATUS_0130 OUTPUT

&----


  • text

----


MODULE STATUS_0130 OUTPUT.

  • SET PF-STATUS 'xxxxxxxx'.

  • SET TITLEBAR 'xxx'.

RESULT = NUMBER1 + NUMBER2.

ENDMODULE. " STATUS_0130 OUTPUT

Read only

0 Likes
495

Hi Gopi,

    You should keep the number1 and number2  text fields as Integer(int2) in screen painter..The error Invalid field format(Screen error) won't come..Try this