Subscreen in module pool programming

hello
i want to call to subscreens to subscreen area of main screen dynamically.
i tried using statement under PBO OF MAIN SCREEN flow logic.
call subscreen including '<program name>' variable1'.
i declared all the things in layout as well as in main program.
data............
variable1 type sy-dynnr.
if ( statement).
variable = 'screen number'.
endif.in this way i have three sub screens.
i am not getting any sytatic errors.
but when i execute this . it showing some message.

HI,
CALL SUBSCREEN subscreen_name INCLUDING prog_name dynnr.
where subscreen_name = your subscreen area
prog_name = a variable which holds the name of desired program
dynnr = a variable holding the screen number from the desired program
br

Similar Messages

Getting error while calling a subscreen in module pool program

HI ALL,
 ACTUALLY I'M GETTING A SYNTAX ERROR WHILE I'M CALLING A SUBSCREEN
 IN A MODULE POOL PROGRAM IN PAI MODULE
 THE ERROR IS AS FOLLOW
 "." or "ID ... FIELD ..." expected after "SUBSCREEN"
 CAN ANYBODY PLS HELP ME.
REGARDS
ANDREWS

HI MAX ,
 THE CODE IS AS FOLLOWS:
*& Report ZTABSTRIP_PS
REPORT ZTABSTRIP_PS.
type-pools : vrm.
DATA:number1 type I,
 number2 type I,
 result type I,
 ok_code like SY-UCOMM,
 employee1 type c,
 ABAP(19) type c,
 SALES(19) type c,
 HR(19) type c,
 MM(19) type c,
employee type c.
 emp type c.
CONTROLS tabstrip TYPE TABSTRIP.
CALL SCREEN 100.
call screen 110.
call screen 130.
call screen 120.
call screen 140.
*& Module STATUS_0100 OUTPUT
 text
MODULE STATUS_0100 OUTPUT.
SET PF-STATUS 'STATUS'.
SET TITLEBAR 'TITLE'.
CASE OK_CODE.
 WHEN 'BACK' or 'EXIT' or 'DELETE'.
 leave program.
 WHEN 'SAVE'.
 MESSAGE 'please choose a valid function' TYPE 'I'.
 WHEN 'BACK'.
 leave PROGRAM.
when 'EXIT' or 'DELETE'.
 leave to screen 0.
 WHEN 'SAVE'.
 MESSAGE 'please choose a valid function' TYPE 'I'.
endcase.
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 'TAB3'.
tabstrip-activetab = 'TAB3'.
SET TITLEBAR 'TITLE1'.
when 'TAB4'.
 tabstrip-activetab = 'TAB4'.
 if employee = 'NEERAJ'.
 ABAP = 'NEERAJ'.
 elseif employee = 'UMESH'.
 SALES = 'UMESH'.
 ELSEIF employee = 'RAM'.
 HR = 'RAM'.
 elseif employee = 'ANIL'.
 MM = 'ANIL'.
 endif.
 employee = employee.
WHEN 'BACK'.
 leave PROGRAM.
when 'EXIT' or 'DELETE'.
 leave to screen 0.
 WHEN 'SAVE'.
 MESSAGE 'please choose a valid function' TYPE 'I'.
ENDCASE.
 WHEN 'BACK' or 'EXIT' or 'DELETE'.
 leave program .
 WHEN 'SAVE'.
 MESSAGE 'please choose a valid function' TYPE 'I'.
endcase.
ENDMODULE. " USER_COMMAND_0100 INPUT
*& Module STATUS_0110 OUTPUT
 text
**MODULE STATUS_0110 OUTPUT.
SET PF-STATUS 'STATUS1'.
SET TITLEBAR 'xxx'.
**case ok_code.
**WHEN 'back' or 'exit' or 'delete'.
 leave PROGRAM.
 WHEN 'save'.
 MESSAGE 'please choose a valid function ' TYPE 'W'.
ENDCASE.
**ENDMODULE. " STATUS_0110 OUTPUT
*& Module USER_COMMAND_0110 INPUT
 text
