RE:module pool module switch.

Hi all,
Can any one give me the sample code for module switch in modulepool pgm.What is the exact use of this conditionality,
Thanks in advance,
Alex.

Hi,
You can fetch previous entry into itab and that you compare with current entry.
1)
select ....
into itab.
loop at itab where batch eq batch.
endloop.
2)
select ... form table into itab
where batch eq batch.
if sy-subrc eq 0.
functionality after true the condition.
endif.
3)select single ...from ..into..
where batch eq batch.
select ... form table into itab
where batch eq batch.
if sy-subrc eq 0.
functionality after true the condition.
endif.

Similar Messages

MODULE POOL / MODULE PROGRAMMING / DIALOGUE PROG.

Hello to the Experts!!
I need to know what's the diffrences among
1.) Module Pool
2.) Module Programming
3.) Dialogue Prog.
If they are different from each other, I want to learn each of them.
Kindly provide me all the materials to master them.
Looking forward to your huge responses.
Thanks!!

Hi,
I need to know what's the diffrences among
1.) Module Pool
2.) Module Programming
3.) Dialogue Prog.
All the 3 are the same.
For the docs.
Refer
new to module pool program
http://wiki.ittoolbox.com/index.php/FAQ:What_is_module_pool_program_in_abap%3F
http://www.thespot4sap.com/Articles/SAP_Design_Dynpro.asp
check this link:
http://help.sap.com/printdocu/core/Print46c/en/data/pdf/BCDWBTUT/BCDWBTUT.pdf
http://help.sap.com/saphelp_40b/helpdata/en/d3/2e974d35c511d1829f0000e829fbfe/applet.htm
Have a look at these good links-
http://www.allsaplinks.com/dialog_programming.html
http://sap.mis.cmich.edu/sap-abap/abap09/
http://www.sapdevelopment.co.uk/dialog/dialoghome.htm
http://help.sap.com/saphelp_webas630/helpdata/en/9f/db9cdc35c111d1829f0000e829fbfe/content.htm
http://sap.mis.cmich.edu/abap-00/
http://www.allsaplinks.com/files/using_table_in_screen.pdf
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
http://help.sap.com
http://www.sapgenie.com/abap/example_code.htm
http://help.sap.com/saphelp_47x200/helpdata/en/52/670ba2439b11d1896f0000e8322d00/frameset.htm
http://www.allsaplinks.com/dialog_programming.html
http://www.sapbrain.com/TUTORIALS/default.html
http://www.sappoint.com/abap/spmp.pdf
http://sappoint.com/abap.html
http://www.sap-img.com/abap.htm
http://sap.ittoolbox.com/code/archives.asp?i=10&t=450&a=t
http://www.sapdevelopment.co.uk/dialog/dialoghome.htm
http://www.sap-img.com/abap/
http://www.sap-img.com/
http://www.sappoint.com/faq/faqdiapr.pdf
http://www.allsaplinks.com/dialog_programming.html
http://www.sapgenie.com/abap/example_code.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
http://www.sapdevelopment.co.uk/dialog/dialoghome.htm
Regards,
Deepu.K

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

Module Pool Programming in ECC 5.0

Hi Experts,
Can any one explain the unique features of Module pool programming in ECC 5.0.
Even if you find any documentation please pass it on.
Regards,
Shankar

The screen painter is basically the same in 4.7 and ECC6.
The difference you see might be because you are using the alphanumerical screen painter in 4.7 where the default in ECC is the graphical screen painter. Both are available in 4.7 and ECC.
To switch back to the alphanumerical in ECC6, just do:
- SE80
- menu Utilities
- Settings
- tabstrip Screen Painter
- remove the flag for graphical layout editor
This will start the alphanumerical instead of the graphical one
However the graphical one is much easier to use so you might want to look into using that one instead of the (old) alphanumerical one.
Hope that helps,
Michael

Reg. cursor-selection in module pool....have ur points.

Hi all,
Pleas. help me with a simple example of at cursor-selection in module pool programming.
with simple code & steps
Have ur points.
Regards,
[email protected]

Hi Pradeep,
The Best explanation with example comes from our help.sap.com....
http://help.sap.com/saphelp_nw04/helpdata/en/9f/dbabbd35c111d1829f0000e829fbfe/content.htm
Also this might help...
MODULE mod [ AT {EXIT-COMMAND|CURSOR-SELECTION} ]
[ ON {CHAIN-INPUT|CHAIN-REQUEST} ]
[ SWITCH switch ].
... AT CURSOR-SELECTION
The AT CURSOR-SELECTION addition at the event PAI causes the module mod to be called only if
The function used to trigger event PAI has function code "CS" and function type "S"
The cursor is placed on a single input or output field of the screen at the moment of the user action
The call occurs within the usual PAI processing, meaning that the automatic input checks defined in the system or in the ABAP Dictionary are executed and the MODULE statement is called according to its position in the event block. You can use the addition in connection with the FIELD statement.
If the PAI event is triggered under the above circumstances, the function code is not passed to sy-ucomm and the OK field. They keep their previous values.
Note
The function type and function code of a function are determined in the Screen Painter or in the Menu Painter. We recommend to assign function code "CS" in the Menu Painter to function key F2 in order to simultaneously assign the double-click function of the mouse to it. This allows you to assign dialog modules to the selection of input or output fields.
Refer thread: Re: MODULE REQUEST
Hope that helps!!
*Reward useful answers*
Regards,
Naveenan.

ABAP Module pool programming

Hi all plz any one send me the doc for Module pool programmiing to learn on my own
thanks & regards
vamsin

Hi,
This is the material find the attachment.
hi,
Pool table
A database table defined in the ABAP Dictionary whose database instance is assigned to more than one table defined in the ABAP Dictionary. Multiple pool tables are assigned to a table pool in the database. The key fields of a pool table have to be character-type fields. The table pool's primary key consists of two fields: TABNAME for the name of a pool table, and VARKEY for the interdependent contents of the key fields in the corresponding pool table. The non-key fields of the pool table are stored in compressed format in their own column, called VARDATA, of the table pool. The only way to access pool tables is by using Open SQL. Joins are not allowed.
Table Pool
Database table in the database that contains the data of several pool tables.
Cluster Table
Database table defined in the ABAP Dictionary, whose version on the database is not only assigned to one table defined in the ABAP Dictionary. Several cluster tables are assigned to a table cluster in the database. The intersection of the key fields of the cluster tables forms the primary key of the table cluster. The other columns of the cluster tables are stored in compressed form in a single column VARDATA of the table cluster. You can access cluster tables only via Open SQL, and only without using joins.
Table Cluster
Database table in the database that contains the data of several cluster tables.
Note: Never mix up with a database table that has the necessary structure for storing data clusters in database tables and in the shared memory. Those are called INDX-type, with reference to the database table INDX supplied by SAP. Data clusters are groupings of data objects for transient and persistent storage in a selectable storage medium. A data cluster can be processed using the statements IMPORT, EXPORT, and DELETE FROM
P.Naganjana ReddyDAY-4 CONTENTS
SCREEN PAINTER
 &#56256;&#56510;
Introduction to Dialog Programming
 &#56256;&#56510;
Transactions
Screens (dynpros)
ABAP/4 module pool
Transferring Field Data
Field Attributes
Error Dialogs
Data Consistency
Dynpro
Layout
 &#56256;&#56510;
Exercise
TABLE CONTROL
 &#56256;&#56510;
Functional scope
 &#56256;&#56510;
Programming
 &#56256;&#56510;
Attributes
 &#56256;&#56510;
EXERCISE
TABSTRIP CONTROLS
 &#56256;&#56510;
Defining the Tabstrip Control Area and Tab Titles
 &#56256;&#56510;
Assigning a Subscreen Area to a Tab Title
 &#56256;&#56510;
Paging in the SAPgui
 &#56256;&#56510;
Programming the Flow Logic
 &#56256;&#56510;
