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.

Similar Messages

Calling a report from Module Pool

While calling a report from the module pool I'm not able to display th alv. The skeleton of the ALV is coming. But the data and headings are also not displayed.
But where as calling the same program from a report it is coming properly. can somebody please guide me where did I go wrong?

MODULE user_command_1001 INPUT.
w_ok_code = ok_code.
CLEAR ok_code.
CASE w_ok_code.
    WHEN 'BACK'.
      LEAVE PROGRAM .
    WHEN 'CREATE'.
      CALL TRANSACTION 'Z_FIRST_TIME'.
    WHEN 'SYNC'.
      CALL TRANSACTION 'Z_SYNC'.
    WHEN 'APPROVE'.
     SUBMIT zds_xx_approval_status WITH po_aname EQ sy-uname AND RETURN.
    WHEN 'OVERVIEW'.
      PERFORM show_all_reqids.
ENDCASE.
ENDMODULE.

How to extract the data from module pool program to Excel Sheet?

Hi Guys
        I am having a requirement to transfer the data from Module pool screen to excel sheet directly.
        This is an urgent requirement.
        So plz reply me with some coding examples.
        I will give points for that.

This report extract excel file. From that concept you can easily extract data from module pool program also by coding in PAI of the screen.
REPORT ztest1 .
* this report demonstrates how to send some ABAP data to an
* EXCEL sheet using OLE automation.
include ole2incl.
* handles for OLE objects
data: h_excel type ole2_object,        " Excel object
      h_mapl type ole2_object,         " list of workbooks
      h_map type ole2_object,          " workbook
      h_zl type ole2_object,           " cell
      h_f type ole2_object,            " font
      h_c type ole2_object.            " color
DATA: FILENAME LIKE RLGRAP-FILENAME.
tables: spfli.
data h type i.
* table of flights
data: it_spfli like spfli occurs 10 with header line.
*&   Event START-OF-SELECTION
start-of-selection.
* read flights
select * from spfli into table it_spfli.
* display header
uline (61).
write: /     sy-vline no-gap,
          (3) 'Flg'(001) color col_heading no-gap, sy-vline no-gap,
          (4) 'Nr'(002) color col_heading no-gap, sy-vline no-gap,
          (20) 'Von'(003) color col_heading no-gap, sy-vline no-gap,
          (20) 'Nach'(004) color col_heading no-gap, sy-vline no-gap,
          (8) 'Zeit'(005) color col_heading no-gap, sy-vline no-gap.
uline /(61).
* display flights
loop at it_spfli.
    write: / sy-vline no-gap,
             it_spfli-carrid color col_key no-gap, sy-vline no-gap,
             it_spfli-connid color col_normal no-gap, sy-vline no-gap,
             it_spfli-cityfrom color col_normal no-gap, sy-vline no-gap,
             it_spfli-cityto color col_normal no-gap, sy-vline no-gap,
             it_spfli-deptime color col_normal no-gap, sy-vline no-gap.
endloop.
uline /(61).
* tell user what is going on
call function 'SAPGUI_PROGRESS_INDICATOR'
     exporting
*           PERCENTAGE = 0
           text       = text-007
       exceptions
            others     = 1.
* start Excel
create object h_excel 'EXCEL.APPLICATION'.
* PERFORM ERR_HDL.
set property of h_excel 'Visible' = 1.
* CALL METHOD OF H_EXCEL 'FILESAVEAS' EXPORTING #1 = 'c:kis_excel.xls'
* PERFORM ERR_HDL.
* tell user what is going on
call function 'SAPGUI_PROGRESS_INDICATOR'
     exporting
*           PERCENTAGE = 0
           text       = text-008
       exceptions
            others     = 1.
* get list of workbooks, initially empty
call method of h_excel 'Workbooks' = h_mapl.
perform err_hdl.
* add a new workbook
call method of h_mapl 'Add' = h_map.
perform err_hdl.
* tell user what is going on
call function 'SAPGUI_PROGRESS_INDICATOR'
     exporting
