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

Similar Messages

How to copy the module pool program ( Screens, codeing ) ?

Hi guys,
How can I copy the Module pool program to another program including screen and every thing?
can anyone help me....

1. GO TO SE80, and select program from drop down
2. Enter Source Prog Name and press enter
3. Below Object name, right click on the program
4. Select COPY and enter the (New) Target Prog Name
it ll ask for following check box options
-Source
-Text Element
-Documentation
-Variant...etc.
5 Select all and press enter.
Hope this ll be helpful.
Thanks & Regards
Vinsee

How to degub the module pool program

Hi friends,
could anyone tell me "How to degub the module pool program"...!!
Thanks in advance..!!

Hi
Debugging of module pool is same as reports, use /h or put breakpoint
but u shud know what u want to check
there are generally two event used in module pool
PBO
This event is used before displaying the screen,It is used to clear fields table, show table control, tabstrip and most important conditionally modify the scrren .
PAI
is used to validate the fields which are entered on the screen with database values and then fetch records from table.
i mean all values to make available in internal table
now u would be sure which part u want to debug.
Rewards if helpful..............

How to down load the Module pool program from sap

hi friends,
i am having the Module pool program in one server
it consists of 1 screen.
now i want to down load the Module pool program into another server.
those two server are not linked.
is there any way to copy from one server to another server.
like what we do in smartfroms,that is downloading form and uploading the form.

Hi,
You can down load code from source system and u can upload those in your destination system. You can down load Code as normally like execute SE38 > enter ur program name> click on change button> Utilities(in menu bar)->more utilities>upload/down load>down load in source system & Just use same path with upload instead of down load. So this will help u to transfer code from one system to other.
Screens transfer: SE51> enter ur program name & screen no> click on change button> click on Layout button> Utilities(m)>upload/download>download for down loading a screen from source system.
And follow the same procedure in destination system also just use up load instead of download. to upload a screen in destination system.
Hope useful.
Regards,
BBR.

How to give the application server file path in the module pool programming

Hi,
     Could somebody help me how to provide the application server file path in module pool programming once the logo is uploaded to sap system.
For eg I have imported a logo name owens into sap system by using transaction se78; now I need to call the path in the below url,
if container2 is initial.
CREATE OBJECT CONTAINER2
EXPORTING
    CONTAINER_NAME              = 'PICTURE_CONTAINER2'.
CREATE OBJECT PICTURE2
EXPORTING
    PARENT = CONTAINER2.
CALL METHOD PICTURE2->SET_DISPLAY_MODE
EXPORTING
    DISPLAY_MODE = CL_GUI_PICTURE=>display_mode_fit_center
EXCEPTIONS
    ERROR        = 1.
CALL METHOD PICTURE2->LOAD_PICTURE_FROM_URL
EXPORTING
    URL    = " ? "
EXCEPTIONS
    ERROR = 1
    Others = 2.
endif.
Thanks in advance
Deepu

hi Deepu,
Use FM '/SAPDMC/LSM_F4_FRONTEND_FILE' for fetching the data from the application server path/presentation server path
Regards,
Santosh

Data type selection Problem in ztable to use in the Module Pool Program

Dear Experts,
I have created a z-table which is used in Module Pool Program in which i have to save the information saved by the endusers in z-table. But the problem comming is that the amount of information saved by the endusers is so havey & our table is just limited for the 50 characters which is not sufficiet. So I urge you to please tell me what & which type of data type should I have to use to store maximum amount of information in our zt-able which is available in SAP ECC6.0.
Thanks & Regards,
Akg

Dear Akg,
u can resolve ur problem in following ways,
1. You can declare the field in a table without an Data element.
i.e. In the length field . using F4 help in length field how many characters u want u enter.
2. In the same u can search for an standard data element and use the same.
3. Creating an custom data element .
Reward if helps to u!!!
Regards,
MNR

Can we submit the module pool code in background as a job.

Hi All,
Is there any possiblity that, we can capture the module pool program screen element, and run the process in background as a job using the same logic as module pool program.
In other words, can we have any feasible solution to have push button on the transaction screen of a module pool program, after clicking which, it will capture all the screen elements of module pool program and using the same logic of module pool program it will submit a job in background and process the data.
Any hep will be appreciated.
Thanks in adv.
Regard,
Vivek.

Hi Prasenjit,
Thanks for your reply.
My question is, can we use "SUBMIT" statement in module pool program so as it will submit job in backgroung.
The same logic of module pool we will write in executable statement and submit in background using SUBMIT. will this thing is feasible. I am trying the same. Anyways thanks.
Regards,
Vivek

How to get the cursor position from screen in module pool program

Hi,
I am doing the module pool program, I have one table control in one screen.
I have to give functionality to the user that when the user enters first record in the table control and after filling the last field
when he presses enter the cursor will have to come in the starting field of the second record.
I know the logic , but i m bit confused.
Can any body help me to solve this....
thanks

Hi,
Check this code,
Write it in the PBO
MODULE SET_CURSOR_WERTKONTRAKT.
MODULE SET_CURSOR_WERTKONTRAKT OUTPUT.
PERFORM SET_CURSOR USING 'VBAP-ZWERT'.
ENDMODULE.                 " SET_CURSOR_WERTKONTRAKT OUTPUT
FORM SET_CURSOR USING US_FELDNAME.
DATA: DA_TFILL LIKE SY-TFILL.
DESCRIBE TABLE IVBAP LINES DA_TFILL.
FCODE 'Create Position':
==> Cursor to the first free line set to make the new position
Can be created directly
    IF DA_TFILL EQ 0.
      SET CURSOR FIELD US_FELDNAME LINE 1.   -> set cursor position
    ELSE.
      SET CURSOR FIELD US_FELDNAME LINE 2.
    ENDIF.
Product proposal actively
Set ==> cursor in the first row
IF DPP_ACTIVE   EQ CHARX AND
     XVBAP_UMFANG_OPV IS INITIAL.
in the 'target volume' if available
    IF KOPGR_MIT_ZMENG CS TVAK-KOPGR.
        SET CURSOR FIELD 'VBAP-ZMENG' LINE 1.
        EXIT.
    ELSE.