EXERCISE
P.Naganjana Reddy
SCREEN WITH FIELDS
Introduction to Dialog Programming
Transactions
A transaction is a program that conducts a dialog with the user. In a typical dialog, the
system displays a screen on which the user can enter or request information. As a reaction on
the the user input or request, the program executes the appropriate actions: it branches to the
next screen, displays an output, or changes the database.
Example
A travel agent wants to book a flight. The agent enters the corresponding data on the
screen. The system either confirms the desired request, that is, the agent can book the flight
and the customer travels on the desired day on the reserved seat to the chosen destination,
or the system displays the information that the flight is already booked up.
To fulfil such requirements, a dialog program must offer:
_a user-friendly user interface
_format and consistency checks for the data entered by the user
_easy correction of input errors
_access to data by storing it in the database.
ABAP/4 offers a variety of tools and language elements to meet the requirements stated
above in the dialog programs.
Structure of a Dialog Program
A dialog program consists of the following basic components:
P.Naganjana Reddy
Screens (dynpros)
Each dialog in an SAP system is controlled by dynpros. A dynpro (Dynamic PROgram) consists of a screen and its flow logic and controls exactly one dialog step. The flow logic determines which processing takes place before displaying the screen (PBO-Process Before Output) and after receiving the entries the user made on the screen (PAI-Process After Input).
The screen layout fixed in the Screen Painter determines the positions of input/output
fields, text fields, and graphical elements such as radio buttons and checkboxes. In addition, the Menu Painter allows to store menus, icons, pushbuttons, and function keys in one or more GUI statuses. Dynpros and GUI statuses refer to the ABAP/4 program that control the sequence of the dynpros and GUI statuses at runtime.
ABAP/4 module pool
Each dynpro refers to exactly one ABAP/4 dialog program. Such a dialog program is also called a module pool, since it consists of interactive modules. The flow logic of a dynpro contains calls of modules from the corresponding module pool. Interactive modules called at the PBO event are used to prepare the screen template in accordance to the context, for example by setting field contents or by suppressing fields from the display that are not needed. Interactive modules called at the PAI event are used to check the user input and to trigger appropriate dialog steps, such as the update task.
All dynpros to be called from within one transaction refer to a common module pool. The dynpros of a module pool are numbered. By default, the system stores for each dynpro the dynpro to be displayed next. This dynpro sequence or chain can be linear as well as cyclic. From within a dynpro chain, you can even call another dynpro chain and, after processing it, return to the original chain.
Transferring Field Data
How do I display fields known in an ABAP/4 module on the screen? How do I transfer
user entries on the screen to the module? In contrast to report programming, you cannot write field data to the screen using the WRITE statement. The system instead transfers data by comparing screen field names with ABAP/4 variable names. If both names are the same, it transfers screen field values to ABAP/4 program fields and vice versa. This happens immediately before and immediately after displaying the screen.
Field Attributes
For all screen fields of a dynpro, field attributes are defined in the Screen Painter. If a
field name in the screen corresponds to the name of an ABAP/4 Dictionary field, the system automatically establishes a reference between these two fields. Thus, a large number of field attributes in the dynpro is automatically copied from the ABAP/4 Dictionary. The field attributes together with data element and domain of the assigned Dictionary field form the basis for the standard functions the dynpro executes in a dialog (automatic format check for screen fields, automatic value range check, online help, and so on).
Error Dialogs
Another task of the dynpro processor is to conduct error dialogs. Checking the input data is carried out either automatically using check tables of the ABAP/4 Dictionary or by the ABAP/4 program itself. The dynpro processor includes the error message into the received screen and returns the screen to the user. The message may be context-sensitive, that is, the system replaces placeholders in the message text with current field contents. In addition, only fields whose contents is related to the error and for which a correction may solve the error can accept input.
P.Naganjana Reddy
Data Consistency
To keep data consistent within complex applications, ABAP/4 offers techniques for
optimizing database updates that operate independent of the underlying database and correspond to the special requests of dialog programming. For more information on database updates, see Programming Database Updates.
Dynpro
Each screen contains fields used to display or request information. Fields can be text strings, input or output fields, radio buttons, checkboxes, or pushbuttons. The screen of Transaction TZ10 contains only texts and input/output fields.
An SAP dynpro consists of several components:
Flow logic: Calls of the ABAP/4 modules for a screen.
Screen layout: Positions of the texts, fields, pushbuttons, and so on for a screen.
Screen attributes: Number of the screen, number of the subsequent screen, and others.
Field attributes: Definition of the attributes of the individual fields on a screen.
SCREEN PAINTER
You create and edit all components of a dynpro in the Screen Painter. To call the Screen
Painter, create a dynpro in the Object Browser or double-click on an existing dynpro. The Object Browser then calls the Screen Painter. There, you can enter the flow logic of the new dynpro. By pressing the corresponding pushbutton you can maintain the Screen attributes, branch to the Full Screen-Editor or you choose the pushbutton Field list and change the attributes of fields.
Screen Attributes
From the users point of view, a transaction is a sequence of screens, displayed one after
another. How do I determine this sequence? The transactionss attributes determine the first screen to be displayed. The attributes of the individual dynpros determine which screen to display
P.Naganjana Reddy
after the current screen. You can also set the number of the subsequent screen dynamically from within the ABAP/4 program.
Layout
Choose Fullscreen to go to the screen editor. Here you can determine the layout of the
screen. For Transaction TZ10, the desired fields can be copied from Table SPFLI of the
ABAP/4 Dictionary.
Field Attributes
To display and modify the attributes of the individual fields (input/output fields, input
required, possible entries button, invisible, and so on), use the Field list.The fields Company (SPFLI-CARRID) and Flight number (SPFLI-CONNID) are defined as input/output fields. All other fields are used only for outputting the flight data.
Flow Logic
The flow control code of a dynpro consists of a few statements that syntactically ressemble ABAP/4 statements. However, you cannot use flow contol keywords in ABAP/4 and vice versa. You enter the flow control code in the Screen Painter as one component of the dynpro.
The flow control for the dynpro of Transaction TZ10 looks like this:
PROCESS BEFORE OUTPUT.
MODULE SET_STATUS_0100.
PROCESS AFTER INPUT
MODULE USER_COMMAND_0100.
The PROCESS statement names the event type for the dynpro and the MODULE statement tells the system which ABAP/4 routine to call for this event. In this example, there is only one MODULE for each event PBO and PAI. However, an event can contain several statements with several keywords. (The flow control language contains only few statement types. The most important are MODULE, FIELD, CHAIN, LOOP, CALL SUBSCREEN.) To display information on the statement syntax in the flow logic, choose Utilities Help on... in the flow logic editor. In the subsequent dialog window, mark Flow logickeyword, enter the name of the desired keyword, and press ENTER.
ABAP/4 Module Pool
In the Object Browser, the module pool code belongs to one of the following categories:
Global fields: data declarations that can be used by all modules in the module pool
PBO modules: modules that are called before displaying the screen
PAI modules: modules that are called in response to the user input
Subroutines: subroutines that can be called from any position within the module pool.
You use the ABAP/4 Dictionary to store frequently used data declarations centrally. Objects defined in the Dictionary are known throughout the system. Active Dictionary definitions can be accessed by any application. Data defined in the Dictionary can be included in a screen or used by an ABAP/4 program. You declare global data in the TOP module of the transaction, using the TABLES, STRUCTURE, LIKE statements and others. Transaction TZ10 accesses the Dictionary definition of Table SPFLI to provide the desired flight data display. If the TOP include contains the TABLES: SPFLI declaration, all modules in the module pool can access the table fields of
P.Naganjana Reddy
Table SPFLI. The PAI module USER_COMMAND_0100 checks which pushbutton the user activated (CASE OK_CODE). The Display pushbutton in Transaction TZ10 has the function code
SHOW. (For more information on handling function codes, see Processing User Requests). The program then tries to select those records in the SPFLI database that correspond to the data the user entered. The WHERE condition determines matching records by comparing the fields SPFLI-CARRID and SPFLI-CONNID with the database key fields CARRID and CONNID. As soon as a matching record is found, the database transfers all accompanying SPFLI fields to the program table.
When the screen is displayed again, the complete information appears in the output fields
of the screen. The system automatically displays these fields, since the ABAP/4 field names SPFLI-CARRID and SPFLI-CONNID are the same as the screen field names.
In the PBO module STATUS_0100 of Transaction TZ10, the screen 100 receives a GUI status (using SET PF-STATUS) and a GUI title (using SET TITLEBAR):
SET PF-STATUS TZ0100.
SET TITLEBAR 100.
A GUI status is a subset of the interface elements used for a certain screen. The status
Comprise those elements that are currently needed by the transaction. The GUI status for a transaction may be composed of the following elements:
The GUI title is the screen title displayed in the title bar of the window. In contrast to the
GUI status that can be used for several screens, a GUI title belongs to one screen.To create and edit GUI status and GUI title, you use the Menu Painter. To start the Menu Painter, create a GUI status or GUI title in an object list in the Object Browser (or double-click on an existing status or title).
Interaction between Dynpro and ABAP/4 Module Pool
In its most simple form, a transaction is a collection of screens and ABAP/4 routines, controlled and executed by a dialog processor. The dialog processor processes screen after screen, thereby triggering the appropriate ABAP/4 processing for each screen. For each screen, the system executes the flow logic that contains the corresponding ABAP/4 processing. The control passes from screen flow logic to ABAP/4 code and back.
The sequence of events for Transaction TZ10, for example, looks like this:
P.Naganjana Reddy
 1.
In the PBO event, the statement MODULE STATUS_0100 passes control to the corresponding ABAP/4 module.In the ABAP/4 module pool, the screen to be displayed receives a menu interface.
2.
After processing the module STATUS_0100, control returns to the flow logic.For the PBO event, no further processing is required. The system display the screen and receives entries from the user. The entries are:
the values for the fields Company and Flight number.
the four-character function code that tells which pushbutton the user activated.
 3.
