To call subscreen in another screen

hi
How to call a subscreen if i check certain checkbox.please help

Hi,
In screen painter(SE51) choose the subscreen tool button and draw a subscreen area on the screen,this subscreen area will be used to hold the subscreen at run time.To make a subscreen select the attribute screen type as subscreen and specify the size of the subscreen according to the size of the subscreen area in which it will be placed.
We use ABAP statement to embed and start the flow logic of the subscreen area in the PBO of a screen. A subscreen can contain another subscreen.
CALL SUBSCREEN subscreen_area INCLUDING program screen_number.
A similar call should also exist in PAI of screen.It will also call the PAI modules of the subscreen and will transfer data from subscreen to ABAP program.
CALL SUBSCREEN subscreen_area.
open T.code : ABAPDOCU
path:BC ABAP Prg ->ABAP User dialog ->Screen ->Complex screen element - >Subscreen.
You will get sample prg, Run it.You can get lot of sample prg in T.Code ABAPDOCU.
Regards,
Raj.

Similar Messages

Call subscreen from main screen

Dear all,
I have a subscreen and from that subscreen i am calling another normal screen using 'call screen' statement. After doing some manipulation in the normal screen i want to go back to the subscreen on clicking 'BACK' button. i tried 'leave to screen' and 'call screen' in PAI of normal screen but it is not working. how to come back to the subscreen again?
Thanks in advance,
Aswin.

Dear Friend,
You include a subscreen screen using the CALL SUBSCREEN statement in the flow logic of the main screen.
To include a subscreen screen in the subscreen area of the main screen and call its PBO flow logic, use the following statement in the PBO event of the main screen:
This statement assigns the subscreen screen with number <dynp> to the subscreen area called <area>. With <prog> you must specify the ABAP program in which the subscreen screen is defined. If it does not find a corresponding subscreen screen, a runtime error occurs. The PBO flow logic of the subscreen screen is also included at the same point. This can call PBO modules of the ABAP program in which the subscreen screen is defined. At the end of the subscreen PBO, the global fields from the program are passed to any identically-named screen fields in the subscreen screen. The PBO flow logic of the subscreen screen can itself include further subscreens.
The name <area> of the subscreen area must be entered directly without inverted commas. You can specify the names <prog> and <dynp> either as literals or variables. If you use variables, you must declare and fill identically-named variables in the ABAP program. The screen number <dynp> must be 4 characters long. If you do not assign a subscreen screen to an area, it remains empty.
PROCESS BEFORE OUTPUT.
CALL SUBSCREEN <area> INCLUDING <prog> <dynp>.
find the Below Example Code.
DATA: ok_code TYPE sy-ucomm,
      save_ok TYPE sy-ucomm.
DATA: number1(4) TYPE n VALUE '0110',
      number2(4) TYPE n VALUE '0130',
      field(10) TYPE c, field1(10) TYPE c, field2(10) TYPE c.
CALL SCREEN 100.
MODULE status_100 OUTPUT.
SET PF-STATUS 'SCREEN_100'.
ENDMODULE.
MODULE fill_0110 OUTPUT.
field = 'Eingabe 1'(001).
ENDMODULE.
MODULE fill_0120 OUTPUT.
field = field1.
ENDMODULE.
MODULE fill_0130 OUTPUT.
field = 'Eingabe 2'(002).
ENDMODULE.
MODULE fill_0140 OUTPUT.
field = field2.
ENDMODULE.
MODULE cancel INPUT.
LEAVE PROGRAM.
ENDMODULE.
MODULE save_ok INPUT.
save_ok = ok_code.
CLEAR ok_code.
ENDMODULE.
MODULE user_command_0110 INPUT.
IF save_ok = 'OK1'.
    number1 = '0120'.
    field1 = field.
    CLEAR field.
ENDIF.
ENDMODULE.
MODULE user_command_0130 INPUT.
IF save_ok = 'OK2'.
    number2 = '0140'.
    field2 = field.
    CLEAR field.