MODULE USER_COMMAND_0110 INPUT.
number1 = number1.
number2 = number2.
CLEAR NUMBER1.
CLEAR NUMBER2.
REFRESH NUMBER1.
REFRESH NUMBER2.
ENDMODULE. " USER_COMMAND_0110 INPUT
*& Module STATUS_0130 OUTPUT
 text
MODULE STATUS_0130 OUTPUT.
SET PF-STATUS 'STATUS2'.
SET TITLEBAR 'xxx'.
RESULT = number1 + number2.
*CLEAR RESULT.
REFRESH RESULT.
ENDMODULE. " STATUS_0130 OUTPUT
*& Module STATUS_0120 OUTPUT
 text
MODULE STATUS_0120 OUTPUT.
SET PF-STATUS 'xxxxxxxx'.
SET TITLEBAR 'xxx'.
DATA: l_name TYPE vrm_id,
 li_list TYPE vrm_values,
 l_value LIKE LINE OF li_list.
l_value-key = '1'.
l_value-text = 'ANIL'.
APPEND l_value TO li_list.
CLEAR l_value.
CLEAR li_list.
l_value-key = '2'.
l_value-text = 'RAM'.
APPEND l_value TO li_list.
CLEAR l_value.
CLEAR li_list.
l_value-key = '3'.
l_value-text = 'NEERAJ'.
APPEND l_value TO li_list.
CLEAR l_value.
CLEAR li_list.
l_value-key = '4'.
l_value-text = 'UMESH'.
APPEND l_value TO li_list.
CLEAR l_value.
CLEAR li_list.
l_name = 'employee'.
CALL FUNCTION 'VRM_SET_VALUES'
 EXPORTING
 ID = l_name
 VALUES = li_list
 EXCEPTIONS
 ID_ILLEGAL_NAME = 1
 OTHERS = 2
IF SY-SUBRC <> 0.
MESSAGE ID SY-MSGID TYPE SY-MSGTY NUMBER SY-MSGNO
 WITH SY-MSGV1 SY-MSGV2 SY-MSGV3 SY-MSGV4.
ENDIF.
CLEAR li_list.
ENDMODULE. " STATUS_0120 OUTPUT
*& Module USER_COMMAND_0120 INPUT
 text
MODULE USER_COMMAND_0120 INPUT.
INCLUDING sy-repid '140'.
employee1 = employee.
IF employee1 CS 'NEERAJ'.
call SUBSCREEN sub4 .
ABAP = 'NEERAJ'.
CLEAR ABAP.
ELSEIF employee1 CS 'UMESH'.
 call SUBSCREEN sub4 .
 SALES = 'UMESH'.
 CLEAR SALES.
elseif employee1 CS 'RAM'.
call SUBSCREEN sub4 .
 HR = 'RAM'.
 CLEAR HR.
ELSEIF employee1 CS 'ANIL'.
 call SUBSCREEN sub4 .
 MM = 'ANIL'.
 CLEAR MM.
 endif.
ENDMODULE. " USER_COMMAND_0120 INPUT
*& Module STATUS_0140 OUTPUT
 text
MODULE STATUS_0140 OUTPUT.
*CASE OK_CODE.
 WHEN employee1 'NEERAJ'.
 screen-active = 1.
 ABAP = 'NEERAJ'.
 WHEN employee1 = 'UMESH'.
 screen-active = 1.
 SALES = 'UMESH'.
 WHEN employee1 = 'RAM'.
 screen-active = 1.
 HR = 'RAM'.
 WHEN employee1 = 'ANIL'.
 screen-active = 1.
 MM = 'ANIL'.
 endif.
*ENDCASE.
ENDMODULE. " STATUS_0140 OUTPUT

Conditional call to a subscreen in module pool program.

Hi,
Could anybody please let me know how i will be able to call a subscreen conditionally in a module pool program?
Example: I have to call a subscreen XXXX if a FLAG = X. How will I achieve this?
I tried to write the below code in PAI
if flag = 'X'.
call subscreen XXXX.
endif.
This produced an error.
Regards,
Smithesh