The user input triggers the PAI event. The first PAI statement passes control to the ABAP/4 module USER_COMMAND_0100.Module USER_COMMAND_0100 processes the requests of the user.
4. After processing MODULE USER_COMMAND_0100, control returns to PAI. This terminates the dialog.
P.Naganjana Reddy
EXERCISE
Goto to ABAP editor, and enter the program name ZKA_SCREEN.
Declare the tables and call the screen.
In order to create the object, double click on the screen no, you will automatically guided to the screen painter SE51.
P.Naganjana Reddy
Enter the short description and click on the FLOW LOGIC tab.
Uncomment the flow logic, both PAI and PBO.
P.Naganjana Reddy
Now click on the LAYOUT button.
Click on the DICTIONARY/PROGRAM FIELDS WINDOW F6 button. Type in the table name and click on GET FROM DIC button and select the fields required for the screen and click on the COPY button.
P.Naganjana Reddy
Now drag and place the INPUT/OUTPUT fields box on the screen.
Now click on the TEXT FIELD button and place in the screen and stretch the box for the size required. Now double click on the box, U will get the attributes screen. Enter the name and Text for the field.
P.Naganjana Reddy
Now we need to place the bush buttons. So Click on the push button on the left side and place it on the screen. Double click on it, u will get the attributes screen. Enter the name, text and the icon required and mainly the FCTCODE. It is the one which links the screen painter with the code.
Once everything is set up, SAVE, CHECK and ACTIVATE the screen.
P.Naganjana Reddy
Click on the BACK button. U will be guided to the FLOW LOGIC screen.
Double click on PAI, Because for the screen painter with the fields, Process After the Input is done and so u will guided to the Editor screen.
P.Naganjana Reddy
Now we need to set the System-Uses commands which links the code to the Editor.
So the conditions would be:
IF SY-UCOMM = 'DISPLAY'.
SELECT SINGLE * FROM ZKA_CENTER WHERE CENTERNO = ZKA_CENTER-CENTERNO.
ELSEIF SY-UCOMM ='SAVE'.
INSERT ZKA_CENTER.
ELSEIF SY-UCOMM = 'REFRESH'.
CLEAR ZKA_CENTER.
ELSEIF SY-UCOMM = 'GOTO'.
LEAVE TO SCREEN '0002'.
ELSEIF SY-UCOMM = 'EXIT'.
LEAVE PROGRAM.
ENDIF.
If u create many screens and need links between the screens then u can use GOTO to guide to the other screen.
SAVE, CHECK and ACTIVATE and click on TEST.
P.Naganjana Reddy
Now click on the DISPLAY button.
Also verify with SAVE, REFRESH and EXIT buttons. Thus the screen painter.
P.Naganjana Reddy
TABLE CONTROL
Basic form
CONTROLS ctrl TYPE TABLEVIEW USING SCREEN scr.
Effect
Creates a table control ctrl of the type TABLEVIEW . The reference screen for the initialization is the screen scr . Area of use The table control (referred to here as TC ) facilitates the display and entry of one-line, tabular data in dialog transactions. The functional scope has been defined so that you can implement many typical set operations usually handled by an elementary STEP-LOOP with the standard methods of a TC . Functional scope
Resizeable table grid for displaying and editing data.
Column width and column position modifiable by user and by program.
Storing and loading of user-specific column layout.
Selection column for line selection with color selection display.
Variable column headers as pushbuttons for column selection.
Simple selection, multiple selection, Select/deselect all.
Scrolling functions (horizontal and vertical) via scroll bar.
Fixing of any number of key columns.
Setting attributes for each cell at runtime.
Programming The data exchange between the application and the SAPgui is achieved with a STEP-LOOP , i.e. an ABAP/4 module is called to transfer data for each page.
Example
Processing without an internal table
PROCESS BEFORE OUTPUT.
LOOP WITH CONTROL ctrl.
MODULE ctrl_pbo.
ENDLOOP.
PROCESS AFTER INPUT.
LOOP WITH CONTROL ctrl.
MODULE ctrl_pai.
ENDLOOP.
In this case, the module ctrl_pbo OUTPUT is called once for each output line before the screen is displayed, in order to fill the output fields. After the user has entered data on the screen, the module ctrl_pai INPUT is executed to check the input and copy the new contents.
Example
Processing with an internal table
P.Naganjana Reddy
PROCESS BEFORE OUTPUT.
LOOP AT itab WITH CONTROL ctrl CURSOR ctrl-CURRENT_LINE.
ENDLOOP.
PROCESS AFTER INPUT.
LOOP AT itab WITH CONTROL ctrl.
MODULE ctrl_pai.
ENDLOOP.
Here, the system fills the output fields before displaying the screen by reading the internal table itab. When the user has entered data, the module ctrl_pai INPUT must be executed to check the input and to refresh the contents of the internal table. Vertical scrolling with the scroll bar is followed by the event PAI for the displayed page. Then, cntl-TOP_LINE is increased and PBO is processed for the next page. Program-driven scrolling and the most of the functionality described above is achieved by manipulating the control attributes.
Attributes The CONTROLS statement creates a complex data object of the type CXTAB_CONTROL with the name of the control. You maintain the initial values in the Screen Painter and assign the screen with the initial values for a control using the addition USING SCREEN . Initialization is achieved automatically in the "1st access to the control" (setting or reading values). You can use the customizing button (in the top right corner) to save the current setting (column widths and column positions) and use it as the initial value for the next call. All the initial values can be overwritten by the program using the MOVE ... TO TC attributes statement.
EXERCISE
Enter the Editor with SE38.
Declare the Tables and an internal table.
Then use the CONTROLS statement to have the controls for the Table control.
P.Naganjana Reddy
CONTROLS: <var> TYPE TABLEVIEW USING SCREEN '<screenno>'.
Now call the screen with the CALL SCREEN statement. Click on the screen to draw the table.
Fill in the attributes screen with the short description and click on the LAYOUT button.
Now click on the TABLE CONTROL button and draw the table to the size required. Double click on the table and enter the Attributes giving the Table-control name.
And select the check boxes for the vertical & horizontal resizing and separators.
Click on the DICTIONARY/PROGRAM FIELDS WINDOW F6 button. Type in the table name and click on GET FROM PROGRAM button and select the fields required for the screen and click on the COPY button.
P.Naganjana Reddy
Enter the header with the TEXT FIELDS button by double clicking on the TEXT FIELD and fill in the ATTRIBUTES button with the name and text.
P.Naganjana Reddy
SAVE, CHECK & ACTIVATE.
Click the BACK button and go the FLOW LOGIC screen.
P.Naganjana Reddy
REPORT ZKA_TC .
TABLES: ZKA_EMP.
DATA: ITAB LIKE ZKA_EMP OCCURS 0 WITH HEADER LINE.
CONTROLS: TC TYPE TABLEVIEW USING SCREEN '0001'.
CALL SCREEN '0001'.
*& Module STATUS_0001 OUTPUT
text
MODULE STATUS_0001 OUTPUT.
SET PF-STATUS 'xxxxxxxx'.
SET TITLEBAR 'xxx'.
SELECT * FROM ZKA_EMP INTO TABLE ITAB.
ENDMODULE. " STATUS_0001 OUTPUT
*& Module USER_COMMAND_0001 INPUT
P.Naganjana Reddy
text
MODULE USER_COMMAND_0001 INPUT.
IF SY-UCOMM = 'EXIT'.
LEAVE PROGRAM.
ENDIF.
ENDMODULE. " USER_COMMAND_0001 INPUT
P.Naganjana Reddy
TABSTRIP CONTROLS
A tabstrip control is a screen object consisting of two or more pages. Each tab page consists of a tab title and a page area. If the area occupied by the tabstrip control is too narrow to display all of the tab titles, a scrollbar appears, allowing you to reach the titles that are not displayed. There is also a pushbutton that allows you to display a list of all tab titles.
Tabstrip controls allow you to place a series of screens belonging to an application on a single screen, and to navigate between them easily. The recommended uses and ergonomic considerations for tabstrip controls are described in the Tabstrip Control section of the SAP Style Guide.
From a technical point of view, a tab page is a subscreen with a pushbutton assigned to it, which is displayed as the tab title.
The tabstrip control is the set of all the tab pages. Tabstrip controls are therefore subject to the same restrictions as subscreens. In particular, you cannot change the GUI status
P.Naganjana Reddy
when you switch between pages in the tabstrip control. However, they are fully integrated into the screen environment, so present no problems with batch input.
To use a tabstrip control on a screen, you must be using a SAPgui with Release 4.0 or higher, and its operating system must be Motif, Windows 95, MacOS, or Windows NT with version 3.51 or higher.
When you create a tabstrip control, you must:
Define the tab area on a screen and the tab titles.
Assign a subscreen area to each tab title.
Program the screen flow logic.
Program the ABAP processing logic.
You must then decide whether you want to page through the tabstrip control at the SAPgui or on the application server. In the first case, each tab page has its own subscreen. In the second, there is a single subscreen area that is shared by all tab pages.
Defining the Tabstrip Control Area and Tab Titles
You define both the tabstrip area and the tab titles in the screen layout. The tabstrip area has a unique name and a position, length, and height. You can also specify whether the tabstrip area can be resized vertically or horizontally when the user resizes the window. If the area supports resizing, you can specify a minimum size for it.
When you define a tabstrip area, it already has two tab titles. Tab titles are technically exactly the same as pushbuttons. To create additional tab titles, simple create pushbuttons in the row containing the tab titles. Tab titles have the same attributes as pushbuttons, that is, each has a name, a text, and a function code. You can also use icons and dynamic texts with tab titles.
Assigning a Subscreen Area to a Tab Title
You must assign a subscreen area to each tab title. There are two ways of doing this:
Paging in the SAPgui
You need to assign a separate subscreen area to each tab title, and define the function codes of the tab titles with type P (local GUI function). In the screen flow logic, you call all the subscreens in the PBO event. This means that all of the tab pages reside locally on the SAPgui.
When the user chooses a tab title, paging takes place within the SAPgui. In this respect, the tabstrip control behaves like a single screen. In particular, the PAI event is not triggered when the user chooses a tab title, and no data is transported. While this improves the performance of your tabstrip control, it also has the negative effect that when the user does trigger the PAI event, all of the input checks for all of the subscreens are performed. This means that when the user is working on one tab page, the input checks may jump to an unfilled mandatory field on another page.
P.Naganjana Reddy
Local paging at the SAPgui is therefore most appropriate for screens that display data rather than for input screens.
Paging on the Application Server
One subscreen area is shared by all tab titles and called in the PBO event. You define the function codes of the individual tab titles without a special function type. When the user chooses a tab page, the PAI event is triggered, and you must include a module in your flow logic that activates the appropriate tab page and assigns the correct subscreen to the subscreen area.
Since the PAI event is triggered each time the user chooses a tab title, this method is less economical for the application server, but the input checks that are performed only affect the current tab page.
Procedure in Either Case
You create the subscreen areas within the tabstrip area. You assign the subscreen areas to one or more tab titles in the Screen Painter by selecting one or more titles. You can also assign a subscreen area to a tab title in the tab title attributes by entering the name of the subscreen area in the Reference field attribute.
The procedure for the alphanumeric Screen Painter is described under Creating Tabstrip Controls.
If you are paging at the SAPgui, create a subscreen area for each tab title. If you are paging at the application server, select all tab titles and create a single subscreen area. The subscreen areas may not cover the top line of the tab area. However, within a tab area, more than one subscreen area can overlap.
Programming the Flow Logic
In the flow logic, all you have to do by hand is include the correct subscreens. The screen flow and data transport to the ABAP program is the same as for normal subscreens. There are two ways of programming the screen flow logic, depending on how you have decided to page through the tabstrip control.
Paging in the SAPgui
When you page in the SAPgui, you must include a subscreen for each subscreen area:
PROCESS BEFORE OUTPUT. ... CALL SUBSCREEN: <area1> INCLUDING [<prog 1>] <dynp 1>, <area2> INCLUDING [<prog 2>] <dynp 2>, <area3> INCLUDING [<prog 3>] <dynp 3>, ... ...
P.Naganjana Reddy
PROCESS AFTER INPUT. ... CALL SUBSCREEN: <area1>, <area2>, <area3>, ... ...
Paging on the Application Server
When you page on the application server, you only have to include a subscreen for the one subscreen area:
PROCESS BEFORE OUTPUT. ... CALL SUBSCREEN <area> INCLUDING [<prog>] <dynp>. ...
PROCESS AFTER INPUT. ... CALL SUBSCREEN <area>. ...
Handling in the ABAP Program
Before you can use a tabstrip control in your ABAP program, you must create a control for each control in the declaration part of your program using the following statement:
CONTROLS <ctrl> TYPE TABSTRIP.
where <ctrl> is the name of the tabstrip area on a screen in the ABAP program. The control allows the ABAP program to work with the tabstrip control. The statement declares a structure with the name <ctrl> . The only component of this structure that you need in your program is called ACTIVETAB.
Use in the PBO event
Before the screen is displayed, you use the control to set the tab page that is currently active. To do this, assign the function code of the corresponding tab title to the component ACTIVETAB:
<ctrl>-ACTIVETAB = <fcode>.
When you page at the SAPgui, you only need to do this once before the screen is displayed. This initializes the tabstrip control. The default active tab page is the first page. After this, the page activated when the user chooses a tab title is set within SAPgui.
When you page on the application server, you must assign the active page both before the screen is displayed for the first time, and each time the user pages. At the same time, you must set the required subscreen screen.
P.Naganjana Reddy
You can suppress a tab page dynamically by setting the ACTIVE field of table SCREEN to 0 for the corresponding tab title.
Use in the PAI event
In the PAI event, ACTIVETAB contains the function code of the last active tab title on the screen. When you page in the SAPgui, this allows you to find out the page that the user can currently see. When you page at the application server, the active tab page is controlled by the ABAP program anyway. The OK_CODE field behaves differently according to the paging method:
Paging in the SAPgui
When you page in the SAPgui, the PAI event is not triggered when the user chooses a tab title, and the OK_CODE field is not filled. The OK_CODE field is only filled by user actions in the GUI status or when the user chooses a pushbutton either outside the tabstrip control or on one of the subscreens.
Paging on the application server
If you are paging at the application server, the PAI event is triggered when the user chooses a tab title, and the OK_CODE field is filled with the corresponding function code. To page through the tabstrip control, you must assign the function code to the ACTIVETAB component of the control:
<ctrl>-ACTIVETAB = <ok_code>.
This statement overwrites the function code of the last active tab page with that of the new tab title. At the same time, you must ensure that the correct subscreen is inserted in the subscreen area. Otherwise, tabstrip controls are handled like normal subscrens in ABAP programs, that is, the ABAP program of a subscreen screen must contain the dialog modules called from the flow logic of the subscreen.
P.Naganjana Reddy
EXERCISE
Goto SE38. Enter the tabstrip program name Eg: ZKA_TABSTRIP and click on the create button.
First we need to declare the tables.
Then use the controls for the tabstrip.
Syntax: <ctrl-name> TYPE TASTRIP.
Now call the screen. Using CALL SCREEN statement.
Double click on the screen no to draw the screen for tabstrip control.
Now uncomment the FLOW LOGIC and click on the LAYOUT.
P.Naganjana Reddy
The flow logic for the tabstrip would be as follows.
PBO:
The PBO is initiated so that the subscreen for the corresponding tab can be maintained.
Syntax:
CALL SUBSCREEEN <sub-screen name> INCLUDING SY-REPID <screen-var>.
PAI:
When the tab is clicked, the corresponding subscren should open
Syntax:
CALL SUBSCREEN <subscreen>.
P.Naganjana Reddy
DRAWING THE TABSTRIP CONTROL:
Click on the TABSTRIP button and place it on the screen for the required size.
Double click on the control and give the name for the tabstrip control in the ATTRIBUTES screen.
Now double click on the tab and fill in the attributes screen for the name and the text.
Also draw the subscreen in one of the tab and refer the same subscreen in the rest of the tabs.
P.Naganjana Reddy
Now in the sub-screens, we need to get the screen for the tabs.
So call an other screen and draw with fields and pushbuttons to perform actions very similar like SCREEN WITH FIELDS (refer screen painter).
Enter the short description and click on the FLOW LOGIC tab.
P.Naganjana Reddy
Uncomment the flow logic, both PAI and PBO.
Now click on the LAYOUT button.
Naganjana Reddy.P
Click on the DICTIONARY/PROGRAM FIELDS WINDOW F6 button. Type in the table name and click on GET FROM DIC button and select the fields required for the screen and click on the COPY button.
Now drag and place the INPUT/OUTPUT fields box on the screen.
P.Naganjana Reddy
Now click on the TEXT FIELD button and place in the screen and stretch the box for the size required. Now double click on the box, U will get the attributes screen. Enter the name and Text for the field.
Now we need to place the bush buttons. So Click on the push button on the left side and place it on the screen. Double click on it, u will get the attributes screen. Enter the name, text and the icon required and mainly the FCTCODE. It is the one which links the screen painter with the code.
P.Naganjana Reddy
Once everything is set up, SAVE, CHECK and ACTIVATE the screen.
P.Naganjana Reddy
Click on the BACK button. U will be guided to the FLOW LOGIC screen.
Double click on PAI, Because for the screen painter with the fields, Process After the Input is done and so u will guided to the Editor screen.
P.Naganjana Reddy
Now we need to set the System-Uses commands which links the code to the Editor.
So the conditions would be:
IF SY-UCOMM = 'DISPLAY'.
SELECT SINGLE * FROM ZKA_CENTER WHERE CENTERNO = ZKA_CENTER-CENTERNO.
ELSEIF SY-UCOMM ='SAVE'.
INSERT ZKA_CENTER.
ELSEIF SY-UCOMM = 'REFRESH'.
CLEAR ZKA_CENTER.
ELSEIF SY-UCOMM = 'GOTO'.
LEAVE TO SCREEN '0002'.
ELSEIF SY-UCOMM = 'EXIT'.
LEAVE PROGRAM.
ENDIF.
The same procedure for the company table as well will lead the screen in the below manner.
P.Naganjana Reddy
Summary:
REPORT ZKA_TABSTRIP .
TABLES: ZKA_EMP,ZKA_COM.
CONTROLS: TS TYPE TABSTRIP..
DATA: SCREENNO(4) TYPE N.
CALL SCREEN '0003'.
*& Module STATUS_0001 OUTPUT
text
MODULE STATUS_0001 OUTPUT.
SET PF-STATUS 'xxxxxxxx'.
SET TITLEBAR 'xxx'.
IF SCREENNO IS INITIAL.
TS-ACTIVETAB = 'EMP'.
SCREENNO = '0002'.
ENDIF.
ENDMODULE. " STATUS_0001 OUTPUT
*& Module USER_COMMAND_0001 INPUT
text
MODULE USER_COMMAND_0001 INPUT.
IF SY-UCOMM = 'EMP'.
TS-ACTIVETAB = 'EMP'.
SCREENNO = '0002'.
ELSEIF SY-UCOMM = 'COM'.
TS-ACTIVETAB = 'COM'.
SCREENNO = '0003'.
ENDIF.
ENDMODULE. " USER_COMMAND_0001 INPUT
*& Module USER_COMMAND_0002 INPUT
text
MODULE USER_COMMAND_0002 INPUT.
IF SY-UCOMM = 'DISPLAY'.
SELECT SINGLE * FROM ZKA_EMP WHERE EMPNO = ZKA_EMP-EMPNO.
ELSEIF SY-UCOMM = 'SAVE'.
INSERT ZKA_EMP.
ELSEIF SY-UCOMM = 'REFRESH'.
CLEAR ZKA_EMP.
ELSEIF SY-UCOMM = 'EXIT'.
LEAVE PROGRAM.
ENDIF.
P.Naganjana Reddy

