Hi
All Tabstribs use the same subarea SUB (see the dynpro 100), in PBO it needs to indicate the program and subscreen number have to be loaded in that subarea.
In PBO of screen 100 you can see the line:
CALL SUBSCREEN SUB INCLUDING SY-REPID NUMBER.
The variable NUMBER is managed in the USER_COMMAND:
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.
But this module is triggered as soon as you press a button on screen 100 (you have to considere the label of tabstrip is a pushbutton),
so it needs to initialize the variable NUMBER for the first time screen 100 is called, that mean it needs to indicate which is the first tab has to be shown at the beginning, so you have the code:
mytabstrip-activetab = 'PUSH2'.
number = '0120'.
CALL SCREEN 100.
The same code can be included in the PBO in the following way:
PROCESS BEFORE OUTPUT.
MODULE STATUS_0100.
MODULE INIT_TABSTRIP. "<--- New Module
CALL SUBSCREEN SUB INCLUDING SY-REPID NUMBER.
PROCESS AFTER INPUT.
MODULE CANCEL AT EXIT-COMMAND.
CALL SUBSCREEN SUB.
MODULE USER_COMMAND.
MODULE INIT_TABSTRIP.
IF NUMBER IS INITIAL.
mytabstrip-activetab = 'PUSH2'.
number = '0120'.
ENDIF.
ENDMODULE.
The line:
mytabstrip-activetab = 'PUSH2'.
is to indicate which tabstrip has to be placed in foreground (remember every tabstrip is a pushbutton, so every tabstrip has an own ok_code)
Max
Bluesky