Else in the field 'Order quantity'
      SET CURSOR FIELD 'RV45A-KWMENG' LINE 1.
      EXIT.
    ENDIF.
ENDIF.
Hope it helps you,
Regards,
Abhijit G. Borkar

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

Module pool programming in ECC 6.0 version

Hi All,
Any one can help me how to work on module pool progrmming in 6.0 version,it was completely different to 4.7 version, plz send me some documentation regarding the module pool programming to my mail-id [email protected]

hi,
May be you can search the documentation from this link.
just select ecc 6 from the dropdown menu at the bottom of the page.
http://help.sap.com/search/sap_trex.jsp
Hope this is helpful, Do reward.

Module Pool Programming Guide

Hi,
I have no specific question regarding the module pool program, but want to learn it from beginning.
can anyone help me by sending the Module pool programming material and table control.
Thanks,

Hi
hope it will help you.
reward if help.
Check the below link:
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
http://www.geocities.com/ZSAPcHAT
http://www.allsaplinks.com/files/using_table_in_screen.pdf
http://help.sap.com/saphelp_webas630/helpdata/en/9f/db9cdc35c111d1829f0000e829fbfe/content.htm
http://www.sapdevelopment.co.uk/dialog/dialoghome.htm
http://www.sap-img.com/
http://help.sap.com/saphelp_46c/helpdata/en/08/bef2dadb5311d1ad10080009b0fb56/content.htm
http://www.sapgenie.com/links/abap.htm
http://help.sap.com/saphelp_nw04/helpdata/en/c9/5472fc787f11d194c90000e8353423/frameset.htm
You can also check the transaction ABAPDOCU which gives you lot of sample programs.
Also you can see the below examples...
Go to se38 and give demodynpro and press F4.
YOu will get a list of demo module pool programs.
One more T-Code is ABAPDOCU.
YOu can find more examples there.
See the prgrams:
DEMO_DYNPRO_TABLE_CONTROL_1 Table Control with LOOP Statement
DEMO_DYNPRO_TABLE_CONTROL_2 Table Control with LOOP AT ITAB
http://www.geocities.com/ZSAPcHAT
http://www.allsaplinks.com/files/using_table_in_screen.pdf

How to write module pool program

hai,
what is the module -pool program ?
what are the procedures to write the module-pool program.
plz give the simple program for module-pool programs?
regards
surender

Hi
This component though is not attached to the screen painter, plays important role in transaction. Normally, for reports, on line executable programs are written but for transaction, Module Pool Programs are written. The module pool program contains only modules to handle various events associated with screen and data declaration statements.
System divides the module pool program into several include program. These are global field, PBO modules, and PAI modules. It is entirely users decision whether to use these modules or write directly into main program.
Creation of Module Pool Program
You can create module pool program either through
Object browser
System automatically creates the module pool program and for these program which are created through object browser, system creates the include modules.
Or
ABAP/4 editor
It is similar to normal program creation. Type of program should be given M and is not created by system.
Communication between Dynpro and Module Program
For each screen, the system executes the flow logic, which contains corresponding events. The control is passed to Module Pool Program. Module Pool Program handles the code for these events and again passes back control to the flow logic and finally to screen. Unlike on line program, in this case, the control remains with flow logic. The switching of control between flow logic and module pool program and back is common process when user executes transaction.
Creation of a Complete Transaction
Steps involved to create a complete transaction
 Create module pool program.
 From screen painter create screens.
 Write flow logic for each screen.
 Write code for all the events in module pool program.
 Check for any error in screen and flow logic.
 Generate each and every component of screen i.e. flow logic and screen.
 Single screen can be tested using Screen Painter.
 Create transaction code through object browser.
 Generate the transaction code.
 User can execute the transaction by entering the transaction code in the command field.
Handling Function Code
The function code or OKCODE is the last field of Field list. Function code can be handled as follows:
During the Designing of the screen, a function code is assigned to pushbutton.
 In field list, developer needs to specify OKCODE as last field.
 In module program it is a global field and can be evaluated in the PAI event.
 A function code is treated in the same way, regardless it comes from pushbutton, menu item or any other GUI element.
When the user clicks on the Display button, you want to display details of sflight, with corresponding carrid and connid (which is entered by the user).
Module pool program to handle this particular screen is as follows:
Program YVTEST7.
TABLES: SFLIGHT.
DATA: OKCODE (4).
MODULE INPUT1 INPUT,
CASE OKCODE.
 WHEN DISP.
 SELECT * FROM SFLIGHT
 WHERE CARRID = SFLIGHT CARRID AND
 CONNID = SFLIGHT CONNID.
 ENDSELECT.
 LEAVE TO SCREEN 200.
 WHEN EXIT. LEAVE TO SCREEN 0.
ENDCASE.
ENDMODULE. INPUT1 INPUT
MODULE USER_COMMAND_0200 INPUT.
CASE OKCODE.
WHEN BACK. LEAVE TO SCREEN 100.
ENDCASE.
ENDMODULE. USER_COMMAND_0200 INPUT
When the user clicks on display, control is transferred to screen no. 200 on which you display sflight details & on the same screen, when user clicks on BACK button, he comes back to main screen.
Flow logic for screen 100 is as follows:
PROCESS AFTER INPUT.
MODULE INPUT.
Flow logic for screen 200
PROCESS AFTER INPUT.
USER_COMMAND_0200.
MODULES: Modules are handled in module pool program.
You need to write flow logic for screen 200 and design screen 200.
In case of transaction transfer of data from program to screen is automatic i.e. you need not transfer the data from program to screen explicitly. The fields, which you define in the screen receives the data from program and displays the same.
The Field Checks
As already mentioned Transaction is the only method, which SAP recommends to update the database tables. Data entered in the database table should be valid and correct. Data entered is validated at each and every point. ABAP/4 offers various methods to validate data and those are as follows:
 Automatic field checks
 Checks performed in the flow logic
 Checks performed in the ABAP/4 module pool program