How to call module pool through interactive ALV

Moderator message: do not post in ALL CAPITALS.
Hi all,
I want to create an interactive report in which some parameters on selection-screen when i fill those & press f8 then an alv list is generated from ddic and when user double click on any row then a tcode get call which call a module pool program how can i do so please help me for that
Ketan pande
Abap consultant.
Edited by: Matt on Feb 13, 2009 1:33 PM - Switched to sentence case
Edited by: Matt on Feb 13, 2009 1:34 PM

Modify this code to add Hot spots or double click action.
This code will dynamically list the data of any DB table.
REPORT yptc_dynamic_alv_table_display .
TABLES: dd02t.
TYPE-POOLS: slis. " ALV Global Types*data declaration for dynamic
* internal table and alv
DATA: l_structure TYPE REF TO data,
 l_table TYPE REF TO data,
 struc_desc TYPE REF TO cl_abap_structdescr,
 lt_layout TYPE slis_layout_alv,
 ls_lvc_fieldcatalogue TYPE lvc_s_fcat,
 lt_lvc_fieldcatalogue TYPE lvc_t_fcat,
 ls_fieldcatalogue TYPE slis_fieldcat_alv,
 lt_fieldcatalogue TYPE slis_t_fieldcat_alv,
 g_repid LIKE sy-repid,
 g_list_top_of_page TYPE slis_t_listheader,
 g_events TYPE slis_t_event,
 g_events_ex TYPE slis_t_event_exit.
*field symbols declaration
FIELD-SYMBOLS :
<it_table> TYPE STANDARD TABLE,
<dyn_str> TYPE ANY,
<str_comp> TYPE abap_compdescr.
*declarations for grid title
DATA : t1(30),
 t2(10),
 t3(50).
*selection screen declaration for table input
PARAMETERS : p_table LIKE dd02l-tabname.
*initialization event
INITIALIZATION.
*start of selection event
START-OF-SELECTION.
*texts for grid title
t1 = 'Dynamic ALV display for table'.
t2 = p_table. CONCATENATE t1 t2 INTO t3 SEPARATED BY space.
* dynamic creation of a structure
CREATE DATA l_structure TYPE (p_table).
ASSIGN l_structure->* TO <dyn_str>.
* fields structure
struc_desc ?= cl_abap_typedescr=>describe_by_data( <dyn_str> ).
LOOP AT struc_desc->components ASSIGNING <str_comp>.
* build fieldcatalog
 ls_lvc_fieldcatalogue-fieldname = <str_comp>-name.
 ls_lvc_fieldcatalogue-ref_table = p_table.
 APPEND ls_lvc_fieldcatalogue TO lt_lvc_fieldcatalogue.
* build fieldcatalog
 ls_fieldcatalogue-fieldname = <str_comp>-name.
 ls_fieldcatalogue-ref_tabname = p_table.
 APPEND ls_fieldcatalogue TO lt_fieldcatalogue.
ENDLOOP.
* create internal table dynamic
CALL METHOD cl_alv_table_create=>create_dynamic_table
 EXPORTING
 it_fieldcatalog = lt_lvc_fieldcatalogue
 IMPORTING
 ep_table = l_table.
ASSIGN l_table->* TO <it_table>.
* read data from the table selected.
SELECT * FROM (p_table)
 INTO CORRESPONDING FIELDS OF TABLE <it_table>.
* alv layout
lt_layout-zebra = 'X'.
lt_layout-colwidth_optimize = 'X'.
lt_layout-window_titlebar = t3.
* Events
PERFORM eventtab_build USING g_events[]
 g_events_ex[].
g_repid = sy-repid.
*alv output
CALL FUNCTION 'REUSE_ALV_GRID_DISPLAY'
 EXPORTING
 i_callback_program = g_repid
 is_layout = lt_layout
 it_fieldcat = lt_fieldcatalogue
 it_events = g_events[]
* it_excluding = g_exclude
 TABLES
 t_outtab = <it_table>
 EXCEPTIONS
 program_error = 1
 OTHERS = 2.
IF sy-subrc NE 0.
* MESSAGE ID sy-msgid TYPE sy-msgty NUMBER sy-msgno
* WITH sy-msgv1 sy-msgv2 sy-msgv3 sy-msgv4.
ENDIF.
* FORM eventtab_build *
FORM eventtab_build
 USING e03_lt_events TYPE slis_t_event
 e03_lt_events_ex TYPE slis_t_event_exit.
CONSTANTS:
 gc_formname_top_of_page TYPE slis_formname VALUE 'TOP_OF_PAGE',
 gc_formname_user_command TYPE slis_formname VALUE 'USER_COMMAND'.
DATA: ls_event TYPE slis_alv_event,
 ls_event_exit LIKE LINE OF e03_lt_events_ex.
CALL FUNCTION 'REUSE_ALV_EVENTS_GET'
 EXPORTING
 i_list_type = 1
 IMPORTING
 et_events = e03_lt_events.
READ TABLE e03_lt_events
 WITH KEY name = slis_ev_top_of_page
 INTO ls_event.
IF sy-subrc = 0.
 MOVE gc_formname_top_of_page TO ls_event-form.
 APPEND ls_event TO e03_lt_events.
ENDIF.
ENDFORM. " build_events_table
* FORM top_of_page *
FORM top_of_page.
DATA: ls_line TYPE slis_listheader.
SELECT SINGLE * FROM dd02t
 WHERE tabname = p_table
 AND ddlanguage = sy-langu.