Hi
In TOP Include
data repid type sy-repid,
dynnr type sy-dynnr.
In PBO of main screen
module status_100. " First Call This Module to provide the SubScreen Number to below Code
call subscreen sub including repid dynnr. " This serves the purpose of calling subscreen based on condition
in Program.
module status_100.
repid = sy-repid.
if your_condition = 'X'. " This also can be implemented in any PAI logi as its purpose is just to pass a value to DYNNR
dynnr = '200'. " The SUB Screen Number you want to pass
else.
dynnr = '300'. " Dummy Sub Screen Screen or any other (Make Sure these are of SUB SCREEN type )
endif.
endmodule
Cheerz
Ram

How to call table control in subscreen in module pool program

Hi all,
I have req,need call table control in subscreen,but have done but when scroll bar value getting changed ,
please guide how to do it.if its possable send the code.
regards
santosh

Hi,
The navigation happens like this.
Consider you have a main screen and 2 subscreens.
When you click or do some event in the Subscreen 2 (lets say this is the one that has the table control), this will first trigger PAI of the Main Screen. In the flow logic of the Main screen, you would have written call subscreen <subscreen area1> and call subscreen <subscreen area2>.
Now the subscreens get triggered based on the order in which you have written in the flow logic.
So, here the modules before the first call subscreen statement in the Main Screen PAI is all executed. Now, it goes to the subscreen on which you have triggered an event and executes the modules in the subscreen.
This is how the execution goes when you have subscreens.
So there is no problem with the navigation. You only have to worry about the screen where you have the table control. Just debug and find where data is getting changed or duplicated.

How to make a fld mandatory in module pool program?

I need help on following 2 things
I have module pool program created, in that many screen subscreens created.
1.I want to make a field mandatory
second one is, I have a general tab and data tab.
General tab screen - 2101
Data tab = 2102
In general tab, I have edited the values (change mode), when change the values and try to save it,
It is holding old value.but If i exucute the transaction once again, it is showing the changed value(new value)
For ex: there is a date field value is 03/08/2009
If I change this to 03/09/2009 and press on Save button from the standard menu, still it is showing the value 03/08/2009. but I execute this transaction once again it is showing the value as 03/09/2009
I will be thankful if someone helps me here

Hi Chitra,
Go to the properties of the filed select program tab and say input required.
then you will get the problem solved.
For second one actually its saving but not displaying the saved value at the same time ,
for this you write the select statement after saving , so that once save is execute m, select statement also will execute and it will display the newly saved value.
so after saving imdeatly u write the select statement.
like case sy-ucomm.
when 'SAVE'.
insert ztable.
select filed from z table.
endcase.
let me know if ur problem solved.
Regards
Rajendra

Need help in module Pool programming.

Dear gurus
I'm stuck in a step of Module Pool program
Steps i used for enhancement in XK01.
1) i appended a structure in table LFA1 having two fields A and B.
2) then i went to IMG-> Logistic -> Business Partner-> Vendor -> Adoption of Customer's Own Master Data Fields -> Prepare     Modification-Free Enhancement of Vendor Master Record ( Here i created my screen group Z1 without Function Code.
3) then i created below module pool program. of screen 9999 and in layout i added to fields to display A and B which i appended.
PROGRAM ZSNAK_XK01.
TABLES: lfa1.
module status_9999 output.
endmodule.                 " status_9999 OUTPUT
module user_command_9999 input.
endmodule.
4) After this i wen to IMG-> Logistic -> Business Partner-> Vendor -> Adoption of Customer's Own Master Data Fields ->
    Business Add-In: Processing of Master Data Enhancements ( Here i created my implementation on method CHECK_ADD_ON_ACTIVE and added this code
if i_screen_group eq 'Z1'.
e_add_on_active = 'X'.
endif.
5) then i went to   IMG-> Logistic -> Business Partner-> Vendor -> Adoption of Customer's Own Master Data Fields ->
   Business Add-In: Customer Subscreens. and created my implementation on method GET_TAXI_SCREEN where i have written this code.
e_screen = '9999'.
e_program = 'ZSNAK_XK01'.
e_headerscreen_layout = ''.
After activation when i execute t-code XK01 i see my button there after INFORMATION BUTTON when i click on it i get following error.
Incorrect screen type: Screen is incorrectly defined or used.
The attribute screen type with the values 'Normal Screen' and
'Subscreen' determines the use of the screen. If a normal screen is used
   as subscreen or vice versa, an error occurs.