Automatic Field Checks
These checks are based on the field information stored in the dictionary. These checks are performed by the system automatically when the user enters the data for the screen field. System performs these checks before PAI event is triggered. Types of field checks performed by system are as follows:
 Required input
While designing the screen, for particular screen field if you click the Req. Entry checkbox, the field becomes mandatory. When the transaction is executed if user leaves this particular field blank, the system displays error message. User cannot proceed until the user enters some data.
 Proper Data Format
Each field has its own data format whether it is table field or screen field. Whenever data is entered, system checks for the proper format of the data. For example date. Each user has its own format for date, which is defined in the user master record. If the date defined in the user master record is in the format DD/MM/YYYY, if the user enters the date, say, in YY/DD/MM, the user displays the error message. System also checks for the value of month or days. For example if month entered is greater than twelve then the error message is displayed.
 Valid Value for the Field
In data dictionary two tables are related by Primary key-Foreign key relationship. Whenever the user enters the data, the system checks for the check table values. Also in Domain, if you have fixed values, then the system checks for these values.
Automatic field checks are repeated each time the user enters the data.
About at Exit Command
Automatic field checks can be avoided by AT EXIT-COMMAND, which works exactly the same way as Cancel works on application tools bar. In the R/3 screen, if you want to quit the processing of that particular screen without entering the mandatory fields, user can click the Cancel button. Same functionality can be incorporated in the user-defined transaction by using AT EXIT-COMMAND. This module can be called before the system executes the automatic field checks and it goes without saying that before PAI event. Code for AT EXIT-COMMAND in flow logic and in module pool program can be written as follows:
In Flow Logic
Process After Input.
Module exit AT EXIT-COMMAND.
 In module pool program.
Module exit.
Case okcode.
When Exit.
Leave to screen 0.
To achieve this kind of functionality a pushbutton or menu item should be assigned a function type E. It tells the system to process this particular module before carrying out any field checks.
Flow Logic Validations
Consider the case where you want user to enter only LH and SQ for sflight-carrid. In this case, you are restricting value of a screen field. This cannot be achieved by automatic field check. Hence there is a need of additional validation. It can be done in flow logic by using following statement:
Field -
Values
Syntax
PAI.
Field sflight-carrid values (LH).
For multiple values
PAI.
Field sflight-carrid values (LH SQ).
Field sflight-price values (between 1000 and 2000).
In this case when the user enters the value, PAI is triggered and field is checked for that particular value. If the value entered happens to be wrong, that field is enabled for user to enter. If you have multiple Field statements in your flow logic, it is sequential execution.
Consider the following case:
PAI.
Module assign.
Field sflight-carrid values (LH SQ).
In ABAP/4
Module assign.
Data: carrid1 like sflight-carrid.
Carrid1 = sflight-carrid.
Endmodule.
In this case, Sflight-carrid is used in the flow logic before the field statement. The system will give invalid value or some previous value as the field sflight-carrid is used in module before it is checked i.e., field statement is after the module in which sflight-carrid is being used. The field is not available to the system unless it executes the field statement. Field statement transfers the values to the program and is done only once. If you dont have Field statement in your flow logic, transfer of values takes place in PAI event.
Consider one more case where you have multiple field statement
PAI.
Field Sflight-carrid values (LH).
Field Sflight-connid values (0400 0500).
In this case if the user enters only carrid wrong, then this particular field is enabled and rest of the fields are disabled for user to input. Many times if the user enters wrong value for one field, then you might want to give option to user to enter all the fields, which is not possible by using Field statement only. This functionality can be achieved by CHAIN ENDCHAIN.
Syntax
Chain.
Field sflight-carrid value (LH).
 Field sflight-connid values (between 200 and 500).
Endchain.
Field sflight-price values (100 1000).
In this case, if the user enters wrong value only for carrid, both the fields i.e. carrid and connid are enabled as they are grouped together in the Chain statement. The field price will be disabled for input. Usually, logically related fields are grouped together with Chain-Endchain statement.
Module Pool Program Validations
Checking fields ABAP/4 program includes
 Field statement in flow logic.
 Module statement in ABAP/4 module pool Program.
Syntax
PAI.
Field sflight-carrid module <name>.
This module can be handled in the main program i.e. module pool program.
In ABAP/4 program
Module Check.
Select single * from sflight where carrid = sflight-carrid.
If sy-subrc ne 0.
 Message e001.
Endif.
In this case, field sflight-carrid is checked in the table for its existence.
Dynamically Calling the Screens
About Displaying Next Screen
Transaction is a sequence of screens, which are displayed one after the other. The next screen displayed depends upon the attributes of first screen. In attributes you need to give Next Screen number i.e. if next screen displayed should be 200 screen, then this number should be given in next Screen attributes. These are static attributes of the screen. By default, if nothing is specified in the program, the system branches out to the screen number, which is specified in the attribute screen.
In this case, if user selects MARA pushbutton, then fields from Mara table are displayed. When the user clicks on the MARD, then the fields from MARD table are displayed. Depending upon users selection, the screen is branched out and this has to be done during runtime. This functionality can be achieved by dynamically calling the screen in module pool program.
The screen can branch out to new screen depending upon user selection. Following command in module pool program can do this:
 SET SCREEM
 CALL SCREEN
 LEAVE TO SCREEN <NUMBER>
All these commands override the specifications given in the attributes. This overriding is temporary. The values stored in the attribute are not changed.
Set Screen
Syntax
Set screen <number>.
In module pool program
Case okcode.
 When DISP.
 Set screen 200.
 When LIST.
 Set screen 300.
Endcase.
In this case, the entire processing of current screen takes place and then the system branches out to next screen. If you want to branch out to the next screen without processing the current screen, LEAVE SCREEN should be used along with the SET SCREEN.
For Example:
Case okcode..
 When DISP.
 Set screen 200.
 Leave Screen.
 When LIST.
 Set screen 300.
 Leave Screen.