ENDIF.
ENDMODULE.
MODULE user_command_100 INPUT.
CASE save_ok.
    WHEN 'SUB1'.
      number1 = '0110'.
    WHEN 'SUB2'.
      number1 = '0120'.
      CLEAR field1.
    WHEN 'SUB3'.
      number2 = '0130'.
    WHEN 'SUB4'.
      number2 = '0140'.
      CLEAR field2.
ENDCASE.
ENDMODULE.
The screen flow logic for screen 100 is as follows:
PROCESS BEFORE OUTPUT.
MODULE status_100.
CALL SUBSCREEN: area1 INCLUDING sy-repid number1,
                  area2 INCLUDING sy-repid number2.
PROCESS AFTER INPUT.
MODULE cancel AT EXIT-COMMAND.
MODULE save_ok.
CALL SUBSCREEN: area1,
                  area2.
MODULE user_command_100.
The screen flow logic of subscreen screens 110 and 130 is:
PROCESS BEFORE OUTPUT.
MODULE fill_0110|0130.
PROCESS AFTER INPUT.
MODULE user_command_0110|0130.
The screen flow logic of subscreen screens 120 and 140 is:
PROCESS BEFORE OUTPUT.
MODULE fill_0120|0150.
PROCESS AFTER INPUT.
When you run the program, a screen appears on which subscreens 110 and 130 are displayed. The pushbuttons on the main screen allow you to choose between two subscreen screens for each screen area. The pushbuttons on the subscreens allow you to transfer the data from subscreens 110 and 130 to subscreens 120 and 140.
Since the same field name FIELD is used on all subscreens, the identically-named ABAP field is transferred more than once in each PBO and PAI event of the main screen. For this reason, the values have to be stored in the auxiliary fields FIELD1 and FIELD2 in the ABAP program.
The pushbuttons on the subscreen screens have different function codes, and they are handled normally in an ABAP field. If the function codes had had the same names, it would again have been necessary to use auxiliary fields.

Subscreen with Select-Options called from At Selection Screen event

Dear friends,
I'm trying to call a subscreen that contains a select-options, from an 'at selection screen' event, in a report program, but without sucess.
Here's go what I'm doing:
I declared a selection-screen as subscreen in my main program, and I'm calling it from a module-pool subscreen area, to make the module-pool select-options magic.
In my main report program, I have a customized status GUI with a new toolbar button and I'm handling it at the 'at selection screen' event.
What I need to do is to call the subscreen that contains the select-options when this new customized button get pressed, but when It happens, the select-option selections pop-up doesn't appear.
If I call the subscreen from the 'start-of-selection' event, it goes fine, just don't work from the 'at selection screen'.
Any ideas on how can I do it?
Thank you,
Heber

i think you should try something like this:
at selection screen.
if condition handled ....
show_popup = 'X'.
endif.
at selection screen output.
if show_popup EQ 'X.
call subscreen
endif.

How to call subscreen and provide selection screen in subscreen

Hi experts,
please anybody suggest me how to call subscreen in module pool screen and provide selection screen in that sub screen.
please tell me how to design this subscreen in module pool screen.
adevanced
thank you
regards
vijay krishna

Hi,
If you need to have select-options in module pool then follow these steps:-
To implement select-options in module pool, first design two input/output fields (textboxes) for the low and high value of the field and name it as <field_name>-low and <field_name>-high.
Create a button next the high value textbox and keep its sutaible function code.
Now, to call the pop-up on this button click, we have to call the same pop-up as in standard      select-options. For this we have to use the function module COMPLEX_SELECTIONS_DIALOG.
For this FM we have to pass the table name, field name and the range for the field whose range needs to fill when using the popup screen.
To pass the table name and field name details into the FM, we have to declare as:
DATA : tab TYPE rstabfield.
This structure comprises of table name and field name.
Pass these details in program as:-
u2003
*-- clear table and field details
CLEAR tab.
*-- append for range depending on the button clicked
*   either for sales order or line item
CASE sy-ucomm.
    WHEN 'VBELN'.
      tab-tablename = 'VBAP'.
      tab-fieldname = 'VBELN'.