The screen "ZSNAK_XK01" 9999 has, in this respect, an inappropriate screen
   type.
Please guide me
Regards
Saad Nisar.

I think you have defined the screen 9999 as normal screen. go to attributes tab of the screen and make it as "subscreen' (radio button) and activate
a®

Select option in module pool program

Hi,
I have develop a module pool program. In one of the screen i need select option. so do any one have idea or approach for it.
Thanks in advance.

Hi,
try the following code
tables : mard.
data : ok_code_100 type sy-ucomm.
selection-screen begin of screen 1010 as subscreen.
selection-screen begin of block b1 with frame title text-001.
select-options: s_werks for mard-werks,
s_lgort for mard-lgort.
parameters : p_var like disvariant-variant.
parameter: p_rb1 radiobutton group rd1 default 'X', " list
p_rb2 radiobutton group rd1. " grid
selection-screen end of block b1.
selection-screen end of screen 1010.
start-of-selection.
CALL SCREEN 100.
*& Module STATUS_0100 OUTPUT
text
module status_0100 output.
set pf-status 'Z11_SUBMIT'.
set titlebar 'CALL'.
endmodule. " STATUS_0100 OUTPUT
*& Module USER_COMMAND_0100 INPUT
text
module user_command_0100 input.
case ok_code_100.
when 'EXIT'.
leave program.
when 'SUBM'.
submit z11_ap_alv_mat using
selection-screen '1000'
with s_plant in s_werks
with s_stor in s_lgort
with p_var = p_var
with p_rb_01 = p_rb1
with p_rb_02 = p_rb2
and return.
endcase.
endmodule. " USER_COMMAND_0100 INPUT
here u have to design a subscreen area SUB_1010 in the screen painter, there is a option given there for that.
and also in the flow logic of screen 0100 you have to call the subscreen SUB_1010 both in PBO and PAI like :
process before output.
module status_0100.
call subscreen sub_1010 including sy-repid '1010'.
process after input.
call subscreen sub_1010.
module user_command_0100.
reward if helpful

Select-options in module pool programming

hi,
I need to have four fields as part of my layout that are select-options fields with multiple values entry options. Since layout doesnt have 'select-options" functionality, i defined it from the module pool program, ie: I wrote a selection screen in the PBO module. The problem is if i make any changes to the code, the layout changes back to the previuos format.
Is there any way in which i can combine selection-screen logic with my layout.
Thanks,
Sruthy

HI
GOOD
Selection Screen Version
Only for Executable Programs
If you do not specify a selection screen version, the system automatically creates a selection screen based on the selection criteria of the logical database and the parameters and select-options statements in the program.
If you want to use a different selection screen of the logical database, enter a number in this field. The number must be smaller than 1000 and correspond to an additional selection screen of the logical database. The possible values help displays a list of available selection screens. You can also look in the selection include of the logical database (program DBxxxSEL, where xxx is the name of the logical database).
Tomislav
1. In the top include define the selection screen with
selection-screen begin of screen 9250 as subscreen.
SELECT-OPTIONS analyt FOR ztv_cc02-zd_mumla .
selection-screen end of screen 9250.
2. Using the screen painter create a subscreen area in
the main screen where you want to have this.
3. Then, in the screen flow logic code as follows:
PROCESS BEFORE OUTPUT.
MODULE STATUS_1000. etc
call subscreen SUB1 including 'PROGRAM NAME' '9250'.
PROCESS AFTER INPUT.
module exit at exit-command. etc.
call subscreen SUB1.
THANKS
MRUTYUN

How to create select-options in module pool program

Hi
i am structed at this point could you please tell me
how to create select-options in module pool program