Endcase.
When SET SCREEN is used, control cannot be transferred to the main screen or previous screen, unless you write code for the same.
Call Screen
Usually used for pop up screens. Many times, there is a need for user to enter additional information or secondary information on another screen or pop up screen. Once the user enters the data, he should be able to go back to main screen or to the screen where he started. This is not possible by using SET SCREEN. CALL SCREEN achieves this functionality.
Syntax
Call Screen 200.
Will simply call a screen number 200 from a main screen. Once the screen is displayed the user can enter all the data and return to the main screen by clicking BACK button.
To call screen as pop up screen the syntax is
Call screen starting at <col.no.> <line no>
 Ending at <col no> <line no>.
In this case window will be popped as window and user can close it by using BACK button.
Leave to screen
To SET a new screen without processing current screen, you need to use the following two statements together:
SET SCREEN 200.
LEAVE SCREEN.
Or a Single statement
LEAVE TO SCREEN 200.

How to call a "Z"module pool program in a "z"report

Hi Guys,
I have two reports .
1. Report : uploads a tab delimited " .Txt1" file and update the "z1" table
 ".TXT1" : File contains 4 fields
2. Module pool. :Uploads a a tab delimited " .Txt2" file and update another "z2" table
 ".TXT2" file contains the 4 fileds of ".TXT1" and also 2 extra fields.
I want to merge (call) the module pool program in the Report and perform the upload function using only one ".TXT" file.Please do guide me precisely .
*Report:*
REPORT zrswbgcs009 NO STANDARD PAGE HEADING MESSAGE-ID zwb
 LINE-SIZE 185.
TABLES: zgcs_foc. "FOC Parts Table
*data count buffer
DATA: read_cnt(6) TYPE p, "Find read record
 update_cnt(6) TYPE p, "OK record
 error_cnt(6) TYPE p. "Error record
*file buffer(FOC)
DATA: BEGIN OF FOC_inrec OCCURS 0,
 CUSTOMER(10), "Customer
 PART_CODE(18), "Parts Code
 REF_NO(35), "Ref No.
 REF_DATE(10), "Ref Date
 QTY(12), "Parts Qty
 TEXT(100), "Remark
 END OF FOC_inrec.
*file buffer
DATA: BEGIN OF inrec OCCURS 0,
 CUSTOMER(10), "Customer
 PART_CODE(18), "Parts Code
 REF_NO(35), "Ref No.
 REF_DATE(10), "Ref Date
 QTY(12), "Parts Qty
 PRICE(15), "Parts Price
 WAERK(5), "Parts Currency
 TEXT(100), "Remark
 END OF inrec.
DATA : v_file LIKE rlgrap-filename.
DATA gt_zgcs_foc LIKE zgcs_foc OCCURS 0 WITH HEADER LINE.
DATA gs_zgcs_foc LIKE zgcs_foc.
*File name ACCEPT--------------------------------------------------
SELECTION-SCREEN SKIP 1.
SELECTION-SCREEN BEGIN OF BLOCK b1 WITH FRAME TITLE text-001.
*Company code
PARAMETERS: p_comp LIKE zgcs_imei-company OBLIGATORY.
PARAMETERS: pcfile LIKE rlgrap-filename OBLIGATORY LOWER CASE.
SELECTION-SCREEN BEGIN OF LINE.
SELECTION-SCREEN POSITION 1.
PARAMETERS: HQfile RADIOBUTTON GROUP b2.
SELECTION-SCREEN COMMENT 7(20) text-101 FOR FIELD HQfile.
SELECTION-SCREEN POSITION 31.
PARAMETERS: SUBfile RADIOBUTTON GROUP b2.
SELECTION-SCREEN COMMENT 37(20) text-102 FOR FIELD SUBfile.
SELECTION-SCREEN END OF LINE.
SELECTION-SCREEN END OF BLOCK b1.
SELECTION-SCREEN SKIP 1.
SELECTION-SCREEN BEGIN OF BLOCK box WITH FRAME.
SELECTION-SCREEN: COMMENT /2(40) text-011, COMMENT 42(40) text-001,
 ULINE,
 COMMENT /2(40) text-012, COMMENT 42(40) text-002,
 COMMENT /2(40) text-013, COMMENT 42(40) text-003,
 COMMENT /2(40) text-014, COMMENT 42(40) text-004,
 COMMENT /2(40) text-015, COMMENT 42(40) text-005,
 COMMENT /2(40) text-016, COMMENT 42(40) text-006,
 COMMENT /2(40) text-017, COMMENT 42(40) text-007,
 COMMENT /2(40) text-018, COMMENT 42(40) text-008,
 COMMENT /42(40) text-009.
SELECTION-SCREEN END OF BLOCK box.
* -- AT SELECTION SCREEN ON
AT SELECTION-SCREEN ON VALUE-REQUEST FOR pcfile.
CALL FUNCTION 'WS_FILENAME_GET'
 EXPORTING
 def_filename = space
 def_path = 'C:\'
 mask = ',*.txt,*.TXT.'
 mode = 'O'
 title = ' '
 IMPORTING
 filename = pcfile
 EXCEPTIONS
 inv_winsys = 1
 no_batch = 2
 selection_cancel = 3
 selection_error = 4
 OTHERS = 5.
*-----------------------------start--------------------------------
START-OF-SELECTION.
CLEAR: read_cnt, update_cnt, error_cnt.
REFRESH gt_zgcs_foc. CLEAR gs_zgcs_foc.
PERFORM file_upload_from_pc.
SORT gt_zgcs_foc.
DELETE ADJACENT DUPLICATES FROM gt_zgcs_foc
 COMPARING COMPANY CUSTOMER PART_CODE REF_NO REF_DATE.
*// customer code check
DATA: LT_ZESTD LIKE ZESTD OCCURS 0 WITH HEADER LINE.
IF NOT gt_zgcs_foc[] IS INITIAL.
 SELECT COMPANY CUSTOMER CURRENCY
 INTO CORRESPONDING FIELDS OF TABLE LT_ZESTD
 FROM ZESTD
 FOR ALL ENTRIES IN gt_zgcs_foc
 WHERE COMPANY = gt_zgcs_foc-COMPANY
 AND CUSTOMER = gt_zgcs_foc-CUSTOMER.