*--To call the popup screen for the field use code:-
CALL FUNCTION 'COMPLEX_SELECTIONS_DIALOG'
    EXPORTING
      title             = text-002 u201Ctitle text
      text              = ' '
      signed            = 'X'
      search_help       = v_shelp u201Csearch help if required
      tab_and_field     = tab u201Ctable and field name details
    TABLES
      range             = r_vbeln u201Crange for the associated field
    EXCEPTIONS
      no_range_tab      = 1
      cancelled         = 2
      internal_error    = 3
      invalid_fieldname = 4
      OTHERS            = 5.
Hope this helps you.
Regards,
Tarun

How do I pass SELECT-OPTIONS to another screen via CALL TRANSACTION?

Good day, everyone!
I am writing a program that will be passing PARAMETERS and SELECT-OPTIONS values to another transaction via the CALL TRANSACTION statement. I'm new at this, and I've run into a problem. I have several fields that are defined as SELECT-OPTIONS, like so:
SELECT-OPTIONS so_ccode FOR fkkop-bukrs.
The user may select multiple values, enter a range, exclude certain values, etc. -- the things a SELECT-OPTIONS allows.
But how do I pass all of this to a field on another screen using CALL TRANSACTION when I only have two fields (BDCDATA-FNAM and BDCDATA-FVAL) available to me? That works fine for PARAMETERS, but I can send low/high values, different signs/options, etc. for the SELECT-OPTIONS variables.
Please help!! Points awarded for all helpful answers.
Thank you,
Dave

Don't use CALL TRANSACTION. Use SUBMIT instead.
Rob

How to Call another screen using the ABAP Report which is displaying ALV ou

Hello All,
I am developing a ABAP report in which I want to transfer the stock from material to another material.
My Report will include 3 to screens.
The first sleection screen will display all the material with their stock value.
When we execute the report I will get the list of materials along with their current stock. On the top of the output screen I want the Execute button. Also , each line of the output should have checkbox or the ALV provides the functionality of editing one cell like that.....Once the user tick the checkbox or the cell....then I want to move to another screen where user can enter the Quantity and then user will tick ok and then I will call one function module so that the material documnet is posted and transfer of posting form material to material is done successfully.
Could anyone please help me out how to call another screen from the output screen where user can enter the Quantity amount....
I dont want to use the Dialog programming.....I want to create the simple ALV Abap report.
Regards,
Komal Bhutada.

Hi Raymond,
Thanks for the input...I will try this in my code .....
Can you please help me how to insert the checkbox in the ALV Output....so that I can select one of row and then press execute to process further?..
Thanks for the information.
Regards,
Komal.

Probe in calling tabstriped screen from another screen ..

hi
could any one please help me ,,,that what is the logic for calling tabstriped screen from another screen ..
Thanks N Regards
Priya

Hi,
Jonathan.
Thanks for the response ...
I did execute with call screen statement ...(CALL SCREEN 0123). ..when i excute the program its working fine ,but the same programe when I execute with the T.CODE ...its giving erorr ...
ERORR:Program " ZTEST "tried to use screen 000.
        the screen doesn't exist.
HERE IS CODE.
let me know where is the mistake ..
could you please , help me ,,what i suppose to do .
let me know where is the mistake ..
REPORT ZTEST .
DATA: DATE LIKE SY-DATUM,
       TIME LIKE sy-uzeit.
DATA number TYPE sy-dynnr.
CONTROLS tabstrip TYPE TABSTRIP.
tabstrip-activetab = 'TAB1'.
number = '1003'.
tabstrip-activetab = 'TAB2'.
number = '1004'.
CALL SCREEN 1000.
*&      Module STATUS_1000 OUTPUT
      text
MODULE STATUS_1000 OUTPUT.
CASE : SY-UCOMM.
    WHEN 'ENTER'.
      LOOP AT SCREEN.
        IF SCREEN-GROUP1 = 'MOD'.
          DATE = DATE.
          TIME = time.
          SCREEN-INPUT = '0'.
        ENDIF.
        MODIFY SCREEN.
      ENDLOOP.