Steps to get SELECT-OPTIONS in module pool programs.
<li>. Start one dialog program with SAPZ_TEST.
<li>. Place the below code in the TOP include of the dialog program.
PROGRAM SAPMZ_TEST.
TABLES mara.
SELECTION-SCREEN BEGIN OF SCREEN 2100 AS SUBSCREEN.
SELECT-OPTIONS: matnr FOR mara-matnr.
SELECTION-SCREEN END OF SCREEN 2100.
<li>. Create one screen 2000 .
<li>. Go to Layout of the screen and Define subscreen area on the screen and Name it as g_subscreen.
<li>. Place the below code in the Flow logic of the screen.
PROCESS BEFORE OUTPUT.
CALL SUBSCREEN g_subscreen INCLUDING 'SAPMZ_TEST' '2100'.
PROCESS AFTER INPUT.
CALL SUBSCREEN g_subscreen.
<li>. Activate all.
<li>. Create Transaction code for the dialog program SAPZ_TEST.
<li>. Execute the transaction code. You will see the select-option like we see on Selection-screen.
I hope that it gets u clear idea.
Thanks
Venkat.O

How to set user command in module pool program

hello expert,
like in report: PARAMETERS: RB_SING RADIOBUTTON GROUP RAD3 DEFAULT 'X' USER-COMMAND C1.
in module pool program, hw to set user-command in screen.
srinivas

PBO.
Call subscreen <SUBSCREEN NAME> Including sy-repid(PROGRAM NAME) G_DYNNR(SCREEN NUMBER'.
PAI
module user_command.
Call subscreen <subscreen name>
Module user_command.
case sy-ucomm.
when 'BUT1'.
g_dynnr = 200.
when 'BUT2'.
g_dynnr = 300.
Endcase.
end module
REPORT demo_dynpro_tabstrip_server.
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.
flow logic of the screen 100
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.
flow logic of the screen 110
PROCESS BEFORE OUTPUT.
PROCESS AFTER INPUT.
flow logic of the screen 120
PROCESS BEFORE OUTPUT.
PROCESS AFTER INPUT.
flow logic of the screen 130
PROCESS BEFORE OUTPUT.
PROCESS AFTER INPUT.
REGARDS
VASU

Problem in Module Pool Program

Hi All,
I got one problem in Module pool program.Im using table control.when selected multiple coloms by table control option left top.
when I want to de-select one by one,unable to de-select. Please suggest me.
thank you,
Anu.

Thank You All.
Solved my self.
The coding as below.
PROCESS BEFORE OUTPUT.
CALL SUBSCREEN SUB INCLUDING SY-REPID '110'.
LOOP AT GT_ITAB INTO WA WITH CONTROL VCONTROL.
    MODULE SET.
    MODULE STATUS_0100.
ENDLOOP.
PROCESS AFTER INPUT.
   CALL SUBSCREEN SUB.
LOOP AT GT_ITAB .
    CHAIN.
      FIELD WA-EBELN.
      FIELD WA-EMATN.
      FIELD WA-EBELP.
      FIELD WA-MATNR.
      FIELD WA-MARK.
      MODULE MODIFY ON CHAIN-REQUEST.
    ENDCHAIN.
ENDLOOP.
    MODULE USER_COMMAND_0100.
MODULE USER_COMMAND_0100 INPUT.
CASE SY-UCOMM.
    WHEN 'SAVE'.
      PERFORM SAVE_VARIANT.
      PERFORM VARIANT_EXISTS.
    WHEN 'SEL'.
      LOOP AT GT_ITAB INTO WA.
        WA-MARK = 'X'.
        MODIFY GT_ITAB FROM WA .
      ENDLOOP.
endmodule.
MODULE STATUS_0100 OUTPUT.
SET PF-STATUS 'ZTESTING'.
SET TITLEBAR 'ZTEST'.
SET PF-STATUS 'ZTESTING' EXCLUDING IT_EXTAB.
MOVE:WA-EBELN TO EKKO-EBELN,
       WA-EBELP TO EKPO-EBELP,
       WA-MATNR TO WA-MATNR.
MOVE:WA-EMATN TO WA-EMATN.
MODIFY GT_ITAB FROM WA INDEX VCONTROL-CURRENT_LINE.
VCONTROL-LINES = SY-DBCNT.
ENDMODULE.                 " STATUS_0100 OUTPUT
MODULE SET OUTPUT.
SET CURSOR FIELD CURSORFIELD OFFSET POS.
ENDMODULE.                 " SET OUTPUT
Thank You,
Anu.

Problem in Select-option in Module Pool Programming

Hi,
I'm making one module pool programming. In that, I've to make select-option. For that I'm using this command --
1) In PBO --
CALL SUBSCREEN sub INCLUDING 'YBOE_PRINT' '5100'.
2) In PAI --
CALL SUBSCREEN sub.
But, Syntax Error is generated as below --
"." or "ID.........FIELD" expected after "SUBSCREEN"
Please suggest.
Thanks.
Kumar Saurav.