CLEAR g_list_top_of_page[].
CLEAR ls_line.
ls_line-typ = 'H'.
CONCATENATE p_table '-' dd02t-ddtext INTO ls_line-info
 SEPARATED BY space.
* ls_line-info = p_table.
APPEND ls_line TO g_list_top_of_page.
PERFORM build_sub_headings
 USING g_list_top_of_page.
CALL FUNCTION 'REUSE_ALV_COMMENTARY_WRITE'
 EXPORTING
 it_list_commentary = g_list_top_of_page[].
ENDFORM. " top_of_page
* FORM build_sub_headings *
* --> E07_TOP_OF_PAGE *
FORM build_sub_headings
 USING e07_top_of_page TYPE slis_t_listheader.
DATA: ls_line TYPE slis_listheader.
CLEAR ls_line.
ls_line-typ = 'S'.
ls_line-key = 'Run Info'.
CONCATENATE sy-sysid sy-uname sy-mandt
 INTO ls_line-info
 SEPARATED BY space.
APPEND ls_line TO e07_top_of_page.
ENDFORM. "build_sub_headings

Debugging a Module Pool Program(Object Oriented ABAP)

Hello Experts,
Could you please advise me on an efficient debugging technoque of Module Pool Program which is based on Object Oriented ABAP?

Hi
Debugging Module pool program using ABAP objects is same as debugging any other report/module pool program.
Click on the Create shortcut icon on the toolbar.
In the popup window choose "System command" and in the command enter "/h"
A shortcut on the desktop would be created
Drag and drop the shortcut to the modal window to set debugging on.
Approach 2:
Create a txt file on the desktop with the following lines:
[FUNCTION]
Command=/H
Title=Debugger
Type=SystemCommandDrag and drop this file to the modal window to set debugging on.
How do I switch between the Classic and New Debugger
From within the ABAP workbench, select the Utilities->Settings Menu
Select the ABAP Editor Tab
Select the Debugging tab within the ABAP Editor Tab
Select the Classic Debugger or New Debugger radio button
Refer to this thread
http://help.sap.com/saphelp_47x200/helpdata/en/c6/617ca9e68c11d2b2ab080009b43351/content.htm
Debugging
Check these documents.
http://www.cba.nau.edu/haney-j/CIS497/Assignments/Debugging.doc
http://help.sap.com/saphelp_nw04/helpdata/en/5a/4ed93f130f9215e10000000a155106/frameset.htm
http://help.sap.com/saphelp_47x200/helpdata/en/c6/617ca9e68c11d2b2ab080009b43351/content.htm
http://www.cba.nau.edu/haney-j/CIS497/Assignments/Debugging.doc
http://help.sap.com/saphelp_erp2005/helpdata/en/b3/d322540c3beb4ba53795784eebb680/frameset.htm
http://help.sap.com/saphelp_nw04/helpdata/en/84/1f624f4505144199e3d570cf7a9225/frameset.htm
http://help.sap.com/saphelp_bw30b/helpdata/en/c6/617ca9e68c11d2b2ab080009b43351/content.htm
http://help.sap.com/saphelp_erp2005/helpdata/en/b3/d322540c3beb4ba53795784eebb680/frameset.htm
ABAP Debugging
http://www.saplinks.net/index.php?option=com_content&task=view&id=24&Itemid=34
Look at the SAP help link below
http://help.sap.com/saphelp_nw2004s/helpdata/en/c6/617ca9e68c11d2b2ab080009b43351/content.htm
Reward points if useful
Regards
Anji

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 raise pop up window along with radio buttons in module pool program

how to raise pop up window along with radio buttons in module pool program

FUNCTION zscheme_determination.
*"*"Local Interface:
*" IMPORTING
*"     REFERENCE(I_KUNNR) TYPE KUNNR
*" EXPORTING
*"     REFERENCE(E_VALUE) TYPE NETWR_AK
*" TABLES
*"      G_ITEM_DATA_ITAB STRUCTURE ZITEM_DATA
* TYPES: BEGIN OF ty_sord,
*         include type ZSD_SCHEME_DTL,
*         END   OF ty_sord.
* data : gt_sord type standard table of ZSD_SCHEME_DTL,
*         wa_sord type ZSD_SCHEME_DTL.
* select * from ZSD_SCHEME_DTL into table
* gt_sord
* where matnr = i_matnr.
* T_ITEM_DATA
*********Data Declarations
   DATA:
         salesdocumentin LIKE bapivbeln-vbeln,
         orderheaderin LIKE bapisdhd1,
         orderheaderinx LIKE bapisdhd1x,
         sender LIKE bapi_sender,
         binaryrelationshiptype LIKE bapireltype-reltype,
         intnumberassignment LIKE bapiflag-bapiflag,
         behavewhenerror LIKE bapiflag-bapiflag,
         logicswitch LIKE bapisdls,
         testrun LIKE bapiflag-bapiflag,
         convert LIKE bapiflag-bapiflag,
         return LIKE bapiret2 OCCURS 0,
         orderitemsin LIKE bapisditm OCCURS 0,
         orderitemsinx LIKE bapisditmx OCCURS 0,
         orderpartners LIKE bapiparnr OCCURS 0,
         orderschedulesin LIKE bapischdl OCCURS 0,
         orderschedulesinx LIKE bapischdlx OCCURS 0,
         orderconditionsin LIKE bapicond OCCURS 0,
         orderconditionsinx LIKE bapicondx OCCURS 0,
         ordercfgsref LIKE bapicucfg OCCURS 0,
         ordercfgsinst LIKE bapicuins OCCURS 0,
         ordercfgspartof LIKE bapicuprt OCCURS 0,
         ordercfgsvalue LIKE bapicuval OCCURS 0,
         ordercfgsblob LIKE bapicublb OCCURS 0,
         ordercfgsvk LIKE bapicuvk OCCURS 0,
         ordercfgsrefinst LIKE bapicuref OCCURS 0,
         orderccard LIKE bapiccard OCCURS 0,
         ordertext LIKE bapisdtext OCCURS 0,
         orderkeys LIKE bapisdkey OCCURS 0,
         extensionin LIKE bapiparex OCCURS 0,
         partneraddresses LIKE bapiaddr1 OCCURS 0.
   DATA : wa_orderpartners LIKE bapiparnr,
          wa_orderitemsin LIKE bapisditm,
          wa_orderitemsinx LIKE bapisditmx,
          wa_orderschedulesin LIKE bapischdl,
          wa_orderschedulesinx LIKE bapischdlx,
          wa_orderconditionsin LIKE bapicond,
          wa_orderconditionsinx LIKE bapicondx,
          wa_return LIKE bapiret2,
          lv_value TYPE netwr_ak.
   DATA : lv_dtyp TYPE char45,
          lv_sorg TYPE vkorg,
          lv_sdch TYPE vtweg,
          lv_sdiv TYPE spart.
   TYPES : BEGIN OF ty_sord,
           zsdscheme TYPE comt_scheme_id,
           posnr TYPE posnr_va,
           matnr TYPE matnr,
           disc_type TYPE rebate_disc_type,
           calc_type TYPE catyp,
           qty_from TYPE kwmeng,
           qty_to TYPE kwmeng,
           spart TYPE spart,
           custcondgrp TYPE kdkg1,
           werks TYPE werks_d,
           matmn TYPE matnr,
           END   OF ty_sord.
   DATA : gt_sord   TYPE STANDARD TABLE OF ty_sord,
          gt_sordd TYPE STANDARD TABLE OF ty_sord,
          wa_sord TYPE ty_sord,
          wa_knvv TYPE knvv,
          lv_cal_foc TYPE p DECIMALS 3,
          lv_cal_dis TYPE p DECIMALS 3,
          lv_new_qty TYPE kwmeng,
          lv_posmat TYPE posnr_va,
          lv_posfoc TYPE posnr_va.
   DATA:lv_diff TYPE kwmeng.
******Schemes Selection Logic
* Get Valid Schemes
* Validate Scheme for validity Period, Material, Customer Type and Plant
   TYPES : BEGIN OF ty_rtab,
           sign   TYPE c LENGTH 1,
           option TYPE c LENGTH 2,
           low    LIKE mara-matnr,
           high   LIKE mara-matnr,
         END OF ty_rtab.
* TYPES : ty_matnr TYPE RANGE OF ty_rtab.
   DATA : it_matnr TYPE TABLE OF ty_rtab,
          wa_matnr TYPE ty_rtab,
          wa_it    TYPE zitem_data,
         wa_tab TYPE zitem_data.
*order table declaration
   TYPES:
         BEGIN OF ty_order,
           zsdscheme TYPE comt_scheme_id,
           matnr     TYPE matnr,
           kwmeng    TYPE kwmeng,
         END OF ty_order,
   BEGIN OF ty_scheme,
    zsdscheme TYPE comt_scheme_id,
*                matnr     TYPE matnr,
    kwmeng    TYPE kwmeng,
END OF ty_scheme.
   DATA:
         gt_order      TYPE TABLE OF ty_order,
         gt_scheme     TYPE TABLE OF ty_scheme,
          wa_scheme    TYPE ty_scheme,
          wa_order     TYPE ty_order.
   DATA:i_kwmeng TYPE kwmeng.
* Transfer all the material received from order to internal table
   LOOP AT g_item_data_itab INTO wa_it.
     MOVE : wa_it-matnr TO wa_matnr-low,
            'I'          TO wa_matnr-sign,
            'EQ'         TO wa_matnr-option.
     APPEND wa_matnr TO it_matnr.
     CLEAR wa_it.
   ENDLOOP.
* Get the Valid Schemes based on given criteria
   SELECT
           zsd_scheme_dtl~zsdscheme
           zsd_scheme_dtl~posnr
           zsd_scheme_dtl~matnr
           zsd_scheme_dtl~disc_type
           zsd_scheme_dtl~calc_type
           zsd_scheme_dtl~qty_from
           zsd_scheme_dtl~qty_to
           zsd_scheme~spart
           zsd_scheme_hdr~custcondgrp
           zsd_scheme_hdr~werks
           zsd_scheme_hdr~matnr
   FROM zsd_scheme_hdr
   INNER JOIN zsd_scheme ON zsd_scheme~zsdscheme = zsd_scheme_hdr~zsdscheme
   INNER JOIN zsd_scheme_dtl ON zsd_scheme_dtl~zsdscheme = zsd_scheme_hdr~zsdscheme
   INTO TABLE gt_sord
   WHERE zsd_scheme_dtl~matnr IN it_matnr
*    zsd_scheme_hdr~matnr IN it_matnr
*    AND zsd_scheme_hdr~werks = '1509'
     AND zsd_scheme_hdr~werks = '1529'
     AND zsd_scheme_hdr~custcondgrp = '01'
     AND zsd_scheme~datuv LE sy-datum
     AND zsd_scheme~datub GE sy-datum.
   SORT gt_sord BY zsdscheme ASCENDING.