ENDCASE.
SET PF-STATUS 'xxxxxxxx'.
SET TITLEBAR 'xxx'.
ENDMODULE.                 " STATUS_1000 OUTPUT
*&      Module USER_COMMAND_1000 INPUT
      text
MODULE USER_COMMAND_1000 INPUT.
CASE SY-UCOMM.
    WHEN 'ENTER'.
      LEAVE TO SCREEN 1001.
endcase.
ENDMODULE.                 " USER_COMMAND_1000 INPUT
*&      Module USER_COMMAND_1001 INPUT
      text
MODULE USER_COMMAND_1001 INPUT.
CASE SY-UCOMM.
        WHEN 'button1'.
        CALL SCREEN 1002.
    ENDCASE.
    ENDMODULE.                 " USER_COMMAND_1001 INPUT
*&      Module USER_COMMAND_1002 INPUT
      text
MODULE USER_COMMAND_1002 INPUT.
    CASE sy-ucomm.
      WHEN 'TAB1'.
        number = '1003'.
      WHEN 'TAB2'.
        number = '1004'.
    ENDCASE.
    ENDIF.
ENDMODULE.                 " USER_COMMAND_1002 INPUT
*&      Module STATUS_1002 OUTPUT
      text
MODULE STATUS_1002 OUTPUT.
SET PF-STATUS 'xxxxxxxx'.
SET TITLEBAR 'xxx'.
ENDMODULE.                 " STATUS_1002 OUTPUT
Thanks N Regards.
Priya.

Action link URL calling from another screen from the same web server not work

Hi there,
I have an action link URL calling from another screen from the same web server, used the following syntax:
/analytics/saw.dll?Go&path=.....
But it is not working, when open the page, it shows error message
Oops! Google Chrome could not find analytics
Any help? Thanks!
Ling

That's a +1 from me... same issue and yes, isn't inelegant or a shortcoming for some might be the cause of boldness as they rip their hair off their head so thanks in advance for keeping the refinement of the magic potions making the EA secret magic sauce... which may help stop hairloss
Cheers!
tfbkny

Calling the subscreen into main screen

Hi Guru's,
      I am having a main screen, which holds 2 radio buttons.
      If I select one radio button it has to call one table control, if I select 2nd radio button it has to call different table control.
      For this I have created two subscreens, each one holds a table control.
based on the selection of radio button I have to call these subscreens in to the main screen.
   Please help me how to call the subscreen into main screen.

There is no help text for this dump
Either the text was inadvertently deleted or the release of
the kernel differs from the release of the database
Refer to the Note system for further information on            this dump.
000160           %_archive TYPE arc_params,
000170         END   OF COMMON PART.
000180   *
000190   FIELD-SYMBOLS: <%_1>   %_PREDEFINED.
000200
000210   DATA: %_repid     TYPE syst-repid   %_PREDEFINED,
000220         %_viaselscr TYPE x VALUE '04' %_PREDEFINED.
000230
000240   SYSTEM-EXIT.
000250   PERFORM (sy-xform) IN PROGRAM (sy-xprog).
000260
000270   * Nach Laden des Dynpros
000280   MODULE %_ctl_init OUTPUT.
000290     %_repid = sy-repid.
000300     PERFORM %_ctl_init IN PROGRAM sapmssyd USING %_repid IF FOUND.
     >   ENDMODULE.
000320
000330   * Um DCO
000340   MODULE %_ctl_output OUTPUT.
000350     %_repid = sy-repid.
000360     PERFORM %_ctl_output IN PROGRAM sapmssyd USING %_repid IF FOUND.
000370   ENDMODULE.
000380
000390   * Um DCI
000400   MODULE %_ctl_input INPUT.
000410     %_repid = sy-repid.
000420     PERFORM %_ctl_input IN PROGRAM sapmssyd USING %_repid IF FOUND.
000430   ENDMODULE.
000440
000450   * Erstes Modul in PAI
000460   MODULE %_ctl_pai INPUT.
000470     %_repid = sy-repid.
000480     PERFORM %_ctl_pai IN PROGRAM sapmssyd USING %_repid IF FOUND.
000490   ENDMODULE.