ENDIF.
SORT LT_ZESTD BY COMPANY CUSTOMER.
*// part code check
DATA: LT_MARA LIKE MARA OCCURS 0 WITH HEADER LINE.
IF NOT gt_zgcs_foc[] IS INITIAL.
 SELECT *
 INTO TABLE LT_MARA
 FROM MARA
 FOR ALL ENTRIES IN gt_zgcs_foc
 WHERE MATNR = gt_zgcs_foc-PART_CODE.
ENDIF.
SORT LT_MARA BY MATNR.
LOOP AT gt_zgcs_foc.
*// customer code check
 READ TABLE LT_ZESTD WITH KEY
 COMPANY = gt_zgcs_foc-COMPANY
 CUSTOMER = gt_zgcs_foc-CUSTOMER.
 IF SY-SUBRC <> 0.
 WRITE:/'Invalid Customer code ',
 gt_zgcs_foc-COMPANY, ' ',
 gt_zgcs_foc-CUSTOMER.
 STOP.
 ENDIF.
*// part code check
 READ TABLE LT_MARA WITH KEY MATNR = gt_zgcs_foc-PART_CODE
 BINARY SEARCH.
 IF SY-SUBRC <> 0.
 WRITE:/ 'Invalid part code ', gt_zgcs_foc-PART_CODE.
 STOP.
 ENDIF.
*// REF_NO
 TRANSLATE gt_zgcs_foc-REF_NO TO UPPER CASE.
 SHIFT gt_zgcs_foc-REF_NO LEFT DELETING LEADING SPACE.
 IF gt_zgcs_foc-REF_NO = SPACE.
 WRITE:/'Ref No. is blank'.
 STOP.
 ENDIF.
*// REF_DATE
 IF gt_zgcs_foc-REF_DATE = 0.
 WRITE:/'Invalid Ref Date'.
 STOP.
 ENDIF.
*// QTY
* IF gt_zgcs_foc-QTY CO ' 0123456789'.
* ELSE.
* WRITE:/ gt_zgcs_foc-QTY, ' Invalid Qty value'.
* STOP.
* ENDIF.
ENDLOOP.
* Insert/Update table
* MODIFY zgcs_foc FROM TABLE gt_zgcs_foc.
INSERT zgcs_foc FROM TABLE gt_zgcs_foc.
IF sy-subrc EQ 0.
 COMMIT WORK.
 DESCRIBE TABLE gt_zgcs_foc LINES update_cnt.
 error_cnt = read_cnt - update_cnt.
ELSE.
 ROLLBACK WORK.
 error_cnt = read_cnt - update_cnt.
ENDIF.
ULINE.
FORMAT COLOR 3.
WRITE: / 'Read count :', read_cnt.
WRITE: / 'Insert/Update count :', update_cnt.
WRITE: / 'Error count :', error_cnt.
FORMAT COLOR OFF.
*end-of-selection--------------------------------------------------
END-OF-SELECTION.
*& Form FILE_UPLOAD_FROM_PC
FORM file_upload_from_pc.
IF pcfile IS INITIAL.
 WRITE: / 'SELECT UPLOAD FILE !'.
ELSE.
 MOVE pcfile TO v_file.
* HQ file upload
 IF HQfile EQ 'X'.
 CALL FUNCTION 'WS_UPLOAD'
 EXPORTING
 filename = v_file
 filetype = 'DAT'
 TABLES
 data_tab = FOC_inrec
 EXCEPTIONS
 conversion_error = 1
 file_open_error = 2
 file_read_error = 3
 invalid_type = 4
 no_batch = 5
 unknown_error = 6
 invalid_table_width = 7
 gui_refuse_filetransfer = 8
 customer_error = 9
 OTHERS = 10.
 IF sy-subrc <> 0.
 WRITE: / 'FILE UPLOAD :', sy-subrc.
 ENDIF.
 LOOP AT FOC_inrec.
 ADD 1 TO read_cnt.
 call function 'CONVERSION_EXIT_ALPHA_INPUT'
 exporting
 input = FOC_inrec-customer
 importing
 output = FOC_inrec-customer.
 call function 'CONVERSION_EXIT_ALPHA_INPUT'
 exporting
 input = FOC_inrec-part_code
 importing
 output = FOC_inrec-part_code.
 MOVE-CORRESPONDING FOC_inrec TO gs_zgcs_foc.
 MOVE p_comp TO gs_zgcs_foc-company.
 MOVE gs_zgcs_foc-qty TO gs_zgcs_foc-balan.
 MOVE sy-uname TO gs_zgcs_foc-ERNAM.
 MOVE sy-datum TO gs_zgcs_foc-ERDAT.
 MOVE sy-UZEIT TO gs_zgcs_foc-ERZET.
* Source(1:HQ,2:SUB,0:Etc)
 MOVE '1' TO gs_zgcs_foc-source.
 APPEND gs_zgcs_foc TO gt_zgcs_foc.
 ENDLOOP.
* SGE file upload
 ELSE.
 CALL FUNCTION 'WS_UPLOAD'
 EXPORTING
 filename = v_file
 filetype = 'DAT'
 TABLES
 data_tab = inrec
 EXCEPTIONS
 conversion_error = 1
 file_open_error = 2
 file_read_error = 3
 invalid_type = 4
 no_batch = 5
 unknown_error = 6
 invalid_table_width = 7
 gui_refuse_filetransfer = 8
 customer_error = 9
 OTHERS = 10.
 IF sy-subrc <> 0.
 WRITE: / 'FILE UPLOAD :', sy-subrc.
 ENDIF.
 LOOP AT inrec.
 ADD 1 TO read_cnt.
 call function 'CONVERSION_EXIT_ALPHA_INPUT'
 exporting
 input = inrec-customer
 importing
 output = inrec-customer.
 call function 'CONVERSION_EXIT_ALPHA_INPUT'
 exporting
 input = FOC_inrec-part_code
 importing
 output = FOC_inrec-part_code.
 MOVE-CORRESPONDING inrec TO gs_zgcs_foc.
 MOVE p_comp TO gs_zgcs_foc-company.
 MOVE gs_zgcs_foc-qty TO gs_zgcs_foc-balan.
 MOVE sy-uname TO gs_zgcs_foc-ERNAM.
 MOVE sy-datum TO gs_zgcs_foc-ERDAT.
 MOVE sy-UZEIT TO gs_zgcs_foc-ERZET.