* LOOP AT gt_sord INTO wa_sord.
*    READ TABLE g_item_data_itab INTO wa_it WITH KEY matnr = wa_sord-matnr.
*    wa_order-zsdscheme = wa_sord-zsdscheme.
*    wa_order-matnr = wa_it-matnr.
*    wa_order-kwmeng = wa_it-kwmeng.
*    COLLECT wa_order INTO gt_order.
*    CLEAR wa_order.
* ENDLOOP.
   LOOP AT g_item_data_itab INTO wa_it.
     READ TABLE gt_sord INTO wa_sord WITH KEY matnr = wa_it-matnr.
     wa_order-zsdscheme = wa_sord-zsdscheme.
     wa_order-matnr = wa_it-matnr.
     wa_order-kwmeng = wa_it-kwmeng.
     COLLECT wa_order INTO gt_order.
     MOVE : wa_sord-zsdscheme TO wa_scheme-zsdscheme,
            wa_it-kwmeng TO wa_scheme-kwmeng.
     COLLECT wa_scheme INTO gt_scheme.
     CLEAR : wa_order, wa_scheme.
   ENDLOOP.
   CLEAR wa_scheme.
   DATA w_line TYPE sy-tabix.
* Updating table based on Schemes
   LOOP AT gt_scheme INTO wa_scheme.
     CLEAR w_line.
     gt_sordd[] = gt_sord[].
*    DELETE gt_sordd WHERE zsdscheme NE wa_scheme-zsdscheme and disc_type NE 'FOC'.
     DELETE gt_sordd WHERE zsdscheme NE wa_scheme-zsdscheme AND disc_type NE 'F'.
     DELETE ADJACENT DUPLICATES FROM gt_sordd COMPARING zsdscheme matnr.
     DESCRIBE TABLE gt_sordd LINES w_line.
     IF w_line GT 1.
* popup message to select one foc type.
     ELSE.
       CLEAR wa_sord.
       READ TABLE gt_sordd INTO wa_sord INDEX 1.
       IF sy-subrc EQ 0.
         i_kwmeng = wa_scheme-kwmeng.
         lv_cal_foc = i_kwmeng DIV wa_sord-qty_from.
         lv_cal_dis = i_kwmeng MOD wa_sord-qty_from.
         MOVE : lv_cal_foc TO wa_it-kwmeng,
                wa_sord-matnr TO wa_it-matnr.
         APPEND wa_it TO g_item_data_itab.
         SORT gt_order BY kwmeng DESCENDING.
         LOOP AT gt_order INTO wa_order WHERE zsdscheme = wa_scheme-zsdscheme.
           IF lv_cal_dis GT 0.
*        LOOP AT gt_order INTO wa_order WHERE zsdscheme = wa_scheme-zsdscheme
*                                             AND lv_cal_dis GT 0.
*                  LOOP AT gt_order INTO wa_order WHERE zsdscheme = wa_scheme-zsdscheme.
*                LOOP AT g_item_data INTO wa_item_data WHERE matnr EQ wa_order-matnr.
                     LOOP AT g_item_data_itab INTO wa_tab WHERE matnr EQ wa_order-matnr.
                       wa_orderconditionsin-itm_number = wa_tab-posnr.
*                  wa_orderconditionsin-itm_number = wa_item_data-posnr.
                       wa_orderconditionsin-cond_st_no = '001'.
*                  IF gt_sordd-calc EQ ‘post AND disc_type EQ ‘percentage’.
                       IF wa_sord-calc_type EQ 'O' AND wa_sord-disc_type EQ 'P'.
                         wa_orderconditionsin-cond_type = 'ZTPB'.   "'ZREG'.
*                  ELSEIF gt_sordd-calc EQ ‘pre’ AND disc_type EQ ‘percentage’
                       ELSEIF wa_sord-calc_type EQ 'E' AND wa_sord-disc_type EQ 'P'.
                         wa_orderconditionsin-cond_type = 'ZTPP'.   "'ZREG'.
                       ENDIF.
                       wa_orderconditionsin-currency = 'INR'.
                       wa_orderconditionsin-conpricdat = sy-datum.
                       APPEND wa_orderconditionsin TO orderconditionsin.
                       CLEAR wa_orderconditionsin.
*Update Discount Conditon
                     ENDLOOP.
*                  ENDLOOP.
*Modify balance of Item
             CLEAR wa_tab.
             READ TABLE g_item_data_itab INTO wa_tab WITH KEY matnr = wa_order-matnr.
             IF sy-subrc EQ 0.
               lv_diff = wa_tab-kwmeng - lv_cal_dis.
               IF lv_diff GT 0.
                 wa_tab-kwmeng = wa_tab-kwmeng - lv_cal_dis.
*            MODIFY g_item_data TRANSPORTING kwmeng index sy-tabix.
                 MODIFY g_item_data_itab INDEX sy-tabix FROM wa_tab TRANSPORTING kwmeng .
               ELSE.
                 wa_tab-kwmeng = lv_cal_dis.
                 lv_cal_dis = lv_diff.
                 MODIFY g_item_data_itab INDEX sy-tabix FROM wa_tab TRANSPORTING kwmeng .
*            MODIFY G_ITEM_DATA_ITAB TRANSPORTING kwmeng index sy-tabix.
               ENDIF.
               gt_sordd[] = gt_sord[].
               DELETE gt_sordd WHERE zsdscheme NE wa_scheme-zsdscheme AND disc_type EQ 'F'.
               DESCRIBE TABLE gt_sordd LINES w_line.
               IF w_line GT 1.
                 SORT gt_sordd BY zsdscheme DESCENDING.
*              SORT gt_sordd BY quantity DESCENDING.
                 CLEAR wa_sord.
*              LOOP AT gt_sordd WHERE quantity_from LT wa_shceme-kwmeng AND quantity_to GT wa_shceme-kwmeng.
                 LOOP AT gt_sordd INTO wa_sord WHERE qty_from LT wa_scheme-kwmeng AND qty_to GT wa_scheme-kwmeng.
*             LOOP AT gt_order INTO wa_order WHERE scheme = wa_scheme-scheme.
                   LOOP AT gt_order INTO wa_order WHERE zsdscheme = wa_scheme-zsdscheme.
*                LOOP AT g_item_data INTO wa_item_data WHERE matnr EQ wa_order-matnr.
                     LOOP AT g_item_data_itab INTO wa_tab WHERE matnr EQ wa_order-matnr.
                       wa_orderconditionsin-itm_number = wa_tab-posnr.
*                  wa_orderconditionsin-itm_number = wa_item_data-posnr.
                       wa_orderconditionsin-cond_st_no = '001'.
*                  IF gt_sordd-calc EQ ‘post AND disc_type EQ ‘percentage’.
                       IF wa_sord-calc_type EQ 'O' AND wa_sord-disc_type EQ 'P'.
                         wa_orderconditionsin-cond_type = 'ZDPD'.   "'ZREG'.
*                  ELSEIF gt_sordd-calc EQ ‘pre’ AND disc_type EQ ‘percentage’
                       ELSEIF wa_sord-calc_type EQ 'E' AND wa_sord-disc_type EQ 'P'.
                         wa_orderconditionsin-cond_type = 'ZDPD'.   "'ZREG'.
                       ENDIF.
                       wa_orderconditionsin-currency = 'INR'.
                       wa_orderconditionsin-conpricdat = sy-datum.
                       APPEND wa_orderconditionsin TO orderconditionsin.
                       CLEAR wa_orderconditionsin.
*Update Discount Conditon
                     ENDLOOP.
                   ENDLOOP.
                 ENDLOOP.
               ELSE.
               ENDIF.
             ENDIF.
           ENDIF.
         ENDLOOP.
       ENDIF.
     ENDIF.
   ENDLOOP.
* select
*          ZSD_SCHEME_DTL~ZSDSCHEME
*          ZSD_SCHEME_DTL~POSNR
*          ZSD_SCHEME_DTL~matnr
*          ZSD_SCHEME_DTL~DISC_TYPE
*          ZSD_SCHEME_DTL~CALC_TYPE
*          ZSD_SCHEME_DTL~QTY_FROM
*          ZSD_SCHEME_DTL~QTY_TO
*          ZSD_SCHEME~SPART
*          ZSD_SCHEME_HDR~CUSTCONDGRP
*          ZSD_SCHEME_HDR~WERKS
*          ZSD_SCHEME_HDR~MATNR
* from ZSD_SCHEME_DTL
* inner join ZSD_SCHEME on ZSD_SCHEME~ZSDSCHEME = ZSD_SCHEME_DTL~ZSDSCHEME
* inner join ZSD_SCHEME_HDR on ZSD_SCHEME_HDR~ZSDSCHEME = ZSD_SCHEME_DTL~ZSDSCHEME
* into table
* gt_sord
* where ZSD_SCHEME_DTL~matnr = i_matnr and
*        ZSD_SCHEME~DATUV LE sy-datum and
*        ZSD_SCHEME~DATUB GE sy-datum.
* break-point.
* Process Common Logic for Schemes Processcing
   CLEAR wa_sord.
* Convert FOC Quantity and Materials
* LOOP AT gt_sord INTO wa_sord.
**   lv_cal = i_kwmeng / wa_sord-QTY_FROM.
*    lv_cal_foc = i_kwmeng DIV wa_sord-qty_from.
*    lv_cal_dis = i_kwmeng MOD wa_sord-qty_from.
* ENDLOOP.
*lv_new_qty = i_kwmeng - lv_cal_dis.
* Get the Sales Document Type
   SELECT SINGLE low
FROM tvarvc
INTO lv_dtyp WHERE
name = 'SD_DOC_TYPE'.
   SELECT SINGLE * FROM knvv INTO wa_knvv WHERE kunnr = i_kunnr.
   IF sy-subrc = 0.
     lv_sorg = wa_knvv-vkorg.
     lv_sdch = wa_knvv-vtweg.
     lv_sdiv = wa_knvv-spart.
   ENDIF.
* Give the Popup for schemes with multiple FOC
* Schemes Specific Processing
* Schemes Specific Processing
   orderheaderin-doc_type = lv_dtyp.
   orderheaderin-sales_org = lv_sorg.
   orderheaderin-distr_chan = lv_sdch.
   orderheaderin-division = lv_sdiv.
   wa_orderpartners-partn_role = 'AG'.
   wa_orderpartners-partn_numb = i_kunnr.
   APPEND wa_orderpartners TO orderpartners.