*           PERCENTAGE = 0
           text       = text-009
       exceptions
            others     = 1.
* output column headings to active Excel sheet
perform fill_cell using 1 1 1 200 'Carrier id'(001).
perform fill_cell using 1 2 1 200 'Connection id'(002).
perform fill_cell using 1 3 1 200 'City from'(003).
perform fill_cell using 1 4 1 200 'City to'(004).
perform fill_cell using 1 5 1 200 'Dep. Time'(005).
loop at it_spfli.
* copy flights to active EXCEL sheet
    h = sy-tabix + 1.
    if it_spfli-carrid cs 'AA'.
      perform fill_cell using h 1 0 000255000 it_spfli-carrid.
    elseif it_spfli-carrid cs 'AZ'.
      perform fill_cell using h 1 0 168000000 it_spfli-carrid.
    elseif it_spfli-carrid cs 'JL'.
      perform fill_cell using h 1 0 168168000 it_spfli-carrid.
    elseif it_spfli-carrid cs 'LH'.
      perform fill_cell using h 1 0 111111111 it_spfli-carrid.
    elseif it_spfli-carrid cs 'SQ'.
      perform fill_cell using h 1 0 100100100 it_spfli-carrid.
    else.
      perform fill_cell using h 1 0 000145000 it_spfli-carrid.
    endif.
    if it_spfli-connid lt 400.
      perform fill_cell using h 2 0 255000255 it_spfli-connid.
    elseif it_spfli-connid lt 800.
      perform fill_cell using h 2 0 077099088 it_spfli-connid.
    else.
      perform fill_cell using h 2 0 246156138 it_spfli-connid.
    endif.
    if it_spfli-cityfrom cp 'S*'.
      perform fill_cell using h 3 0 155155155 it_spfli-cityfrom.
    elseif it_spfli-cityfrom cp 'N*'.
      perform fill_cell using h 3 0 189111222 it_spfli-cityfrom.
    else.
      perform fill_cell using h 3 0 111230222 it_spfli-cityfrom.
    endif.
    if it_spfli-cityto cp 'S*'.
      perform fill_cell using h 4 0 200200200 it_spfli-cityto.
    elseif it_spfli-cityto cp 'N*'.
      perform fill_cell using h 4 0 000111222 it_spfli-cityto.
    else.
      perform fill_cell using h 4 0 130230230 it_spfli-cityto.
    endif.
    if it_spfli-deptime lt '020000'.
      perform fill_cell using h 5 0 145145145 it_spfli-deptime.
    elseif it_spfli-deptime lt '120000' .
      perform fill_cell using h 5 0 015215205 it_spfli-deptime.
    elseif it_spfli-deptime lt '180000' .
      perform fill_cell using h 5 0 000215205 it_spfli-deptime.
    else.
      perform fill_cell using h 5 0 115115105 it_spfli-deptime.
    endif.
endloop.
* EXCEL FILENAME
CONCATENATE SY-REPID '_' SY-DATUM+6(2) '_' SY-DATUM+4(2) '_'
              SY-DATUM(4) '_' SY-UZEIT '.XLS' INTO FILENAME.
CALL METHOD OF H_MAP 'SAVEAS' EXPORTING #1 = FILENAME.
free object h_excel.
perform err_hdl.
*       FORM FILL_CELL                                                *
*       sets cell at coordinates i,j to value val boldtype bold       *
form fill_cell using i j bold col val.
call method of h_excel 'Cells' = h_zl
    exporting
      #1 = i
      #2 = j.