Hi Ramchander,
Thanks for replying. But, even if I changed Prog_Name with term 'repid', that same error regarding
"." or "ID ... FIELD ..." expected after "SUBSCREEN"
is coming up.
I guess, there is any step missing.
Lemme describe what I'm doing in points --
1) I declared SELECTION-SCREEN with screen no --
SELECTION-SCREEN BEGIN OF SCREEN 5100 AS SUBSCREEN.
      PARAMETERS : p_bukrs TYPE ekko-bukrs OBLIGATORY DEFAULT '1000'.
      SELECT-OPTIONS: kunnr FOR kna1-kunnr.
      select-options: gjahr for bsid-gjahr.
      select-options: bank for bsed-bank.
      select-options: budat for bsid-budat.
      SELECTION-SCREEN END OF SCREEN 5100.
2) Then I made a call in PBO as given above.
3) Finally, a call to that subscreen is made in PAI - again as given above.
When I checked that, this gave the error.
Are you looking any erroneous step ...?
Please guide.
Thanks.
Kumar Saurav.

How to store the variant in Module Pool Programming

Hi,
I have the module pool program which is having 4 screen. depends on the first and second screen, third screen is called. i want to store the data of third screen to the variant. All the screen except first screen is a subscreen.
Regards,
Dhiraj.

Hi Dhiraj,
You can create a variant only for a Report. Module Pool Programs require a dialog with the user & hence creating a varint is not possible. You can possibly create some Parameter IDs & default values in there.
Regards,
Suresh Datti

No Interval effect in Module Pool Program field

Dear All,
If I want to introduce No Interval effect of the Report Selection screen ,in Module Pool program field,what will be the approach.
Thx in Adv.

Define the selection-screen as a subscreen and call it in the initial screen of ur transaction.
Check this link
http://help.sap.com/saphelp_47x200/helpdata/en/e7/deb237b9a9a968e10000009b38f8cf/content.htm
Also check this demo program
demo_sel_screen_as_subscreen.

Plz provide tutorial to learn the Module pool programing?

Hello,
Please provide me with the Tutorials which will be helpful to learn Module Pool Programming.
If any one can provide me with the screen shots then it would be great!
ANy help would be appreciated......
Thank You!
Krishna Chaitanya