*    wa_ORDERPARTNERS-PARTN_ROLE = 'WE'.
*    wa_ORDERPARTNERS-PARTN_NUMB = p_ship.
*    append wa_ORDERPARTNERS to ORDERPARTNERS.
* Item number begin
   CLEAR : lv_posmat.
   lv_posmat = lv_posmat + 10.
   wa_orderitemsin-itm_number = lv_posmat.
   wa_orderitemsin-material = wa_sord-matmn. "i_matnr.
   wa_orderitemsin-target_qty = lv_new_qty.
* wa_ORDERITEMSIN-TARGET_QU = i_VRKME.
   APPEND wa_orderitemsin TO orderitemsin.
   wa_orderitemsinx-itm_number = lv_posmat.
   wa_orderitemsinx-material = 'X'.
   wa_orderitemsinx-target_qty = 'X'.
   wa_orderitemsinx-target_qu = 'X'.
   APPEND wa_orderitemsinx TO orderitemsinx.
   wa_orderschedulesin-itm_number = lv_posmat.
   wa_orderschedulesin-sched_line = lv_posmat.
   wa_orderschedulesin-req_qty = lv_new_qty.
   APPEND wa_orderschedulesin TO orderschedulesin.
   wa_orderschedulesinx-itm_number = lv_posmat.
   wa_orderschedulesinx-sched_line = lv_posmat.
   wa_orderschedulesinx-req_qty = 'X'.
   wa_orderschedulesinx-updateflag = 'X'.
   APPEND wa_orderschedulesinx TO orderschedulesinx.
   wa_orderconditionsin-itm_number = lv_posmat.
   wa_orderconditionsin-cond_st_no = '001'.
   wa_orderconditionsin-cond_type = 'ZDPD'.   "'ZREG'.
   wa_orderconditionsin-currency = 'INR'.
   wa_orderconditionsin-conpricdat = sy-datum.
   APPEND wa_orderconditionsin TO orderconditionsin.
   wa_orderconditionsinx-itm_number = lv_posmat.
   wa_orderconditionsinx-cond_st_no = '001'.
   wa_orderconditionsinx-cond_type = 'ZDPD'. "'ZREG'.
   wa_orderconditionsinx-updateflag = 'X'.
   wa_orderconditionsinx-cond_value ='X'.
   wa_orderconditionsinx-currency = 'X'.
   APPEND wa_orderconditionsinx TO orderconditionsinx.
****18/06Beg
* if not lv_cal_dis is initial.
*    lv_posmat = lv_posmat + 10.
*    wa_ORDERITEMSIN-ITM_NUMBER = lv_posmat.
*    wa_ORDERITEMSIN-MATERIAL = WA_SORD-MATMN. "i_matnr.
*    wa_ORDERITEMSIN-TARGET_QTY = lv_cal_dis.
** wa_ORDERITEMSIN-TARGET_QU = i_VRKME.
*    append wa_ORDERITEMSIN to ORDERITEMSIN.
*    wa_ORDERITEMSINX-ITM_NUMBER = lv_posmat.
*    wa_ORDERITEMSINX-MATERIAL = 'X'.
*    wa_ORDERITEMSINX-TARGET_QTY = 'X'.
*    wa_ORDERITEMSINX-TARGET_QU = 'X'.
*    append wa_ORDERITEMSINX to ORDERITEMSINX.
*    wa_ORDERSCHEDULESIN-ITM_NUMBER = lv_posmat.
*    wa_ORDERSCHEDULESIN-SCHED_LINE = lv_posmat.
*    wa_ORDERSCHEDULESIN-REQ_QTY = lv_cal_dis.
*    append wa_ORDERSCHEDULESIN to ORDERSCHEDULESIN.
*    wa_ORDERSCHEDULESINX-itm_number = lv_posmat.
*    wa_ORDERSCHEDULESINX-sched_line = lv_posmat.
*    wa_ORDERSCHEDULESINX-req_qty = 'X'.
*    wa_ORDERSCHEDULESINX-updateflag = 'X'.
*    append wa_ORDERSCHEDULESINX to ORDERSCHEDULESINX.
* endif.
* lv_posmat = lv_posmat + 10.
* wa_ORDERITEMSIN-ITM_NUMBER = lv_posmat.
* wa_ORDERITEMSIN-MATERIAL = i_matnr. "WA_SORD-MATMN.
* wa_ORDERITEMSIN-TARGET_QTY = LV_CAL_FOC.
* wa_ORDERITEMSIN-ITEM_CATEG = 'ZDGN'.
** wa_ORDERITEMSIN-TARGET_QU = i_VRKME.
* append wa_ORDERITEMSIN to ORDERITEMSIN.
* wa_ORDERITEMSINX-ITM_NUMBER = lv_posmat.
* wa_ORDERITEMSINX-MATERIAL = 'X'.
* wa_ORDERITEMSINX-TARGET_QTY = 'X'.
* wa_ORDERITEMSINX-TARGET_QU = 'X'.
* wa_ORDERITEMSINX-ITEM_CATEG = 'X'.
* append wa_ORDERITEMSINX to ORDERITEMSINX.
* wa_ORDERSCHEDULESIN-ITM_NUMBER = lv_posmat.
* wa_ORDERSCHEDULESIN-SCHED_LINE = lv_posmat.
* wa_ORDERSCHEDULESIN-REQ_QTY = LV_CAL_FOC.
* append wa_ORDERSCHEDULESIN to ORDERSCHEDULESIN.
* wa_ORDERSCHEDULESINX-itm_number = lv_posmat.
* wa_ORDERSCHEDULESINX-sched_line = lv_posmat.
* wa_ORDERSCHEDULESINX-req_qty = 'X'.
* wa_ORDERSCHEDULESINX-updateflag = 'X'.
* append wa_ORDERSCHEDULESINX to ORDERSCHEDULESINX.
****18/06End
* Item number end
* Switch off dialog (BAPIs always run without)
   CALL FUNCTION 'DIALOG_SET_NO_DIALOG'.
   CALL FUNCTION 'BAPI_SALESORDER_CREATEFROMDAT2'
     EXPORTING
*     SALESDOCUMENTIN               =
     order_header_in               = orderheaderin
*     ORDER_HEADER_INX              =
*     SENDER                        =
*     BINARY_RELATIONSHIPTYPE       =
*     INT_NUMBER_ASSIGNMENT         =
*     BEHAVE_WHEN_ERROR             =
*     LOGIC_SWITCH                  =
*     TESTRUN                       =
*     CONVERT                       = ' '
*   IMPORTING
*     SALESDOCUMENT                 =
   TABLES
     return                        = return
     order_items_in                = orderitemsin
     order_items_inx               = orderitemsinx
     order_partners                = orderpartners
     order_schedules_in            = orderschedulesin
     order_schedules_inx           = orderschedulesinx
     order_conditions_in           = orderconditionsin
     order_conditions_inx          = orderconditionsinx
*     ORDER_CFGS_REF                =
*     ORDER_CFGS_INST               =
*     ORDER_CFGS_PART_OF            =
*     ORDER_CFGS_VALUE              =
*     ORDER_CFGS_BLOB               =
*     ORDER_CFGS_VK                 =
*     ORDER_CFGS_REFINST            =
*     ORDER_CCARD                   =
*     ORDER_TEXT                    =
*     ORDER_KEYS                    =
*     EXTENSIONIN                   =
*     PARTNERADDRESSES              =
*    commit work.
   CALL FUNCTION 'BAPI_TRANSACTION_COMMIT'
*     EXPORTING
*       WAIT          =
*     IMPORTING
*       RETURN        =
   LOOP AT return INTO wa_return.
     WRITE:/ wa_return-message.
   ENDLOOP.
ENDFUNCTION.
*& Include ZSD_SO_CHANGES2_TOP                               Module Pool      ZSD_SO_CHANGES2
PROGRAM ZSD_SO_CHANGES2.
***&SPWIZARD: DATA DECLARATION FOR TABLECONTROL 'ITEM_DATA'
*&SPWIZARD: DEFINITION OF DDIC-TABLE
TABLES:   VBAP,kna1.
*&SPWIZARD: TYPE FOR THE DATA OF TABLECONTROL 'ITEM_DATA'
TYPES: BEGIN OF T_ITEM_DATA,
          POSNR LIKE VBAP-POSNR,
          MATNR LIKE VBAP-MATNR,
          KWMENG LIKE VBAP-KWMENG,
          VRKME LIKE VBAP-VRKME,
        END OF T_ITEM_DATA.
*&SPWIZARD: INTERNAL TABLE FOR TABLECONTROL 'ITEM_DATA'
DATA:     G_ITEM_DATA_ITAB   TYPE T_ITEM_DATA OCCURS 0,
           G_ITEM_DATA_WA     TYPE T_ITEM_DATA. "work area
DATA:     G_ITEM_DATA_COPIED.           "copy flag
*&SPWIZARD: DECLARATION OF TABLECONTROL 'ITEM_DATA' ITSELF
CONTROLS: ITEM_DATA TYPE TABLEVIEW USING SCREEN 4000.
DATA:GV_NUM TYPE I VALUE 1,
       GV_NUM2 TYPE I.
DATA:     G_T_YREC_TAB_LINES LIKE SY-LOOPC.***********top*************
*& Include ZSD_SO_CHANGES2_TOP                               Module Pool      ZSD_SO_CHANGES2
PROGRAM ZSD_SO_CHANGES2.
***&SPWIZARD: DATA DECLARATION FOR TABLECONTROL 'ITEM_DATA'
*&SPWIZARD: DEFINITION OF DDIC-TABLE
TABLES:   VBAP,kna1.
*&SPWIZARD: TYPE FOR THE DATA OF TABLECONTROL 'ITEM_DATA'
TYPES: BEGIN OF T_ITEM_DATA,
          POSNR LIKE VBAP-POSNR,
          MATNR LIKE VBAP-MATNR,
          KWMENG LIKE VBAP-KWMENG,
          VRKME LIKE VBAP-VRKME,
        END OF T_ITEM_DATA.
*&SPWIZARD: INTERNAL TABLE FOR TABLECONTROL 'ITEM_DATA'
DATA:     G_ITEM_DATA_ITAB   TYPE T_ITEM_DATA OCCURS 0,
           G_ITEM_DATA_WA     TYPE T_ITEM_DATA. "work area
DATA:     G_ITEM_DATA_COPIED.           "copy flag
*&SPWIZARD: DECLARATION OF TABLECONTROL 'ITEM_DATA' ITSELF
CONTROLS: ITEM_DATA TYPE TABLEVIEW USING SCREEN 4000.
DATA:GV_NUM TYPE I VALUE 1,
       GV_NUM2 TYPE I.
DATA:     G_T_YREC_TAB_LINES LIKE SY-LOOPC.
************************pbo*******************
*& Include           ZSD_SO_CHANGES2_PBO
*&SPWIZARD: OUTPUT MODULE FOR TC 'ITEM_DATA'. DO NOT CHANGE THIS LINE!
*&SPWIZARD: COPY DDIC-TABLE TO ITAB
MODULE ITEM_DATA_INIT OUTPUT.
   IF G_ITEM_DATA_COPIED IS INITIAL.