* Source(1:HQ,2:SUB,0:Etc)
 MOVE '2' TO gs_zgcs_foc-source.
 APPEND gs_zgcs_foc TO gt_zgcs_foc.
 ENDLOOP.
 ENDIF.
ENDIF.
ENDFORM.
*MODULE POOL::*
*& Module Name : Warranty Bill
*& Sub-Module : W/B
*& Description : Parts Q'ty Adjust(Sales & Warranty)
*& Program Name : ZRSWBP004
*& History
*& Date Author Reason
*& 2007.05.08 Song, Ji-Hyun Initial Coding Req.by WH.Song
*& Logic Process
* - CONDITIONS
* Company, Customer, Material
* - PROCESS
* Display,Insert,Update data in the T/B ZESP04
REPORT zrswbp004 NO STANDARD PAGE HEADING
 MESSAGE-ID 00
 LINE-SIZE 250
 LINE-COUNT 50.
* G L O B A L V A R I A B L E S *
TABLES : zesp04.
DATA : BEGIN OF itab_list OCCURS 0,
 company LIKE zesp04-company,
 customer LIKE zesp04-customer,
 material LIKE zesp04-material,
 adj_date LIKE zesp04-adj_date,
 adjust LIKE zesp04-adjust,
 reason LIKE zesp04-reason,
 reason_code LIKE zesp04-reason_code,
 doc_no LIKE zesp04-doc_no,
 in_date LIKE zesp04-in_date,
 create_id LIKE zesp04-create_id,
 END OF itab_list.
DATA : itab_upload LIKE TABLE OF zesp04 WITH HEADER LINE.
DATA : s_mode(10).
DATA : table_name(10) VALUE 'ZESP04'.
DATA : tot_cnt TYPE i.
DATA : ref_flag(1).
* M A C R O D E F I N E *
DEFINE conversion_kunnr.
call function 'CONVERSION_EXIT_ALPHA_INPUT'
 exporting
 input = &1
 importing
 output = &1.
END-OF-DEFINITION.
DEFINE conversion_material.
call function 'CONVERSION_EXIT_MATN1_INPUT'
 exporting
 input = &1
 importing
 output = &1.
END-OF-DEFINITION.
* S E L E C T I O N S C R E E N *
SELECTION-SCREEN BEGIN OF BLOCK b1 WITH FRAME TITLE title1.
PARAMETERS : company LIKE zesp04-company MEMORY ID buk MODIF ID v1
 OBLIGATORY.
SELECT-OPTIONS : customer FOR zesp04-customer MEMORY ID kun
 MODIF ID v1.
SELECT-OPTIONS : material FOR zesp04-material MEMORY ID mat
 MODIF ID v1.
SELECTION-SCREEN SKIP.
SELECTION-SCREEN BEGIN OF LINE.
SELECTION-SCREEN POSITION 3.
SELECTION-SCREEN COMMENT 3(12) text-002 MODIF ID v2.
PARAMETERS : up_flag AS CHECKBOX MODIF ID v2.
SELECTION-SCREEN END OF LINE.
SELECTION-SCREEN BEGIN OF LINE.
SELECTION-SCREEN COMMENT 3(12) text-001 MODIF ID v2.
PARAMETERS : p_fname(300) LOWER CASE MODIF ID v2.
SELECTION-SCREEN END OF LINE.
SELECTION-SCREEN END OF BLOCK b1.
SELECTION-SCREEN BEGIN OF BLOCK b2 WITH FRAME TITLE title2.
SELECTION-SCREEN BEGIN OF LINE.
SELECTION-SCREEN COMMENT 3(53) text-003 MODIF ID v2.
SELECTION-SCREEN END OF LINE.
SELECTION-SCREEN BEGIN OF LINE.
SELECTION-SCREEN COMMENT 5(10) text-004 MODIF ID v2.
SELECTION-SCREEN END OF LINE.
SELECTION-SCREEN BEGIN OF LINE.
SELECTION-SCREEN COMMENT 5(12) text-005 MODIF ID v2.
SELECTION-SCREEN END OF LINE.
SELECTION-SCREEN BEGIN OF LINE.
SELECTION-SCREEN COMMENT 5(12) text-006 MODIF ID v2.
SELECTION-SCREEN END OF LINE.
SELECTION-SCREEN BEGIN OF LINE.
SELECTION-SCREEN COMMENT 5(15) text-007 MODIF ID v2.
PARAMETERS : df1 TYPE c RADIOBUTTON GROUP grp1.
SELECTION-SCREEN COMMENT 24(13) text-012 MODIF ID v2.
PARAMETERS : df2 TYPE c RADIOBUTTON GROUP grp1.
SELECTION-SCREEN COMMENT 41(11) text-013 MODIF ID v2.
SELECTION-SCREEN END OF LINE.
SELECTION-SCREEN BEGIN OF LINE.
SELECTION-SCREEN COMMENT 5(14) text-008 MODIF ID v2.
SELECTION-SCREEN END OF LINE.
SELECTION-SCREEN BEGIN OF LINE.
SELECTION-SCREEN COMMENT 5(11) text-009 MODIF ID v2.
SELECTION-SCREEN END OF LINE.
SELECTION-SCREEN BEGIN OF LINE.
SELECTION-SCREEN COMMENT 5(14) text-010 MODIF ID v2.
SELECTION-SCREEN END OF LINE.
SELECTION-SCREEN BEGIN OF LINE.
SELECTION-SCREEN COMMENT 5(10) text-011 MODIF ID v2.
SELECTION-SCREEN END OF LINE.
SELECTION-SCREEN END OF BLOCK b2.
INCLUDE zrswbp004_pbo.
INCLUDE zrswbp004_pai.
INITIALIZATION.
title1 = ' Parts Quantity Adjustment '.
title2 = ' Text File Layout '.
* S T A R T O F S E L E C T I O N *
TOP-OF-PAGE.
PERFORM write_header.
TOP-OF-PAGE DURING LINE-SELECTION.
PERFORM write_header.
START-OF-SELECTION.
IF up_flag = 'X'.
 PERFORM upload_data.