Hi,
Screens are the most general type of user dialog that you can use in ABAP programs. You do not define them in ABAP programs, but instead in the Screen Painter. A screen consists of the input/output mask and the flow logic. You can define screens for any program with type 1, M, or F.
The screens in a single ABAP program can be combined to form screen sequences. You can call single screens or screen sequences either using a transaction code from outside the ABAP program, or by using the CALL SCREEN statement in the corresponding ABAP program. When you call a screen or screen sequence, the screen flow logic takes control of the ABAP program execution. You can define screen sequences dynamically by setting the next screen attribute for a screen dynamically in the ABAP program.
A screen consists of the input/output mask and the flow logic. The screen flow logic is divided into the Process Before Output (PBO) event, which is processed before the screen is displayed, and the Process After Input (PAI) event, which is processed after a user action on the screen.
The following diagram shows the place of screens between the GUI status and the ABAP program:
The screen flow logic calls dialog modules in the ABAP program, either to prepare the screen for display (PBO event) or to process the user's entries (PAI event). Screens are dynamic programs, and have their own data objects, called screen fields. These are linked to the input/output fields that appear on the screen itself. When the screen is displayed, and when it finishes processing, the system passes data between the screen fields and data objects in the ABAP program. Data is copied between identically-named fields.
Each screen has a GUI status, containing a menu bar, standard toolbar, and an application toolbar. Like screens, GUI statuses are independent components of the ABAP program. You create them in the ABAP Workbench using the Menu Painter. You assign GUI statuses to screens dynamically in your ABAP programs. Each screen is linked to the current GUI status by a special screen field into which the corresponding function code is placed whenever the user chooses a function. The screen passes the function code to the ABAP program just like any other screen field. You can then read it in the program.
Screen Attributes
Like all objects in the R/3 Repository, screens have attributes that both describe them and determine how they behave at runtime. Important screen attributes for ABAP programming:
Program
The name of the ABAP program (type 1, M, or F) to which the screen belongs.
Screen number
A four-digit number, unique within the ABAP program, that identifies the screen within the program. If your program contains selection screens, remember that selection screens and Screen Painter screens use the same namespace. For example, if you have a program with a standard selection screen, you may not contain any further screens with the number 1000. Lists, on the other hand, have their own namespace.
Screen type
A normal screen occupies a whole GUI window. Modal dialog boxes only cover a part of a GUI window. Their interface elements are also arranged differently. Selection screens are generated automatically from the definition in the ABAP program. You may not define them using the Screen Painter. A subscreen is a screen that you can display in a subscreen area on a different screen in the same ABAP program.
Next screen
Statically-defined screen number, specifying the next screen in the sequence. If you enter zero or leave the field blank, you define the current screen as the last in the chain. If the next screen is the same as the current screen, the screen will keep on calling itself. You can override the statically-defined next screen in the ABAP program.
Cursor position
Static definition of the screen element on which the cursor is positioned when the screen is displayed. By default, the cursor appears on the first input field. You can overwrite the static cursor position dynamically in your ABAP program.
Screen group
Four-character ID, placed in the system field SY-DYNGR while the screen is being processed. This allows you to assign several screens to a common screen group. You can use this, for example, to modify all of the screens in the group in a uniform way. Screen groups are stored in table TFAWT.
Hold data
If the user calls the screen more than once during a terminal session, he or she can retain changed data as default values by choosing System ® User profile ® Hold data.
Screen Attributes
Like all objects in the R/3 Repository, screens have attributes that both describe them and determine how they behave at runtime. Important screen attributes for ABAP programming:
Program
The name of the ABAP program (type 1, M, or F) to which the screen belongs.
Screen number
A four-digit number, unique within the ABAP program, that identifies the screen within the program. If your program contains selection screens, remember that selection screens and Screen Painter screens use the same namespace. For example, if you have a program with a standard selection screen, you may not contain any further screens with the number 1000. Lists, on the other hand, have their own namespace.
Screen type
A normal screen occupies a whole GUI window. Modal dialog boxes only cover a part of a GUI window. Their interface elements are also arranged differently. Selection screens are generated automatically from the definition in the ABAP program. You may not define them using the Screen Painter. A subscreen is a screen that you can display in a subscreen area on a different screen in the same ABAP program.
Next screen
Statically-defined screen number, specifying the next screen in the sequence. If you enter zero or leave the field blank, you define the current screen as the last in the chain. If the next screen is the same as the current screen, the screen will keep on calling itself. You can override the statically-defined next screen in the ABAP program.
Cursor position
Static definition of the screen element on which the cursor is positioned when the screen is displayed. By default, the cursor appears on the first input field. You can overwrite the static cursor position dynamically in your ABAP program.
Screen group
Four-character ID, placed in the system field SY-DYNGR while the screen is being processed. This allows you to assign several screens to a common screen group. You can use this, for example, to modify all of the screens in the group in a uniform way. Screen groups are stored in table TFAWT.
Hold data
If the user calls the screen more than once during a terminal session, he or she can retain changed data as default values by choosing System ® User profile ® Hold data.
Check the below link:
http://sap.mis.cmich.edu/sap-abap/abap09/index.htm
http://wiki.ittoolbox.com/index.php/FAQ:What_is_module_pool_program_in_abap%3F
http://help.sap.com/saphelp_46c/helpdata/en/35/26b1aaafab52b9e10000009b38f974/content.htm
http://sap.mis.cmich.edu/sap-abap/abap09/sld011.htm
http://sap.mis.cmich.edu/sap-abap/abap09/index.htm
You can also check the transaction ABAPDOCU which gives you lot of sample programs.
Regards
Kiran Sure

Subscreen in module pool programming

Similar Messages

Maybe you are looking for