*&SPWIZARD: COPY DDIC-TABLE 'VBAP'
*&SPWIZARD: INTO INTERNAL TABLE 'g_ITEM_DATA_itab'
*    SELECT * FROM VBAP
*       INTO CORRESPONDING FIELDS
*       OF TABLE G_ITEM_DATA_ITAB.
*    G_ITEM_DATA_COPIED = 'X'.
     REFRESH CONTROL 'ITEM_DATA' FROM SCREEN '4000'.
   ENDIF.
   ITEM_DATA-LINES = G_T_YREC_TAB_LINES + 15.
ENDMODULE.
*&SPWIZARD: OUTPUT MODULE FOR TC 'ITEM_DATA'. DO NOT CHANGE THIS LINE!
*&SPWIZARD: MOVE ITAB TO DYNPRO
MODULE ITEM_DATA_MOVE OUTPUT.
   MOVE-CORRESPONDING G_ITEM_DATA_WA TO VBAP.
ENDMODULE.
*&      Module STATUS_4000 OUTPUT
*       text
MODULE STATUS_4000 OUTPUT.
   SET PF-STATUS 'APAR'.
* REFRESH G_ITEM_DATA_ITAB.
    GV_NUM = 1.
* SET TITLEBAR 'xxx'.
ENDMODULE.                 " STATUS_4000 OUTPUT

Imp: Module pool Or Dialog programming

Hi ,
I have got a requirement to work on module pool programming.....Please help me with some documents which explains me about it from scratch clearly .
Awaiting for ur reply...........

basics of module pool
OVERVIEW
There are programs in every domain that require certain amount of user interaction .Such requirements in ABAP are fulfilled with the help of a user dialog and dialog programming which encapsulates the entire logic pertaining to the required user dialog.
One needs to take care that user interactions with the system are comfortable and user friendly along with being logically coherent.
What is a user dialog?
Any kind of user interaction with the system can be called as a user dialog:
1) Entering data on the screen.
2) Clicking a button.
3) Navigation between screens.
Need of dialog programming
In a typical dialog, the system displays a screen on which the user can enter or request information. As a reaction on the user input or request, the program executes the appropriate actions: it branches to the next screen, displays an output, or changes the database.
Example
A travel agent wants to book a flight. The agent enters the corresponding data on the screen. The system either confirms the desired request, that is, the agent can book the flight and the customer travels on the desired day on the reserved seat to the chosen destination, or the system displays the information that the flight is already booked up.
To fulfill such requirements, a dialog program must offer:
A user-friendly user interface
Format and consistency checks for the data entered by the user
Easy correction of input errors
Access to data by storing it in the database.
ABAP/4 offers a variety of tools and language elements to meet the requirements stated above in the dialog programs.

Why dialog programming is also known as module pool?
Dialog Programming consists of screens and corresponding ABAP program. Screens call dialog modules in the associated ABAP program from their flow logic. Type M programs serve principally as containers for these dialog modules, and hence dialog programming is also known as module pools. A module pool program is a program type which is not executable directly. You can not just run by hitting F8 like a report program. You must tie a transaction code to a screen in order to start the program.
VARIOUS COMPONENTS OF A DIALOG PROGRAM
Unlike report, interface or any conversion development which generally entails the creation of one autonomous program which can be executed independently of other objects, dialog program development entails development of multiple objects none of which can be executed on its own. Instead all objects are linked hierarchically to the main program and are executed in a sequence dictated by the Dialog Main Program.

Components of a dialog program
1) Transaction
2) Screen
3) GUI status
4) ABAP program
All these components are explained in detail below.
1) TRANSACTION :
The transaction starts a screen sequence. You create transaction codes in the Repository Browser in the ABAP Workbench or using Transaction SE93. A transaction code is linked to an ABAP program and an initial screen. As well as using a transaction code, you can start a screen sequence from any ABAP program using the CALL SCREEN statement.
2) SCREEN
As a user of an R/3 system, one is always confronted with screens. From the moment one logs on, one can see a screen and one must perform actions on this screen. All those screens are components of ABAP programs. Generally, we define the screens of an ABAP program with the Screen Painter tool of the ABAP.
In the R/3 system, screens are program objects that consist of two parts. First, they have a layout that defines the front end appearance of the window that is presented to the user. Second, they have a flow logic that is executed on the backend by the application server. The screen flow logic is a program layer between the front end and the actual ABAP application program at the backend. The language used to program screen flow logic has a similar syntax to ABAP, but is not part of ABAP itself. Unlike ABAP programs, the screen flow logic contains no explicit data declarations. You define the screen fields by placing elements on the screen mask instead. When you define screen fields by referring to data types in the ABAP Dictionary, the runtime environment automatically creates dialogs for field help, input help, and error handling that depends on the semantics of the data type in the dictionary.
The screen flow logic is similar to an ABAP program in that it contains processing blocks. These processing blocks are event blocks that are triggered by the ABAP runtime environment. The most important event blocks are:
PROCESS BEFORE OUTPUT
The respective event (PBO) is triggered after the PROCESS AFTER INPUT (PAI) processing of the previous screen and before the current screen is displayed.
PROCESS AFTER INPUT
The respective event (PAI) is triggered when the user chooses a function on the current screen.
PROCESS ON HELP REQUEST
This event is triggered when function key F1 is pressed.
PROCESS ON VALUE REQUEST
This event is triggered when function key F4 is pressed.
The main task of these processing blocks is to call ABAP dialog modules using the MODULE statement. During the PBO event, you can call any dialog module in the ABAP program that is marked with the addition OUTPUT. In the PAI event, you can call any dialog module program that is marked with the addition INPUT. The screens of an ABAP program can share the dialog modules of that program. You use the dialog modules called during PBO to prepare the screen and the dialog modules called during PAI to react to the user input.
Each screen of an ABAP program has a unique screen number. The screens of an ABAP program can be combined to form screen sequences. Screen sequences are either built statically by setting the following screen in the Screen Painter or dynamically by overriding the static setting in the ABAP program. The last screen of a screen sequence is always the one where the following screen is set to zero.
ATTRIBUTES OF SCREEN
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 by using SET CURSOR FIELD <f>
 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.
VARIOUS SCREEN ELEMENTS
A screen can contain a wide variety of elements, either for displaying field contents, or for allowing the user to interact with the program (for example, filling out input fields or choosing pushbutton functions). We use the Screen Painter to arrange elements on the screen.
We can use the following elements:
 Text fields
Display elements, which cannot be changed either by the user or by the ABAP program.
 Input/output fields and templates
Used to display data from the ABAP program or for entering data on the screen. Linked to screen fields.
 Dropdown list boxes
Special input/output fields that allow users to choose one entry from a fixed list of possible entries.
 Checkbox elements
Special input/output fields that the user can either select (value X) or deselect (value SPACE). Checkbox elements can be linked with function codes.
 Radio button elements
Special input/output fields that are combined into groups. Within a radio button group, only a single button can be selected at any one time. When the user selects one button, all of the others are automatically deselected. Radio button elements can be linked with function codes.
 Pushbuttons
Elements on the screen that trigger the PAI event of the screen flow logic when chosen by the user. There is a function code attached to each pushbutton, which is passed to the ABAP program when it is chosen.
 Frame
Pure display elements that group together elements on the screen, such as radio button groups.
 Subscreens
Area on the screen in which you can place another screen.
 Table controls
Tabular input/output fields.
 Tab strip controls
Areas on the screen in which you can switch between various pages.
 Custom Controls
Areas on the screen in which you can display controls. Controls are software components of the presentation server.
 Status icons
Display elements, indicating the status of the application program.
 OK field
Every screen has a twenty-character OK_CODE field (also known as the function code field) that is not displayed directly on the screen. User actions that trigger the PAI event also place the corresponding function code into this field, from where it is passed to the ABAP program. You can also use the command field in the standard toolbar to enter the OK field. To be able to use the OK field, you need to assign a name to it.
All screen elements have a set of attributes, some of which are set automatically, others of which have to be specified in the Screen Painter. They determine things such as the layout of the screen elements on the screen. You can set the attributes of screen elements in the Screen Painter - either for a single element, or using the element list, which lists all of the elements belonging to the current screen. Some of the attributes that you set statically in the Screen Painter can be overwritten dynamically in the ABAP program.
Regards
navjot
reward points if helpfull

How to delete the row in table control with respect to one field in module pool programming?

Hi,
Can I know the way to delete the row in table control with respect to one field in module pool programming
Regards
Darshan MS

HI,
I want to delete the row after the display of table control. I have created push button as delete row. If I click on this push button, the selected row should get deleted.
I have written this code,
module USER_COMMAND_9000 input.
DATA OK_CODE TYPE SY-UCOMM.
OK_CODE = SY-UCOMM.
CASE OK_CODE.
     WHEN 'DELETE'.
        LOOP AT lt_source INTO ls_source WHERE mark = 'X'.
            APPEND LS_SOURCE TO LT_RESTORE.
            DELETE TABLE LT_SOURCE FROM LS_SOURCE.
            SOURCE-LINES = SOURCE-LINES - 1.
        ENDLOOP.
But I'm unable to delete the selected rows, It is getting deleted the last rows eventhough I select the other row.
So I thought of doing with respect to the field.

How to use table maintenance view in module pool screen

hi ,
want to use table maintenance view in a module pool screen so that i can edit, insert, delete and update date in to the ztable.please help.

You can simply call it via SM30.   Or you can call the table maintence view from any program(report or module pool) using a function module.
call function 'VIEW_MAINTENANCE_CALL'
       exporting
            action                       = 'U'
            view_name                    = 'Z_Table_Name'
       exceptions
            client_reference             = 1
            foreign_lock                 = 2
            invalid_action               = 3
            no_clientindependent_auth    = 4
            no_database_function         = 5
            no_editor_function           = 6
            no_show_auth                 = 7
            no_tvdir_entry               = 8
            no_upd_auth                  = 9
            only_show_allowed            = 10
            system_failure               = 11
            unknown_field_in_dba_sellist = 12
            view_not_found               = 13
            others                       = 14.
Regards,
RIch Heilman

Error while transporting modification in module pool of a specific infotype

HI experts,
While transporting some modifications that have be done on the PAI of a module pool of a specific infotype, we have an error with code return = 8, the error is --> Original object R3TRPROGMP900730 must not be changed!!!
Any suggestion .
Tanhks a lot .

Hi ,
Nice to know that your problem is solved. If any of the replies were usefull please acknowledge their work.
And it would be great if you can just put in your remarks about the best solution you had in solving that problem.
It might be useful to other users when they encoutner such problem.
BR,
Vijay.

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

RE:module pool module switch.

Similar Messages

Maybe you are looking for