Calling subscreen in module pool

Hi friends,
I am trying to call sub-screen in module pool.
but it is giving me an error as "." or "ID ... FIELD ..." expected after "SUBSCREEN".
i am using followning statement
CALL SUBSCREEN SUB INCLUDING SY-REPID '0101'.
OR
CALL SUBSCREEN SUB. (SUB is screen i have created in layout).
I tried it a lot, but not able to solve it.
Kindly help me.

Hi Kiran,
<li>Subscreen concept is like this. You have one main screen. You want another screen which has to be displayed on main screen when you run main screen.
<li>First we need to create subscreen area on main screen. Goto layout and click subscreen element and place on main screen and name to that subscreen area as SUB.
<li>Now create another screen type subscreen. place fields on that and write logic.
<li> Check REPORT demo_dynpro_subscreens.
Thanks
venkat.O

Steps to create tabstrip for subscreen in selection screen

hi,
can let me know the steps taken to create subscreen in selection screen and put in tabstrip?
i need to have 3 screens. 1000 being the tabstrip, 2000 being first subscreen and 3000 being the second subscreen.
i have the abap code but i do not know the steps to create especially 1000 screen.
for 2000 and 3000, once i activated the program, these 2 screens added but i do not know where can i create the 1000 screen.
also, should i use wizard to create tabstrip?
please advise. thanks
SELECTION-SCREEN BEGIN OF SCREEN 2000 AS SUBSCREEN.        SELECTION-SCREEN BEGIN OF BLOCK x WITH FRAME TITLE text-001.
SELECT-OPTIONS: para1 FOR field1 ,
                              para2 FOR field2.
SELECTION-SCREEN END OF BLOCK x.
SELECTION-SCREEN END OF SCREEN 2000.
SELECTION-SCREEN BEGIN OF SCREEN 3000 AS SUBSCREEN.
SELECTION-SCREEN BEGIN OF BLOCK y WITH FRAME TITLE text-002.
SELECT-OPTIONS: para3 FOR field3 ,
                              para4 FOR field4.
SELECTION-SCREEN END OF BLOCK y.
SELECTION-SCREEN:SKIP.
SELECTION-SCREEN END OF SCREEN 3000.

e_l,
See the total doc.. with example.
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

Call subscreen

Hi
CALL SUBSCREEN is used only in the flow logic but not in the actual program. I want to know the reason why it is not used in the actual program. please help me.
POINTS WILL BE GIVEN.
thanks,
S.Gangi Reddy.

hi,
Subscreens allow you to embed one screen within another at runtime. The term subscreen applies both to the screen that you embed, and the area on the main screen in which you place it. This section is about subscreen areas. The actual screens that you embed are called subscreen screens. When you use a subscreen, the flow logic of the embedded screen is also embedded in the flow logic of the main screen. Using subscreens on screens is like using includes in ABAP programs.
Subscreens are screens which can be embeded into another screen. These can be used and created with both selection screen as well as screen painter.
They differ from normal screens in the way that that they don't have OK_CODE field of ther own and there PBO and PAI transfer data to the ABAP program in which these screens were created and the cannot have module calls which change status or leave screen and module call AT EXIT-COMMAND AND E type function codes.
Subscreens allow you to embed one screen within another at runtime. The term subscreen applies both to the screen that you embed, and the area on the main screen in which you place it. This section is about subscreen areas. The actual screens that you embed are called subscreen screens. When you use a subscreen, the flow logic of the embedded screen is also embedded in the flow logic of the main screen. Using subscreens on screens is like using includes in ABAP programs.
In screen painter(SE51) choose the subscreen tool button and draw a subscreen area on the screen,this subscreen area will be used to hold the subscreen at run time.To make a subscreen select the attribute screen type as subscreen and specify the size of the subscreen according to the size of the subscreen area in which it will be placed.
We use ABAP statement to embed and start the flow logic of the subscreen area in the PBO of a screen. A subscreen can contain another subscreen.
Hope this answers you, Do reward.
Edited by: Runal Singh on Feb 8, 2008 5:36 PM