ELSE.
 PERFORM select_data.
 SET PF-STATUS 'PF01' EXCLUDING 'SAVE'.
 PERFORM display_data.
ENDIF.
AT USER-COMMAND.
PERFORM user_command.
AT SELECTION-SCREEN ON VALUE-REQUEST FOR p_fname.
PERFORM get_filename.
*& Form SELECT_DATA
* Select Data for Display
FORM select_data.
SELECT * FROM (table_name)
 INTO CORRESPONDING FIELDS OF TABLE itab_list
 WHERE company = company
 AND customer IN customer
 AND material IN material.
CHECK sy-subrc <> 0.
WRITE: 'No data found with your option.'.
ENDFORM. " SELECT_DATA
*& Form DISPLAY_DATA
* Display Data following Condition
FORM display_data.
LOOP AT itab_list.
 FORMAT COLOR 2 INTENSIFIED.
 WRITE : / '|' NO-GAP.
 WRITE : (07) itab_list-company CENTERED NO-GAP, '|' NO-GAP,
 (10) itab_list-customer CENTERED NO-GAP, '|' NO-GAP,
 (20) itab_list-material CENTERED NO-GAP, '|' NO-GAP,
 (10) itab_list-adj_date CENTERED NO-GAP, '|' NO-GAP,
 (15) itab_list-adjust RIGHT-JUSTIFIED NO-GAP, '|'
NO-GAP,
 (55) itab_list-reason LEFT-JUSTIFIED NO-GAP, '|' NO-GAP,
 (11) itab_list-reason_code CENTERED NO-GAP, '|' NO-GAP,
 (10) itab_list-doc_no CENTERED NO-GAP, '|' NO-GAP,
 (10) itab_list-in_date CENTERED NO-GAP, '|' NO-GAP,
 (12) itab_list-create_id CENTERED NO-GAP, '|' NO-GAP.
 FORMAT INTENSIFIED OFF.
 HIDE itab_list.
ENDLOOP.
WRITE : / sy-uline(171).
ENDFORM. " DISPLAY_DATA
*& Form WRITE_HEADER
* Write Report Header
FORM write_header.
DATA : line(1024).
CLEAR line WITH '-'.
DESCRIBE TABLE itab_list LINES tot_cnt.
FORMAT INTENSIFIED ON.
WRITE : 15 'Parts Quantity Adjustment'.
SKIP.
WRITE : / 'Total Count : ', tot_cnt.
WRITE : /.
WRITE : (171) sy-uline.
WRITE : / '|' NO-GAP.
WRITE : (07) 'Company' CENTERED NO-GAP, '|' NO-GAP,
 (10) 'Customer' CENTERED NO-GAP, '|' NO-GAP,
 (20) 'Material' CENTERED NO-GAP, '|' NO-GAP,
 (10) 'Adj. Date' CENTERED NO-GAP, '|' NO-GAP,
 (15) 'Adjust' CENTERED NO-GAP, '|' NO-GAP,
 (55) 'Reason' CENTERED NO-GAP, '|' NO-GAP,
 (11) 'Reason Code' CENTERED NO-GAP, '|' NO-GAP,
 (10) 'Doc No' CENTERED NO-GAP, '|' NO-GAP,
 (10) 'IN DATE' CENTERED NO-GAP, '|' NO-GAP,
 (12) 'CREATE ID' CENTERED NO-GAP, '|' NO-GAP.
WRITE : /(171) sy-uline.
FORMAT INTENSIFIED OFF.
ENDFORM. " WRITE_HEADER
*& Form UPLOAD_DATA
* Data Upload from File
FORM upload_data.
DATA : l_filename LIKE rlgrap-filename,
 temp_dateformat TYPE dateformat.
IF df1 = 'X'.
 temp_dateformat = 'YYYY.MM.DD'.
ELSE.
 temp_dateformat = 'DD.MM.YYYY'.
ENDIF.
MOVE p_fname TO l_filename.
CHECK l_filename NE space.
CALL FUNCTION 'WS_UPLOAD'
 EXPORTING
 filename = l_filename
 filetype = 'DAT'
 dat_d_format = temp_dateformat
 TABLES
 data_tab = itab_list
 EXCEPTIONS
 conversion_error = 1
 file_open_error = 2
 file_read_error = 3
 invalid_type = 4
 no_batch = 5
 unknown_error = 6
 invalid_table_width = 7
 gui_refuse_filetransfer = 8
 customer_error = 9.
IF sy-subrc NE 0.
 MESSAGE s000 WITH 'File upload is failed!'.
 STOP.
ELSE.
 CLEAR : itab_upload, itab_upload[].
 LOOP AT itab_list.
 MOVE-CORRESPONDING itab_list TO itab_upload.
 conversion_kunnr itab_upload-customer.
 conversion_material itab_upload-material.
 itab_upload-mandt = sy-mandt.
 itab_upload-in_date = sy-datum.
 itab_upload-create_id = sy-uname.
*>>>>Insert by GSCHOI 2007.11.08
 IF itab_list-adj_date+0(6) NE sy-datum+0(6).
 MESSAGE i368 WITH 'Adjust month must same as current month!'.
 ROLLBACK WORK.
 STOP.
 ENDIF.
*<<<<End
 APPEND itab_upload.
 INSERT INTO (table_name) VALUES itab_upload.
 IF sy-subrc EQ 0.
 CONTINUE.
 ELSEIF sy-subrc EQ 4.
 MESSAGE s368 WITH 'Duplicated Data Error!'.
 ROLLBACK WORK.
 STOP.
 ELSE.
 MESSAGE s368 WITH 'File Error!'.
 ROLLBACK WORK.
 STOP.
 ENDIF.
 ENDLOOP.