perform err_hdl.
set property of h_zl 'Value' = val .
perform err_hdl.
get property of h_zl 'Font' = h_f.
perform err_hdl.
set property of h_f 'Bold' = bold .
perform err_hdl.
set property of h_f 'Color' = col.
perform err_hdl.
endform.                    "FILL_CELL
*&      Form ERR_HDL
*       outputs OLE error if any                                       *
* --> p1        text
* <-- p2        text
form err_hdl.
if sy-subrc <> 0.
    write: / 'OLE-Automation Error:'(010), sy-subrc.
    stop.
endif.
endform.                    " ERR_HDL

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

How to remove the print popup screen from module pool program

Hi,
In my project i am having one module pool program in which 7-8 screens are there.
In the initial screen after entering the equipment number when i am executing the program then after loading second screen
it is showing one screen is coming which is asking to print the content of the page.
I want to remove this screen (printing popup) but i am not able to get the code or setting for it.
Please help me to solve this problem.
Thanks and regards.

I think this is more to do with ABAP than EP so, the corresponding sections of forum could prove more helpful on this...
Thanks,
H

How to pass the field value from module pool program to smartform using submit?

// AT pai of module pool pgm i entered the following: here gv_orderid is my value to be available at smart form(driver pgm) & zmusic_store_smf is the driver program of my smartform.
gv_orderid= wa-itemid./
SUBMIT ZMUSIC_STORE_SMF VIA SELECTION-SCREEN
                              WITH p_order = gv_orderid
                              AND RETURN.
//AT driver pgm(zmusic_store_smf):
START-OF-SELECTION.
CALL FUNCTION 'SSF_FUNCTION_MODULE_NAME'
    EXPORTING
      formname                 = 'ZMUSIC_SMARTFORM1'
*   VARIANT                  = ' '
*   DIRECT_CALL              = ' '
   IMPORTING
     fm_name                  = lv_form
   EXCEPTIONS
     no_form                  = 1
     no_function_module       = 2
     OTHERS                   = 3.
IF sy-subrc <> 0.
* MESSAGE ID SY-MSGID TYPE SY-MSGTY NUMBER SY-MSGNO
*         WITH SY-MSGV1 SY-MSGV2 SY-MSGV3 SY-MSGV4.
ENDIF.
CALL FUNCTION lv_form
   EXPORTING
*      iv_orderid = is_purchase_item-zorder_id.
iv_orderid = gv_orderid.
// here i'm trying to call my smartform('ZMUSIC_SMARTFORM1') from this driver pgm but unable to access the value of gv_orderid please help me out with this.

Declare the gv_orderid in modulepool program.
And Declare the parameter as import parameter in smartform.
CALL FUNCTION lv_form
   EXPORTING
*   ARCHIVE_INDEX              =
*   ARCHIVE_INDEX_TAB          =
*   ARCHIVE_PARAMETERS         =
*   CONTROL_PARAMETERS         =
*   MAIL_APPL_OBJ              =
*   MAIL_RECIPIENT             =
*   MAIL_SENDER                =
*   OUTPUT_OPTIONS             =
*   USER_SETTINGS              = 'X'
   i_input                    = gv_orderid
* IMPORTING
*   DOCUMENT_OUTPUT_INFO       =
*   JOB_OUTPUT_INFO            =
*   JOB_OUTPUT_OPTIONS         =
* EXCEPTIONS
*   FORMATTING_ERROR           = 1
*   INTERNAL_ERROR             = 2
*   SEND_ERROR                 = 3
*   USER_CANCELED              = 4
*   OTHERS                     = 5

How to trigger abap report from module pool

hi,
continuing with this link
table control this is done (Module pool )
there were two buttons (accept and delete )in the module pool..so when the user clik 'accepts ' the records (from table control ) then it shud call abap report which will run in background..
so how do we pass the values selected from table control to the abap report in one go.....as only one background job has to run..say if there are 10 entries then it shud take all the 10 entries and trigger the abap report where it will do the processing with the selected 10 records in the abap report.
Thanks
Mohan..

