How to code with tab strip control in se38

HI masters,
      In SE38 i created tab strips with 4 tabs in selection screen. Each selection screen having 4 or 5 input fields.So whenever user click on first screen he will fill the input on that screen, and based on that fields only he will get information. Each tab is totally differ from other tabs, i mean first tab is orders and second is invoice like that. so there is no connection betwen tabs data. Everything is individual tabs.
     I dont know how to code that.Can you plz help me how to code that? Thanks in advance.Its very urgent.

To create a tabstrip control area, choose Tabstrip control from the object list in the Screen Painter and
place it on the screen. Fix the top-left hand corner of the table control area, and then drag the object to
the required size.
Assign a name to the tabstrip control in the Object name attribute. You need this name to identify your
tabstrip control.
In your ABAP program use the CONTROLS statement to declare an object with the same name. Use
TABSTRIP as the type.
The type TABSTRIP is defined in the type pool CXTAB. The field ACTIVETAB contains the function
code of the tab title of the currently active tabstrip. The other fields are reserved for internal use.
The default number of tab pages for a tabstrip control is two.
Technically, tab titles are treated in the same way as pushbuttons. They have a name, a text, a function
code, and a function type. You enter these in the Name, Text, FctCode and FctType fields of the object
attributes.
A tab title can have the function type ' ' (space) or 'P'. If the function type is ' ' (space), the PAI
processing block is triggered when the user chooses that tab, and the function code of the tab title is
placed in the command field. If the function type is 'P', the user can scroll between different tab pages of
the same type without triggering the PAI processing block. For further details, see the following pages.
If you want your tabstrip control to have more than two pages, you must create further tab titles. To do
this, choose Pushbutton from the object list in the Screen Painter and place it in the tab title area.
You must assign a subscreen area to each tab page.
The subscreen area assigned to a tab page is automatically entered as the Reference object (in the
Dictionary attributes) for the tab title of that page.
To assign a subscreen area to one or more tab pages, choose the relevant tab title in the fullscreen
editor, choose the Subscreen object, and place it on the tab page.
Alternatively, you can assign a single subscreen area to several tab pages by entering the name of the
subscreen area directly in the Reference object field of the attributes of the relevant tab pages.
If you have assigned a different subscreen area to each page element in a tabstrip control, you can
scroll between the pages locally at the front end.
To do this, you must send all of the subscreens to the front end when you send the main screen itself. All
of the tab titles in the tabstrip control must also have function type 'P'.
Now, when you scroll between the different page elements, there is no communication between the
presentation server and the application server.
When the user chooses a function on the screen that triggers PAI processing, the system processes the
PAI blocks of all of the subscreens as well. This means that all of the field checks are run. In this
respect, you could regard the tabstrip control as behaving like a single large screen.
Local scrolling in tabstrip controls is more appropriate for display transactions.
<b>Screen Painter:</b>
<b>PROCESS BEFORE OUTPUT.</b>
CALL SUBSCREEN subarea1
INCLUDING SY-CPROG '0101'.
CALL SUBSCREEN subarea2
INCLUDING SY-CPROG '0102'.
CALL SUBSCREEN subarea3
INCLUDING SY-CPROG '0103'.
<b>PROCESS AFTER INPUT.</b>
CALL SUBSCREEN subarea1.
CALL SUBSCREEN subarea2.
CALL SUBSCREEN subarea3.
<b>ABAP:
CONTROLS: my_tab_strip TYPE TABSTRIP.</b>
To program a tabstrip control to scroll locally at the front end, you must:
Assign
a separate subscreen area to each tab page; a subscreen will be sent to each of these
when the screen is processed.
Call
all of the subscreens from the flow logic.
Assign
function code type 'P' to all of the tab titles.
The system hides any page element whose subscreen contains no elements that can be displayed.
If there are no page elements containing elements that can be displayed, the system hides the entire
tabstrip control.
Hope this is helpful, Do reward.