ENDIF.
IF sy-subrc EQ 0.
 MESSAGE s368 WITH 'Uploaded Successfully!'.
ENDIF.
ENDFORM. " UPLOAD_DATA
*& Form USER_COMMAND
* User Command Execution in Screen 1000
FORM user_command.
MOVE-CORRESPONDING itab_list TO zesp04.
CASE sy-ucomm.
 WHEN 'INSERT'.
 PERFORM insert_item.
 WHEN 'UPDATE'.
 PERFORM update_item.
 WHEN 'DISPLAY'.
 PERFORM display_item.
 WHEN 'REFRESH'.
 PERFORM refresh_list.
ENDCASE.
IF ref_flag = 'Y'.
 PERFORM refresh_list.
 CLEAR ref_flag.
ENDIF.
ENDFORM. " USER_COMMAND
*& Form INSERT_ITEM
* When Clicking Insert Button
FORM insert_item.
CLEAR : s_mode.
CLEAR : zesp04.
s_mode = 'INSERT'.
CALL SCREEN '100'.
ENDFORM. " INSERT_ITEM
*& Form UPDATE_ITEM
* When Clicking Update Button
FORM update_item.
CLEAR : s_mode.
s_mode = 'UPDATE'.
CALL SCREEN '100'.
ENDFORM. " UPDATE_ITEM
*& Form DISPLAY_ITEM
* When Clicking Display Button
FORM display_item.
CLEAR : s_mode.
s_mode = 'DISPLAY'.
CALL SCREEN '100'.
ENDFORM. " DISPLAY_ITEM
*& Form REFRESH_LIST
* When Clicking Refresh Button or Returning Display Screen
FORM refresh_list.
CLEAR : itab_list, itab_list[].
PERFORM select_data.
sy-lsind = sy-lsind - 1.
PERFORM display_data.
ENDFORM. " REFRESH_LIST
*& Form GET_FILENAME
* Get Filename
FORM get_filename.
DATA: l_fname LIKE ibipparms-path .
DATA : p_name LIKE sy-repid.
p_name = sy-repid.
CALL FUNCTION 'F4_FILENAME'
 EXPORTING
 program_name = p_name
 dynpro_number = sy-dynnr
 field_name = ''
 IMPORTING
 file_name = l_fname.
p_fname = l_fname.
ENDFORM. " GET_FILENAME
Edited by: Matt on Nov 24, 2008 11:24 AM - surrounded the ABAP with tags

Hi,
 Use SUBMIT statement in your first Report zrswbgcs009 at the end, to call the Modulepool program zrswbp004.
do a search in SDN you will get lot of threads on SUBMIT statement with selection screen.
SUBMIT... [VIA SELECTION-SCREEN]
 [USING SELECTION-SET <var>]
 [WITH <sel> <criterion>]
 [WITH FREE SELECTIONS <freesel>]
 [WITH SELECTION-TABLE <rspar>].
http://help.sap.com/saphelp_nw04/Helpdata/EN/9f/dba51a35c111d1829f0000e829fbfe/content.htm
Regards
Bala Krishna

Calling a report from module pool program

Hi all,
I had a requirement where I need to call a report from the module pool program where in when we click REPORT button, it should display the report output in the another screen.
Can we do by calling screen after pushing REPORT button. If so, where we should write that code ( In pbo or pai). Please give me an idea.
Thanking you,
Regards,
Murali Krishna T

Use submit syntax.
Press F1 on submit, Donot use return statement with it.
If so, where we should write that code ( In pbo or pai).
Please understand about these two events before doing the requirement.

Creating module pool programming in abap objects

Hello...
I just wanted to know how u create a give modulepool programming in classes and objects.Could anyone tell me the procedure how to do so.And i knew that module pool programming has become obsolete and now everyone are using object oriented concept in module pool programming.soo i want why r they using soo and what is the drawback in using the module pool programming instead of oops concepts.Could anyone give me the clear explanation..

Hello Chadipriya,
You can create module pool program for both ABAP and ABAP OO(Object Oriented).
The thing is in OO u have to declare classes,objects and methods.
Procedure oriented approach
1. Emphasis on tasks
2. Large programs are divided into smaller programs known as functions
3. Most of the functions share global data
4. Data move openly around the system from function to function
Object oriented approach
Emphasis on things that does those tasks
Programs are divided into objects
3. Data structures are designed such that they characterized the objects
4. Functions that operate on the data of an object are tied together in the data structure
5. Data can be hidden and cannot be accessed by external functions
6. New data and functions can be easily added whenever necessary
Go to SE80 ---> Select Program ---> Give ur program name and type this code below :-
REPORT YSUBDEL LINE-SIZE 120.
CLASS parentclass DEFINITION .
PUBLIC SECTION.
DATA : commondata(30) type c value 'Accessible to all'.
METHODS : SHOWVAL.
PROTECTED SECTION.
DATA : protectdata(40) type c value 'Protected data'.
private section.
data : privatedata(30) type c value 'Private data'.
ENDCLASS.
CLASS parentclass IMPLEMENTATION.
METHOD : SHOWVAL.
write:/5 'All data from parentclass shown:-'.
write:/ sy-uline.
WRITE:/5 COMMONDATA,
 /5 PROTECTDATA,
 /5 PRIVATEDATA.
endmethod.
endclass.
CLASS childclass DEFINITION INHERITING FROM parentclass.
PUBLIC SECTION .
METHODS : subval.
ENDCLASS.
CLASS childclass IMPLEMENTATION.
method : subval.
skip 1.
write:/5 'Data of parent shown from child-'.
write:/5 sy-uline.
WRITE:/5 COMMONDATA,
 /5 PROTECTDATA.
Commondata = 'Public data changed in subclass'.
Protectdata = 'Protected data changed in subclass'.
write:/5 sy-uline.
WRITE:/5 COMMONDATA,
 /5 PROTECTDATA.
endmethod.
endclass.
You r using OOPs concepts in module pool program and not module pool programming instead of oops concepts.
Reward points if helpful
Thanks,
Sachin

Plz provide tutorial to learn the Module pool programing?

Similar Messages

Maybe you are looking for