Declare the parameters of the report as select options and call it using submit statement.
link:[http://help.sap.com/abapdocu_70/en/ABAPSUBMIT_VIA_JOB.htm]

Calling a report from a executable program

Hi All,
i want to call a report which is generated by tcode CO88 from a executable program. I want to pass the values of order from the exe program only. But my requirement is such that i want co88 to process only open orders, so please suggest how can i do that.
thanks in advance.
Pankaj Sharma

hi,
chk this sample.
*Code used to populate 'select-options' & execute report
DATA: seltab type table of rsparams,
      seltab_wa like line of seltab.
seltab_wa-selname = 'PNPPERNR'.
seltab_wa-sign    = 'I'.
seltab_wa-option = 'EQ'.
load each personnel number accessed from the structure into
parameters to be used in the report
loop at pnppernr.
    seltab_wa-low = pnppernr-low.
    append seltab_wa to seltab.
endloop.
SUBMIT zreport with selection-table seltab
                                via selection-screen.
*Code used to populate 'parameters' & execute report
SUBMIT zreport with p_param1 = 'value'
                with p_param2 = 'value'.
Other additions for SUBMIT
*Submit report and return to current program afterwards
SUBMIT zreport AND RETURN.
*Submit report via its own selection screen
SUBMIT zreport VIA SELECTION-SCREEN.
*Submit report using selection screen variant
SUBMIT zreport USING SELECTION-SET 'VARIANT1'.
*Submit report but export resultant list to memory, rather than
*it being displayed on screen
SUBMIT zreport EXPORTING LIST TO MEMORY.
Once report has finished and control has returned to calling
program, use function modules LIST_FROM_MEMORY, WRITE_LIST and
DISPLAY_LIST to retrieve and display report.
rgds
anver
if hlped pls mark points

Calling custom report from seeded spawned program

Hi,
I dont know how to call a custom report(ie.,My own report) when Dunning letter generate is kicked off rather than calling the original programs(ie., Dunning letter print from dunning letter generate etc).
thanks in advance.

Hello vishwam,
as I remember, there is an option to keep the dunning conc request assigned but change to executable to your own.
Keep in mind that this way is not fully supported, but it should work.
Regards
Volker

Is there a user exit called when a module pool program is launch ?

Hello,
I know the exit 'EXIT_SAPLSABE_010' and it's very usefull for adding code before a report is launch.
But this exit is not called when a program is a "Module pool" type.
Is there a way to add my own code before this kind of program is launch ?
Thanks in advance,
Simon
Edited by: Simon Desbonnets on Mar 9, 2010 2:23 PM

Thanks for your answer.
No it's not for initializing values. It's for logging statistics into a specific table (program name, date ...).
The event "load-of-program" can be use for one program, it's not what I'm looking for.
I would like to know if there is an exit that is called each time a module pool program is executed.

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 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

How to use one module pool program in another module pool programming?

Hi
I have one moodule pool program.
In one of my screen i want to use some code which already developed in another module pool program.
Is there any direct way for using one module pool programcode in another module pool program.
If there any approaches for this plz help me in this issue.

Dear,
If you want to use the code.
first you can write your code in a subroutine in module pool program 1
and then you can use it from module pool program 2 by
perform subroutine_name(program_name)
using P_1
changing C_1
if you wan to use one module pool data into other module pool.
so that is another requirement.

Call module pool program from report

Hi,
Iam calling module pool program from a report, while passing values to module pool program, one of the field doesn't have parameter id, how to pass value to it. and also please let me know how to call module pool program.
Appreciate your help.
Thanks in advance
jog

Hi Jog,
Module pool program can be run in background. Most of the BDC's are written on module pool programs and they run in the background.
Also regarrding copying the standard program, if you require to make the changes for every user then instead of copying the program make modification in standard program as copied program are much harder to maintain during support pack implementation or upgrade that modification to standard program.
Reward points if useful.
Regards,
Atish

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

Similar Messages

Maybe you are looking for