How to get the alv grid report in another screen when double click on basic

Hi.
I have created an alv report using class cl_gui_alv_grid.I got another report in the same screen,when double clicked on basic list(using double_click event).I want to get this report in another screen.What i have to do?(In classical reports i worked with sy-lsind = 1 ,but how to do here?)
How to set color to the selected rows in the alv grid report?I worked with change_data_from_inside method of cl_gui_alv_grid.But it didn't work out..
With Regards,
Ramana.

On double click event . you will have to call another screen say 9000.
now within screen 900 PBO.. you will have to prepare the fieldcatalog/layout.. and the table to be displayed there.
in PAI of screen 9000, you can return to the original ALV.
method double_click.
call screen 9000.
endmethod.
" now in PBO create a module display_alv2
module display_alv2.
'prepare the fieldcat/layout info for new alv
'add the data to the new ALV table
'instantiate the grid call.. etc
'call the ALV
endmodule
"in PAI
module exit.
case sy-ucomm.
when 'ENT1'.
leave to screen 0.
endcase.
endmodule
while preparing the field catalog you can mention the EMPHASIZE field, whish will give color to tht column
E.g
*--Service Order
    ls_fieldcat-tabname   = 'IT_FINAL_VALID'.
    ls_fieldcat-fieldname = 'AUFNR'.
    ls_fieldcat-scrtext_m = 'Service Order'.
    ls_fieldcat-ref_table = 'AUFK'.
    ls_fieldcat-ref_field = 'AUFNR'.
    ls_fieldcat-col_pos   = 1.
    ls_fieldcat-outputlen = 12.
    ls_fieldcat-emphasize = 'C400'. "This will add color to the cell
    APPEND ls_fieldcat TO fcat_valid.
Hope this helps.

How to move one screen to another screen Webdynpro ?

Hi,
How to move from one screen to another screen Webdypro ?
Best Regards,
Kishore

Hi,
for this you have to declare in and outbound plugs to your views,
bind them into the window area of your component and fire the
outbound plug in your action handler in view one, view2 will be called
automatically.
<a href="http://help.sap.com/saphelp_nw04s/helpdata/en/1f/464941db42f423e10000000a155106/frameset.htm">documentation</a>
grtz
Koen

Calling subscreen on click of radio button

Hi,
I am creating a module pool program , in which on click of a radio butto to 'YES' a subscreen should appear ( on the main screen) with few fields so that the user can input values of it.
But I am having proble in calling the subscreen in PAI event.Actually I think it should be something like this
Module user_command.
case sy-ucomm.
   when rb_yes = 'X'
    { CALL SUBSCRREN CODE
ENDIF.
Can this be done? I f yes how? I only know how to call subscreen in PBO, but the syntax for calling subscrren is different in PAI i think.

Hi,
Try doing this.
This is your flow logic in the main screen to call the Subscreen's PBO
PROCESS BEFORE OUTPUT.
MODULE STATUS_0110.
CALL SUBSCREEN TAB1_REF1 INCLUDING 'ZTRIAL' '0111'.
In the PAI of the main screen,
PROCESS AFTER INPUT.
MODULE USER_COMMAND_0110.
CALL SUBSCREEN TAB1_REF1.
Assign a function code to your radio button.
Layout -> Attributes -> Function Code
In the TOP include,
DATA: v_dynnr type sy-dynnr.
In module USER_COMMAND_0110.
if p_rad = 'X'.
   v_dynnr = '0111'.
else.
v_dynnr = ' '
endif.
You can check this for your reference
[http://help.sap.com/saphelp_nw04/Helpdata/EN/9f/dbabfe35c111d1829f0000e829fbfe/content.htm]

To call subscreen in another screen

Similar Messages

Maybe you are looking for