Similar Messages

  • Call report selection screen in module pool program with tab strip control

    Hi,
    Could anyone explain in detail to call report selection screen in module pool program with tab strip control.
    Thanks
    Mano

    Hi,
    Refer std program:
    demo_sel_screen_in_tabstrip.
    demo_sel_screen_with_tabstrip.
    Call your program with SUBMIT stmt form module program.
    Reward points if this Helps.
    Manish

  • Page layout problem when using more than 3 iviews(with Tab Strip controls)

    Hello Experts,
    I am using MS Visual Studio 2005 and PDK 2.5 for .net.
    I have created four iViews where two iViews are having TabStrip control which are dynamically added to iView.
    When I add iViews to the page and view page  ,I am not able to see the content of iViews having TabsStrip controls.
    But I can see contents with individual iView.I am using 3 columns layout for this scenario.
    I have tried all possible layouts available in EP.
    How should I placed iViews in page so that contents of iviews having Tabsrtip control will be displayed.
    Any help appreciated
    Regards
    Sunil Pawar

    Hi Sunil,
              Try changing the isolation property of iView to URL(Isolated) from Embedded-->Save .Now assign these iViews to the page.
    For more info,
    <a href="http://help.sap.com/saphelp_nw04/helpdata/en/97/0be13dc2fd605ae10000000a11405a/content.htm">Isolation Property</a>
    Regards,
    Vinoth.M

  • Help me in tab strip control

    HI,
    CAN ANY ONE GIVE ME THE ADVICE PLEASE URGENT.
    CAN I CREAT TAB STRIP CONTROL AND SUB SCREEN USEING SELECTION-SCREEN?
    first i have to create selection-screen and after entering the values in this and execute i have to generate the tabstrip in sub screen .so help me please.
    do u have example code please send me
    WITH WARM REGARDS.
    KHADAR.

    yes u can create it.
    This is a sample program to create a tabstrip.
    SELECTION-SCREEN BEGIN OF SCREEN 500 AS SUBSCREEN.
    SELECTION-SCREEN BEGIN OF BLOCK b1 WITH FRAME TITLE text-010.
    PARAMETERS: USER(10) TYPE c,
                PWD(10) TYPE c.
    SELECTION-SCREEN END OF BLOCK b1.
    SELECTION-SCREEN END OF SCREEN 500.
    SELECTION-SCREEN BEGIN OF SCREEN 600 AS SUBSCREEN.
    SELECTION-SCREEN BEGIN OF BLOCK b2 WITH FRAME TITLE text-010.
    PARAMETERS: BUSNO(10) TYPE c,
                BUSNAME(10) TYPE c.
    SELECTION-SCREEN END OF BLOCK b2.
    SELECTION-SCREEN END OF SCREEN 600.
    SELECTION-SCREEN BEGIN OF SCREEN 700 AS SUBSCREEN.
    SELECTION-SCREEN BEGIN OF BLOCK b3 WITH FRAME TITLE text-010.
    PARAMETERS: TNO(10) TYPE c,
                TNAME(10) TYPE c.
    SELECTION-SCREEN END OF BLOCK b3.
    SELECTION-SCREEN END OF SCREEN 700.
    SELECTION-SCREEN: BEGIN OF TABBED BLOCK sub FOR 10 LINES,
                        TAB (10) LOGIN USER-COMMAND LOGIN,
                        TAB (10) BUS USER-COMMAND BUS,
                        TAB (10) TRAIN USER-COMMAND TR,
                      END OF BLOCK sub.
    INITIALIZATION.
    LOGIN = 'LOGIN'.
    BUS = 'BUS'.
    TRAIN = 'TRAIN'.
    SUB-DYNNR = 500.
    SUB-PROG = SY-REPID.
    AT SELECTION-SCREEN.
    CASE SY-UCOMM                  .
    WHEN 'LOGIN'.
         SUB-DYNNR = 500.
    WHEN 'BUS'.
         SUB-DYNNR = 600.
    WHEN 'TR'.
         SUB-DYNNR = 700.
    ENDCASE.

  • TABLE CONTROL IN TAB STRIP CONTROL

    hi experts,
    I have a problem with table control in tab strip control  i have table control in first tab
    and some text fields in second tab .
    i enter data into table control in  first tab and enter into second tab and i fill data into second tab also .
    then i press save after filling data into these two tabs  at that time table control data is not updating into corresponding table ,Because when the time  we enter into second tab data in table control is cleared .
    please give me a solution for this problem as early as possible.
    Note  : saving data is done after filling two tabs only.
    Regards,
    k.Rajesh.

    Hi,
    go through this code,
    DIALOG PROGRAMMING
    TABSTRIPS
    IN SE51 FLOW LOGIC MAIN SCREEN
    PROCESS BEFORE OUTPUT.
    CALL SUBSCREEN PER_REF1 INCLUDING 'YMODULE_PR8' '0200'.
    CALL SUBSCREEN SALE_REF1 INCLUDING 'YMODULE_PR8' '0300'.
    MODULE STATUS_0100.
    PROCESS AFTER INPUT.
    MODULE USER_COMMAND_0100.
    IN SE51 FLOW LOGIC FOR SCREEN 200. 1st TAB IN SUBSCREEN AREA.
    PROCESS BEFORE OUTPUT.
    MODULE STATUS_0200.
    PROCESS AFTER INPUT.
    MODULE USER_COMMAND_0200.
    IN SE51 FLOW LOGIC FOR SCREEN 300. 2nd TAB IN SUBSCREEN AREA.
    PROCESS BEFORE OUTPUT.
    LOOP AT ITVBAK WITH CONTROL TABCTRL.
    MODULE STATUS_0300.
    ENDLOOP.
    PROCESS AFTER INPUT.
    MODULE USER_COMMAND_0300.
    LOOP AT ITVBAK.
    ENDLOOP.
    IN FLOW LOGIN OF MAIN SCREEN
    PROGRAM YMODULE_PR8 .
    TABLES : KNA1, VBAK.
    DATA : BEGIN OF ITVBAK OCCURS 0,
           VBELN LIKE VBAK-VBELN,
           ERDAT LIKE VBAK-ERDAT,
           ERNAM LIKE VBAK-ERNAM,
           NETWR LIKE VBAK-NETWR,
           END OF ITVBAK.
    CONTROLS : TABCTRL TYPE TABLEVIEW USING SCREEN 300,
                            TABSTRIP1 TYPE TABSTRIP.
    *&      Module  STATUS_0300  OUTPUT
    MODULE STATUS_0300 OUTPUT.
    SET PF-STATUS 'xxxxxxxx'.
    SET TITLEBAR 'xxx'.
    MOVE-CORRESPONDING ITVBAK TO VBAK.
    ENDMODULE.                 " STATUS_0300  OUTPUT
    *&      Module  USER_COMMAND_0100  INPUT
    MODULE USER_COMMAND_0100 INPUT.
    CASE SY-UCOMM.
      WHEN 'EXIT'.
        LEAVE PROGRAM.
      WHEN 'PERSONAL' OR SPACE.
        SELECT * FROM KNA1
         WHERE KUNNR = KNA1-KUNNR.
        ENDSELECT.
        TABSTRIP1-ACTIVETAB = 'PERSONAL'.  ## TO ACTIVATE TABSTRIP & MAKE IT                                                                               
    FUNCTIONAL
      WHEN 'SALES'.
        SELECT VBELN ERDAT ERNAM NETWR
          FROM VBAK
          INTO TABLE ITVBAK
         WHERE KUNNR = KNA1-KUNNR.
        DESCRIBE TABLE ITVBAK LINES TABCTRL-LINES.
        TABSTRIP1-ACTIVETAB = 'SALES'.  ## TO ACTIVATE TABSTRIP & MAKE IT                                                                               
    FUNCTIONAL
    ENDCASE.
    ENDMODULE.                 " USER_COMMAND_0100
    reward if usefull

  • Creation of Tab Strips controls

    Hi Gy's ,
    pelase help me how to create the Tab Stip control in Sceen Painter(se51) step-by- step procedure.
    Thanks,
    sai.

    hi,
    A tabstrip control is a screen object consisting of two or more pages. Each tab page consists of a tab title and a page area. If the area occupied by the tabstrip control is too narrow to display all of the tab titles, a scrollbar appears, allowing you to reach the titles that are not displayed. There is also a pushbutton that allows you to display a list of all tab titles.
    Tabstrip controls allow you to place a series of screens belonging to an application on a single screen, and to navigate between them easily. The recommended uses and ergonomic considerations for tabstrip controls are described in the Tabstrip Control section of the SAP Style Guide.
    From a technical point of view, a tab page is a subscreen with a pushbutton assigned to it, which is displayed as the tab title.
    The tabstrip control is the set of all the tab pages. Tabstrip controls are therefore subject to the same restrictions as subscreens. In particular, you cannot change the GUI status when you switch between pages in the tabstrip control. However, they are fully integrated into the screen environment, so present no problems with batch input.
    To use a tabstrip control on a screen, you must be using a SAPgui with Release 4.0 or higher, and its operating system must be Motif, Windows 95, MacOS, or Windows NT with version 3.51 or higher.
    When you create a tabstrip control, you must:
    Define the tab area on a screen and the tab titles.
    Assign a subscreen area to each tab title.
    Program the screen flow logic.
    Program the ABAP processing logic.
    You must then decide whether you want to page through the tabstrip control at the SAPgui or on the application server. In the first case, each tab page has its own subscreen. In the second, there is a single subscreen area that is shared by all tab pages.
    Defining the Tabstrip Control Area and Tab Titles
    You define both the tabstrip area and the tab titles in the screen layout.
    The tabstrip area has a unique name and a position, length, and height. You can also specify whether the tabstrip area can be resized vertically or horizontally when the user resizes the window. If the area supports resizing, you can specify a minimum size for it.
    When you define a tabstrip area, it already has two tab titles. Tab titles are technically exactly the same as pushbuttons. To create additional tab titles, simple create pushbuttons in the row containing the tab titles. Tab titles have the same attributes as pushbuttons, that is, each has a name, a text, and a function code. You can also use icons and dynamic texts with tab titles.
    Assigning a Subscreen Area to a Tab Title
    You must assign a subscreen area to each tab title. There are two ways of doing this:
    Paging in the SAPgui
    You need to assign a separate subscreen area to each tab title, and define the function codes of the tab titles with type P (local GUI function). In the screen flow logic, you call all the subscreens in the PBO event. This means that all of the tab pages reside locally on the SAPgui.
    When the user chooses a tab title, paging takes place within the SAPgui. In this respect, the tabstrip control behaves like a single screen. In particular, the PAI event is not triggered when the user chooses a tab title, and no data is transported. While this improves the performance of your tabstrip control, it also has the negative effect that when the user does trigger the PAI event, all of the input checks for all of the subscreens are performed. This means that when the user is working on one tab page, the input checks may jump to an unfilled mandatory field on another page.
    Local paging at the SAPgui is therefore most appropriate for screens that display data rather than for input screens.
    Paging on the Application Server
    One subscreen area is shared by all tab titles and called in the PBO event. You define the function codes of the individual tab titles without a special function type. When the user chooses a tab page, the PAI event is triggered, and you must include a module in your flow logic that activates the appropriate tab page and assigns the correct subscreen to the subscreen area.
    Since the PAI event is triggered each time the user chooses a tab title, this method is less economical for the application server, but the input checks that are performed only affect the current tab page.
    Procedure in Either Case
    You create the subscreen areas within the tabstrip area. You assign the subscreen areas to one or more tab titles in the Screen Painter by selecting one or more titles. You can also assign a subscreen area to a tab title in the tab title attributes by entering the name of the subscreen area in the Reference field attribute.
    The procedure for the alphanumeric Screen Painter is described under Creating Tabstrip Controls.
    If you are paging at the SAPgui, create a subscreen area for each tab title. If you are paging at the application server, select all tab titles and create a single subscreen area. The subscreen areas may not cover the top line of the tab area. However, within a tab area, more than one subscreen area can overlap.
    Programming the Flow Logic
    In the flow logic, all you have to do by hand is include the correct subscreens. The screen flow and data transport to the ABAP program is the same as for normal subscreens. There are two ways of programming the screen flow logic, depending on how you have decided to page through the tabstrip control.
    Paging in the SAPgui
    When you page in the SAPgui, you must include a subscreen for each subscreen area:
    PROCESS BEFORE OUTPUT.
    CALL SUBSCREEN: <area1> INCLUDING <prog 1> <dynp 1>,
    <area2> INCLUDING <prog 2> <dynp 2>,
    <area3> INCLUDING <prog 3> <dynp 3>,
    PROCESS AFTER INPUT.
    CALL SUBSCREEN: <area1>,
    <area2>,
    <area3>,
    Paging on the Application Server
    When you page on the application server, you only have to include a subscreen for the one subscreen area:
    PROCESS BEFORE OUTPUT.
    CALL SUBSCREEN <area> INCLUDING <prog> <dynp>.
    PROCESS AFTER INPUT.
    CALL SUBSCREEN <area>.
    Handling in the ABAP Program
    Before you can use a tabstrip control in your ABAP program, you must create a control for each control in the declaration part of your program using the following statement:
    CONTROLS <ctrl> TYPE TABSTRIP.
    where <ctrl> is the name of the tabstrip area on a screen in the ABAP program. The control allows the ABAP program to work with the tabstrip control. The statement declares a structure with the name <ctrl> . The only component of this structure that you need in your program is called ACTIVETAB.
    Use in the PBO event
    Before the screen is displayed, you use the control to set the tab page that is currently active. To do this, assign the function code of the corresponding tab title to the component ACTIVETAB:
    <ctrl>-ACTIVETAB = <fcode>.
    When you page at the SAPgui, you only need to do this once before the screen is displayed. This initializes the tabstrip control. The default active tab page is the first page. After this, the page activated when the user chooses a tab title is set within SAPgui.
    When you page on the application server, you must assign the active page both before the screen is displayed for the first time, and each time the user pages. At the same time, you must set the required subscreen screen.
    You can suppress a tab page dynamically by setting the ACTIVE field of table SCREEN to 0 for the corresponding tab title.
    Use in the PAI event
    In the PAI event, ACTIVETAB contains the function code of the last active tab title on the screen.
    When you page in the SAPgui, this allows you to find out the page that the user can currently see. When you page at the application server, the active tab page is controlled by the ABAP program anyway.
    The OK_CODE field behaves differently according to the paging method:
    Paging in the SAPgui
    When you page in the SAPgui, the PAI event is not triggered when the user chooses a tab title, and the OK_CODE field is not filled. The OK_CODE field is only filled by user actions in the GUI status or when the user chooses a pushbutton either outside the tabstrip control or on one of the subscreens.
    Paging on the application server
    If you are paging at the application server, the PAI event is triggered when the user chooses a tab title, and the OK_CODE field is filled with the corresponding function code.
    To page through the tabstrip control, you must assign the function code to the ACTIVETAB component of the control:
    <ctrl>-ACTIVETAB = <ok_code>.
    This statement overwrites the function code of the last active tab page with that of the new tab title. At the same time, you must ensure that the correct subscreen is inserted in the subscreen area.
    Otherwise, tabstrip controls are handled like normal subscrens in ABAP programs, that is, the ABAP program of a subscreen screen must contain the dialog modules called from the flow logic of the subscreen.
    Examples
    Tabstrip control, paging at SAPgui
    REPORT DEMO_DYNPRO_TABSTRIP_LOCAL.
    CONTROLS MYTABSTRIP TYPE TABSTRIP.
    DATA: OK_CODE TYPE SY-UCOMM,
    SAVE_OK TYPE SY-UCOMM.
    MYTABSTRIP-ACTIVETAB = 'PUSH2'.
    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.
    ENDIF.
    ENDMODULE.
    The next screen (statically defined) for screen 100 is itself. It has the following layout:
    The screen contains a tabstrip area called MYTABSTRIP with three tab titles PUSH1, PUSH2 and PUSH3. The function codes have the same name, and all have the function type P. One of the subscreen areas SUB1 to SUB3 is assigned to each tab title. The pushbutton has the name BUTTON and the function code ‘OK’.
    In the same ABAP program, there are three subscreen screens 110 to 130. Each of these fits the subscreen area exactly. The layout is:
    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.
    refer the following sites for reference--
    http://www.saptechies.com/difference-bw-tabstrip-and-table-control/
    http://help.sap.com/saphelp_nw04/helpdata/en/9f/dbac1d35c111d1829f0000e829fbfe/content.htm
    Regards,
    sravanthi

  • About the data of table control in tab strip control

    hi experts:
           I use screen 0001 include one tab strip control,and its include two subscreens,one of it is table control(subscreen is 0003).
    I input data in the table control,when I click the button of tab strip control to change to another subscreen 0002.I found that the data I input into table control have not append to internal table.how can I solve this problem?
           appreciate your reply.thanks a lot.

    Hi,
    in the Main Screen
    In PAI
    call subscreen sub. ---> here it calls the subscreen where the tablecontrol is placed
    then call module user_command
    In the subscreen where you have your table control
    in PAI
    Loop at itab.
    module modify_tab.
    endloop.
    module modify_tab,
    descirbe table itab lines tc-lilnes.
    if tc-lines <= tc-current_line.
    modify itab index tc-current_lilne.
    else.
    append itab.
    endmodule.
    next you call the module user_command on the main screen
    module user_command
    case sy-ucomm
    WHEN 'TAB1'
    TS-ACTIVE_TAB = 'TAB1'
    when tab2.
    ts-active_tab = 'TAB2'.
    endmodule
    further you can take the help of CONTROL EXAMPLES in DWDM tcode
    Regards
    Ramchander Rao.K

  • Does tab strip control work in LSMW

    does tab strip control work in LSMW or not if yes give me a scenario

    Yes it does,
    The trick is uto use transaction SHDB to record the transaction that you are trying to use and then convert this to a program. From here you can add the logic into your ABAP.
    Tab strip sontrol also works in LSMW.
    Regards
    Jules

  • About tab strip control

    Could anyone tell me the usage of tab strip controls in REUSE_ALV_GRID_DISPLAY. The IS_LAYOUT has parameters called  dtc_layout type dtc_s_layo. What exactly would be the use of this, if anybody has worked on this?
    Regards,
    Vijay

    Hi Vijay,
    fro better understabding read the FM documentation,
    in that they explained it very well about IS_LAYOUT.
    IS_LAYOUT
    Output list description structure.
    The parameters are described under the following headers:
    Display options
    Exceptions
    Totals
    Interaction
    Detail screen
    Display variants (only for hierarchical-sequential lists)
    Color
    Other
    Note the section 'Default'.
    Regards
    vijay

  • How to change the Tab Strip name in T-Code CJ20N?

    Dear All,
    I have done one Screen Exit to add 5 additional fields in the T-Code CJ20N using Enhancement CNEX0007.
    I got one extra tab "Cust. enhancement" in T-Code CJ20N.
    Now my requirement is that the name of the Tab Strip "Cust. enhancement" should be changed into "User Tab2".
    Can any one guide me how to do that?
    Thanks & Regards,
    Neeraj

    hi niraj
    how u add fields in cj20n
    please dive me steps
    of that.
    Thanks in advance
    chetan

  • Creation of Tab Strips control

    Hi Guy's,
    Please help me How to create the Tacbstript control in Screen painter(SE51) step-by-step procedure.
    Thanks,
    Sai

    Hi,
      Very good docu....
    Tabstrip Controls
    A tabstrip control is a screen object consisting of two or more pages. Each tab page consists of a tab title and a page area. If the area occupied by the tabstrip control is too narrow to display all of the tab titles, a scrollbar appears, allowing you to reach the titles that are not displayed. There is also a pushbutton that allows you to display a list of all tab titles.
    Tabstrip controls allow you to place a series of screens belonging to an application on a single screen, and to navigate between them easily. The recommended uses and ergonomic considerations for tabstrip controls are described in the Tabstrip Control section of the SAP Style Guide.
    From a technical point of view, a tab page is a subscreen with a pushbutton assigned to it, which is displayed as the tab title.
    The tabstrip control is the set of all the tab pages. Tabstrip controls are therefore subject to the same restrictions as subscreens. In particular, you cannot change the GUI status when you switch between pages in the tabstrip control. However, they are fully integrated into the screen environment, so present no problems with batch input.
    To use a tabstrip control on a screen, you must be using a SAPgui with Release 4.0 or higher, and its operating system must be Motif, Windows 95, MacOS, or Windows NT with version 3.51 or higher.
    When you create a tabstrip control, you must:
    Define the tab area on a screen and the tab titles.
    Assign a subscreen area to each tab title.
    Program the screen flow logic.
    Program the ABAP processing logic.
    You must then decide whether you want to page through the tabstrip control at the SAPgui or on the application server. In the first case, each tab page has its own subscreen. In the second, there is a single subscreen area that is shared by all tab pages.
    Defining the Tabstrip Control Area and Tab Titles
    You define both the tabstrip area and the tab titles in the screen layout.
    The tabstrip area has a unique name and a position, length, and height. You can also specify whether the tabstrip area can be resized vertically or horizontally when the user resizes the window. If the area supports resizing, you can specify a minimum size for it.
    When you define a tabstrip area, it already has two tab titles. Tab titles are technically exactly the same as pushbuttons. To create additional tab titles, simple create pushbuttons in the row containing the tab titles. Tab titles have the same attributes as pushbuttons, that is, each has a name, a text, and a function code. You can also use icons and dynamic texts with tab titles.
    Assigning a Subscreen Area to a Tab Title
    You must assign a subscreen area to each tab title. There are two ways of doing this:
    Paging in the SAPgui
    You need to assign a separate subscreen area to each tab title, and define the function codes of the tab titles with type P (local GUI function). In the screen flow logic, you call all the subscreens in the PBO event. This means that all of the tab pages reside locally on the SAPgui.
    When the user chooses a tab title, paging takes place within the SAPgui. In this respect, the tabstrip control behaves like a single screen. In particular, the PAI event is not triggered when the user chooses a tab title, and no data is transported. While this improves the performance of your tabstrip control, it also has the negative effect that when the user does trigger the PAI event, all of the input checks for all of the subscreens are performed. This means that when the user is working on one tab page, the input checks may jump to an unfilled mandatory field on another page.
    Local paging at the SAPgui is therefore most appropriate for screens that display data rather than for input screens.
    Paging on the Application Server
    One subscreen area is shared by all tab titles and called in the PBO event. You define the function codes of the individual tab titles without a special function type. When the user chooses a tab page, the PAI event is triggered, and you must include a module in your flow logic that activates the appropriate tab page and assigns the correct subscreen to the subscreen area.
    Since the PAI event is triggered each time the user chooses a tab title, this method is less economical for the application server, but the input checks that are performed only affect the current tab page.
    Procedure in Either Case
    You create the subscreen areas within the tabstrip area. You assign the subscreen areas to one or more tab titles in the Screen Painter by selecting one or more titles. You can also assign a subscreen area to a tab title in the tab title attributes by entering the name of the subscreen area in the Reference field attribute.
    The procedure for the alphanumeric Screen Painter is described under Creating Tabstrip Controls.
    If you are paging at the SAPgui, create a subscreen area for each tab title. If you are paging at the application server, select all tab titles and create a single subscreen area. The subscreen areas may not cover the top line of the tab area. However, within a tab area, more than one subscreen area can overlap.
    Programming the Flow Logic
    In the flow logic, all you have to do by hand is include the correct subscreens. The screen flow and data transport to the ABAP program is the same as for normal subscreens. There are two ways of programming the screen flow logic, depending on how you have decided to page through the tabstrip control.
    Paging in the SAPgui
    When you page in the SAPgui, you must include a subscreen for each subscreen area:
    PROCESS BEFORE OUTPUT.
      CALL SUBSCREEN: <area1> INCLUDING [<prog 1>] <dynp 1>,
                      <area2> INCLUDING [<prog 2>] <dynp 2>,
                      <area3> INCLUDING [<prog 3>] <dynp 3>,
    PROCESS AFTER INPUT.
      CALL SUBSCREEN: <area1>,
                      <area2>,
                      <area3>,
    Paging on the Application Server
    When you page on the application server, you only have to include a subscreen for the one subscreen area:
    PROCESS BEFORE OUTPUT.
      CALL SUBSCREEN <area> INCLUDING [<prog>] <dynp>.
    PROCESS AFTER INPUT.
      CALL SUBSCREEN <area>.
    Handling in the ABAP Program
    Before you can use a tabstrip control in your ABAP program, you must create a control for each control in the declaration part of your program using the following statement:
    CONTROLS <ctrl> TYPE TABSTRIP.
    where <ctrl> is the name of the tabstrip area on a screen in the ABAP program. The control allows the ABAP program to work with the tabstrip control. The statement declares a structure with the name <ctrl> . The only component of this structure that you need in your program is called ACTIVETAB.
    Use in the PBO event
    Before the screen is displayed, you use the control to set the tab page that is currently active. To do this, assign the function code of the corresponding tab title to the component ACTIVETAB:
    <ctrl>-ACTIVETAB = <fcode>.
    When you page at the SAPgui, you only need to do this once before the screen is displayed. This initializes the tabstrip control. The default active tab page is the first page. After this, the page activated when the user chooses a tab title is set within SAPgui.
    When you page on the application server, you must assign the active page both before the screen is displayed for the first time, and each time the user pages. At the same time, you must set the required subscreen screen.
    You can suppress a tab page dynamically by setting the ACTIVE field of table SCREEN to 0 for the corresponding tab title.
    Use in the PAI event
    In the PAI event, ACTIVETAB contains the function code of the last active tab title on the screen.
    When you page in the SAPgui, this allows you to find out the page that the user can currently see. When you page at the application server, the active tab page is controlled by the ABAP program anyway.
    The OK_CODE field behaves differently according to the paging method:
    Paging in the SAPgui
    When you page in the SAPgui, the PAI event is not triggered when the user chooses a tab title, and the OK_CODE field is not filled. The OK_CODE field is only filled by user actions in the GUI status or when the user chooses a pushbutton either outside the tabstrip control or on one of the subscreens.
    Paging on the application server
    If you are paging at the application server, the PAI event is triggered when the user chooses a tab title, and the OK_CODE field is filled with the corresponding function code.
    To page through the tabstrip control, you must assign the function code to the ACTIVETAB component of the control:
    <ctrl>-ACTIVETAB = <ok_code>.
    This statement overwrites the function code of the last active tab page with that of the new tab title. At the same time, you must ensure that the correct subscreen is inserted in the subscreen area.
    Otherwise, tabstrip controls are handled like normal subscrens in ABAP programs, that is, the ABAP program of a subscreen screen must contain the dialog modules called from the flow logic of the subscreen.
    Examples
    Tabstrip control, paging at SAPgui
    REPORT DEMO_DYNPRO_TABSTRIP_LOCAL.
    CONTROLS MYTABSTRIP TYPE TABSTRIP.
    DATA: OK_CODE TYPE SY-UCOMM,
          SAVE_OK TYPE SY-UCOMM.
    MYTABSTRIP-ACTIVETAB = 'PUSH2'.
    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.
      ENDIF.
    ENDMODULE.
    The next screen (statically defined) for screen 100 is itself. It has the following layout:
    The screen contains a tabstrip area called MYTABSTRIP with three tab titles PUSH1, PUSH2 and PUSH3. The function codes have the same name, and all have the function type P. One of the subscreen areas SUB1 to SUB3 is assigned to each tab title. The pushbutton has the name BUTTON and the function code ‘OK’.
    In the same ABAP program, there are three subscreen screens 110 to 130. Each of these fits the subscreen area exactly. The layout is:
    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.
    Pls. reward if useful...

  • Problem with tab strip in report programing

    hi,
    I have coded 4 tab strips in a report program.Each tab has some obligatory fields.
    My requirement is user must fill all obligatory fields.
    suppose if I enter values only one tab and execute , its not asking the obligatory fields in other tabs.may be this is the behaviour of tab strips.
    To check the obligatory fields,I  wrote cheks in at selection screen with error message.In this case, suppose I didnt enter values in 2nd tab, the error message is coming under 1st tab screen and I am not able to select the 2nd tab.
    Can any body tells me how to overcome this issu.
    pavan meda

    Hi,
    Check this example..
    Basically you have to check the sy-ucomm not equal to the tab button function code (marked in bold)....
    Note: The only thing is I have to press the second button twice to get to the second tab..But it works..
    SELECTION-SCREEN BEGIN OF TABBED BLOCK tb1 FOR 10 LINES.
    SELECTION-SCREEN TAB (30) tab1  USER-COMMAND tab1  DEFAULT SCREEN 1001.
    SELECTION-SCREEN TAB (30) tab2  USER-COMMAND tab2  DEFAULT SCREEN 1002.
    SELECTION-SCREEN END OF BLOCK tb1.
    SELECTION-SCREEN BEGIN OF SCREEN 1001 AS SUBSCREEN.
    PARAMETERS: p_1 TYPE matnr.
    SELECTION-SCREEN END OF SCREEN 1001.
    SELECTION-SCREEN BEGIN OF SCREEN 1002 AS SUBSCREEN.
    PARAMETERS: p_2 TYPE kunnr.
    SELECTION-SCREEN END OF SCREEN 1002.
    INITIALIZATION.
      tab1 = 'Material'.
      tab2 = 'Customer'.
    AT SELECTION-SCREEN.
    <b>  CHECK sy-ucomm <> 'TAB1' AND sy-ucomm <> 'TAB2'.</b>
      IF p_1 IS INITIAL.
        MESSAGE e000 WITH 'Required entry'.
      ENDIF.
      IF p_2 IS INITIAL.
        MESSAGE e000 WITH 'Required entry'.
      ENDIF.
    START-OF-SELECTION.
      WRITE: / p_1.
      WRITE: / p_2.
    Thanks,
    Naren

  • Reg: How to add new tab strip in MIGO transaction

    Hi Experts,
    I need to add a new tab strip(Inside one selection screen, If the user clicks the new tab strip, New selection screen should populate) in MIGO transaction after pressing enter for the movement type '122'.
    I tried with the BADI MB_MIGO_BADI, Simply i called the module pool program inside that BADI, But it is not giving any solution.
    Please guide me to find the solution for this requirement.
    Regards
    Vijay.R

    Hi,
    You may also try the exits available with the MIGO transaction. To find exits you can use the fillowing code by giving tranasaction code as input.
    REPORT  zrmexitfinder                               .
    TABLES: modsap, modact, tstc.
    PARAMETERS: input1 LIKE tstc-tcode DEFAULT ' ',
                input2 LIKE modsap-typ DEFAULT ' '.
    DATA: search1(6),
          search2(3),
          search3 LIKE modsap-member.
    DATA : first_row VALUE 'Y'.
    CONCATENATE: '%' input1 '%' INTO search1,
    '%' input2 INTO search2.
    SELECT * FROM tstc WHERE tcode LIKE search1.
      first_row = 'Y'.
      CHECK tstc-pgmna NE space.
      CONCATENATE '%' tstc-pgmna '%' INTO search3.
      SELECT * FROM modsap WHERE typ LIKE search2
      AND member LIKE search3.
        SELECT SINGLE * FROM modact WHERE member = modsap-name.
        IF first_row EQ 'Y'.
          WRITE: /0 tstc-tcode, 6 tstc-pgmna, 16 modsap-name, 32 modsap-typ,
                 45 modsap-member, 70 modact-name.
          first_row = 'N'.
        ELSE.
          WRITE: /16 modsap-name, 32 modsap-typ, 45 modsap-member, 70 modact-name.
        ENDIF.
        CLEAR : modsap, modact.
      ENDSELECT.
      IF sy-subrc NE 0.
        WRITE : /0 tstc-tcode, 6 tstc-pgmna, 30 'No exits found'.
      ENDIF.
      CLEAR tstc.
    ENDSELECT.
    END-OF-SELECTION.
      CLEAR: search1, search2, search3.
    Regards,
    Renjith Michael.

  • Navigation is not happening Tab Strip control after execution of PAI

    Hi All,
    I'm facing a problem in my dialog program.
    Here I've a normal screen(200) which contains the tabstrip(3 tabs). Each tab has a subscreen area
    (named header_ref1, line_ref1 and scedule_ref1 respectively).
    screen 200's flow logic:
    PROCESS BEFORE OUTPUT.
      CALL SUBSCREEN header_ref1 INCLUDING sy-repid '0210'.
      CALL SUBSCREEN line_ref1 INCLUDING sy-repid '0220'.
      CALL SUBSCREEN schedule_ref1 INCLUDING sy-repid '0230'.
      MODULE status_0200. "<- Here I've written the logic for changing the tab
    "like when okcode header->first tab,  line ->second tab
    PROCESS AFTER INPUT.
      CALL SUBSCREEN header_ref1.
      CALL SUBSCREEN line_ref1.
      CALL SUBSCREEN schedule_ref1.
      MODULE user_command_0200.
    When I simply navigate between these tabs(without entering anything), its fine and when I enter something in the first/second tab's subscreen and navigate to the other tabs then also navigation is fine.
    But when I enter something in the second tab nad trying to navigate to other tabs its not getting navigated. My second tab contains a table control.
    To summarize, after the PAI execution of second tab navigation is not happening between the tabs
    Helps to solve this problem are highly appreciated.
    thanks in advance.
    Regards,
    Manoj Kumar P
    Edited by: Manoj Kumar on Jun 18, 2009 10:37 AM

    Hi,
    I suggest to do paging not in PBO but in PAI.
    PROCESS AFTER INPUT.
      MODULE change_tab.
    MODULE change_tab. INPUT.
      save_ok = ok_code.
      CLEAR ok_code.
      my_tabstrip-activetab = save_ok.
      CASE save_ok.
        WHEN 'FC_TAB1'.   "<- function code of first tab
          g_dynnr = '0210'.
        WHEN 'FC_TAB2'.    "<- second
          g_dynnr = '0220'.
        WHEN 'FC_TAB3'.    "<- third
          g_dynnr = '0230'.
      ENDCASE.
    ENDMODULE.                  
    If that doens't help, remove your table control and check if that influence paging the tabs. If yes, then it has to be something with this table control i.e. mandatory fields are not filled or similar, which doesn't allow to leave the screen.
    Regards
    Marcin

  • Data not storing in Custom infotype build with tab strips

    Hi All,
    I have created one custom infotype 9030,
    With screen 2000.
    which is having tab strips, I have build the screens refering to p9030-zztest its not storing in database.
    where I am doing wrong...please let me know what should be done in this case.
    Regards
    Satish.v

    Hi,
    Checkout the below link :
    <link to blacklisted site removed by moderator>
    Shailaja Ainala.
    Edited by: Thomas Zloch on Jan 28, 2012 9:06 PM

Maybe you are looking for