Calling search helps dynamically in module pool program

Hi Experts,
I have created two search helps. I need to call these search helps in my module pool program dynamically for a single field (i.e ZMATNR).
you might be known... if it is a single search help, we can assign that in field attributes.
But here... I need to call different search helps for a single field based on the condition.
Pls help me.
Thanks
Raghu

Hi,
Use the below function module and pass the search help created in search help field according to the condition.
Process on Value-request.
if condition = A.
call function " F4IF_FIELD_VALUE_REQUEST"
TABNAME           =
FIELDNAME        =
SEARCHHELP     = "Mention search help created
Elseif Conditon =B.
call function " F4IF_FIELD_VALUE_REQUEST"
TABNAME           =
FIELDNAME        =
SEARCHHELP     = "Mention search help created
Endif.
Regards,
Prabhudas

Similar Messages

Call report selection screen in module pool program with tab strip control

Hi,
Could anyone explain in detail to call report selection screen in module pool program with tab strip control.
Thanks
Mano

Hi,
Refer std program:
demo_sel_screen_in_tabstrip.
demo_sel_screen_with_tabstrip.
Call your program with SUBMIT stmt form module program.
Reward points if this Helps.
Manish

Conditional call to a subscreen in module pool program.

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

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

Want to change the text of a coloumn dynamically in module pool program

Hi to all experts,
I need to change the text in a table control( of a column)of a module pool program dynamically ....depending on the company cod e.

Hi,
In program depends on the condition you can access the table_control-cols-name and modify it accordingly.
Eg:
CONTROLS TABLE_CONTROL TYPE TABLEVIEW USING SCREEN 100.
you can access the control like:
TABLE_CONTROL-COLS[1]-SCREEN-NAME
and modify the same dynamicaly
cheers
shibu

How to deactivate the screen fields dynamically in Module Pool Program?

Hi guys,
 How to activate & deactivate the screen fields of a module pool program
dynamically through program. Like Change mode and display mode in a single
screen.

Hi,
Make use of a Variable,say gv_flag, for both Activate and Deactivate functionalities. As many times you hit the same button, change this variable value. For example, let us say first time you hit this button, assign value 'X' to this variable. Second time you hit this button, assign value ' ' to this variable. In PBO based the variable value you have to Activate and Deactivate.
PBO.
if gv_flag = 'X'. " Activate
 loop at screen.
 if screen-fname = 'ITAB1-MATNR'.
 screen-input = '1'.
 modify screen.
 endif.
 endloop.
elseif gv_flag = ' '. " Deactivate
 if screen-fname = 'ITAB1-MATNR'.
 screen-input = '0'.
 modify screen.
 endif.
 endloop.
endif.
PAI.
case sy-ucomm.
 when 'ACDC'. " Activate/Deactivate
 if gv_flag = 'X'.
 gv_flag = ' '.
 else.
 gv_flag = 'X'.
 endif.
endcase.
thanks,
sksingh

Calling search helps dynamically

Hi all,
I have two search helps. I need to call these search helps in my Application dynamically for a single field (PARNR) based on PARVW.
If it is a single search help, we can assign that in field attributes.
But here... I need to call different search helps for a single field based on the condition.
Pls help me.
Thanks
Kiran

Hi Kiran,
I Think by using OVS help u can acieve this, using WDR_OVS as used component.
here examples... check
http://www.sdn.sap.com/irj/scn/index?rid=/library/uuid/70cee684-ccbb-2c10-3c94-91e806e5f7ac
/people/shruti.rathour/blog/2008/05/05/ovs-help-in-web-dynpro-abap
http://wiki.sdn.sap.com/wiki/display/WDABAP/InputhelpofObjectValueSelectioninWDABAP
Cheers,
Kris.
Edited by: kissnas on Mar 26, 2011 5:17 AM

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

Calling a report from module pool program

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

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

Plz provide tutorial to learn the Module pool programing?

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

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

How to conduct training for Module Pool Programming

Hi everybody
I am going to conduct 5 days training for module pool programming.
Can you please provide me some suggestion about how to start & what r the steps?
Please provide suggestion for following
1) From where should I start
2) What should be the first step & subsequent steps
3) how should I get documentation & sample programs
thanks

Hello,
You can start the training by first explaining what is Module Pool programming, and why is it needed, how is it different from other forms of programming , like reports(SE38).
Then go on to explain how to create a MPP , i.e this you can do by giving the demo online, like:-
Goto SE80
Create a new program, and so on.
Talk about the various elements of MPP, such as the scree(which is also known as Dynpro), text elements, pushbuttons, tabstrips, etc, and how to use them in the program.
For sample programs and documentation, you can refer to help.sap.com, and search the documnetation for Module Pool Programming.
Thanks and regards,
Prerna

Date search help in module pool programming in 4.6C version

Hi Experts,
How can i have input help in my module pool screen, I gave the searh help EXT_DATE in the search help parameter of that screen's field parameter.
But its not showing the input help.
I m facing this issue in 4.6C.
Please advise
Thanks
Yogesh Gupta

Hi,
Just to make sure that you are talking about F1 help and not F4 for input of date right?
For F1 help of screen field, please check program for tcode: F150 (Dunning Run), You will find FM: F150_FIELD_SELECTION_HELP used for one field on screen (112).
I guess this might help you.
thanks,
Ags.

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

How to Use F4 help in Module Pool Programming??????

Hi Friends,
This is Jagadeesh, I have an issue Module Pool Programming. Any of you can go through on this and can give an required answer.
Issue is as follows,
I have an Input/Output field for that i need to give f4 help, based on that field the related data should sit in to my table control. The thing is there is no relation between the input/output field and the table control fields.
Is this possible? If so how can i do this.

Hi Jagadeesh,
For F4 Values on Screen:
PROCESS ON VALUE_REQUEST
using module call starting with FIELD i.e FIELD field MODULE module
There are number of function modules that can be used for the purpose, but these
can fullfill the task easily or combination of them.
DYNP_VALUE_READ
F4IF_FIELD_VALUE_REQUEST
F4IF_INT_TABLE_VALUE_REQUEST
POPUP_WITH_TABLE_DISPLAY
DYNP_VALUE_READ
This function module is used to read values in the screen fields. Use of this
FM causes forced transfer of data from screen fields to ABAP fields.
There are 3 exporting parameters
DYNAME = program name = SY-CPROG
DYNUMB = Screen number = SY-DYNNR
TRANSLATE_TO_UPPER = 'X'
and one importing TABLE parameter
DYNPFIELDS = Table of TYPE DYNPREAD
The DYNPFIELDS parameter is used to pass internal table of type DYNPREAD
to this FM and the values read from the screen will be stored in this table.This
table consists of two fields:
FIELDNAME : Used to pass the name of screen field for which the value is to
be read.
FIELDVALUE : Used to read the value of the field in the screen.
e.g.
DATA: SCREEN_VALUES TYPE TABLE OF DYNPREAD ,
SCREEN_VALUE LIKE LINE OF SCREEN_VALUES.
SCREEN_VALUE-FIELDNAME = 'KUNNR' . * Field to be read
APPEND SCREEN_VALUE TO SCREEN_VALUES. * Fill the table
CALL FUNCTION 'DYNP_VALUES_READ'
EXPORTING
DYNAME = SY-CPROG
DYNUMB = SY-DYNNR
TRANSLATE_TO_UPPER = 'X'
TABLES
DYNPFIELDS = SCREEN_VALUES.
READ TABLE SCREEN_VALUES INDEX 1 INTO SCREEN_VALUE.Now the screen value for field KUNNR is in the SCREEN_VALUE-FIELDVALUE and can be used for further processing like using it to fill the internal table to be used as parameter in F4IF_INT_TABLE_VALUE_REQUEST ETC.
F4IF_FIELD_VALUE_REQUEST
This FM is used to display value help or input from ABAP dictionary.We have to pass the name of the structure or table(TABNAME) along with the field name(FIELDNAME) . The selection can be returned to the specified screen field if three
parameters DYNPNR,DYNPPROG,DYNPROFIELD are also specified or to a table if RETRN_TAB is specified.
CALL FUNCTION 'F4IF_FIELD_VALUE_REQUEST'
EXPORTING
TABNAME = table/structure
FIELDNAME = 'field name'
DYNPPROG = SY-CPROG
DYNPNR = SY-DYNR
DYNPROFIELD = 'screen field'
IMPORTING
RETURN_TAB = table of type DYNPREAD
F4IF_INT_TABLE_VALUE_REQUEST
This FM is used to dsiplay values stored in an internal table as input
help.This FM is used to program our own custom help if no such input help
exists in ABAP dictionary for a particular field. The parameter VALUE_TAB is used to pass the internal table containing input values.The parameter RETFIELD
is used to specify the internal table field whose value will be returned to the screen field or RETURN_TAB.
If DYNPNR,DYNPPROG and DYNPROFIELD are specified than the user selection is passed to the screen field specified in the DYNPROFIELD. If RETURN_TAB is specified the selectionis returned in a table.
CALL FUNCTION 'F4IF_INT_TABLE_VALUE_REQUEST'
EXPORTING
RETFIELD = field from int table whose value will be returned
DYNPPROG = SY-CPROG
DYNPNR = SY-DYNNR
DYNPROFIELD = 'screen field'
VALUE_ORG = 'S'
TABLES
VALUE_TAB = internal table whose values will be shown.
RETURN_TAB = internal table of type DDSHRETVAL
EXCEPTIONS
parameter_error = 1
no_values_found = 2
others = 3.
POPUP_WITH_TABLE_DISPLAY
This FM is used to display the contents of an internal table in a popup window.The user can select a row and the index of that is returned in the CHOISE
parameter.The VALUETAB is used to pass the internal table.
A suitable title can be set using TITLETEXT parameter. The starting and end position of the popup can be specified by the parameters STARTPOS_COL / ROW and ENDPOS_ROW / COL .
CALL FUNCTION 'POPUP_WITH_TABLE_DISPLAY'
EXPORTING
ENDPOS_COL =
ENDPOS_ROW =
STARTPOS_COL =
STARTPOS_ROW =
TITLETEXT = 'title text'
IMPORTING
CHOISE =
TABLES
VALUETAB =
EXCEPTIONS
BREAK_OFF = 1
OTHERS = 2.
e.g.
DATA: w_choice TYPE SY-TABIX.
DATA: BEGIN OF i_values OCCURS 0 WITH HEADER LINE,
values TYPE I,
END OF i_values.
PARAMETRS : id TYPE I.
AT SELECTION-SCREEN ON VALUE-REQUEST FOR id
i_values-values = '0001'.
APPEND i_values.
i_values-values = '0002'.
APPEND i_values.
i_values-values = '0003'.
APPEND i_values.
i_values-values = '0004'.
APPEND i_values.
CALL FUNCTION 'POPUP_WITH_TABLE_DISPLAY'
EXPORTING
ENDPOS_COL = 40
ENDPOS_ROW = 12
STARTPOS_COL = 20
STARTPOS_ROW = 5
TITLETEXT = 'Select an ID'
IMPORTING
CHOISE = w_choice
TABLES
VALUETAB = i_values
EXCEPTIONS
BREAK_OFF = 1
OTHERS = 2.
CHECK w_choice > 0.
READ TABLE i_values INDEX w_choice....now we can process the selection as it is contained
...in the structure i_values.
Other FM that may be used to provide input help is HELP_START .
regards,
Dj
reward for all useful answers.

'Save As Variant' for Module Pool Program - FM to be called?

I have a dialog program, i want to activate the 'Save As variant' when i click on save on the selection screen of the transaction i created for the dialog program. What funtionality should be called or written for the PF-STATUS to implement the functionality.

hi Dagny,
You can't have variants for module pool. It is possible only for selection screen.
You have following alternatives :-
1. Create a report with same selection screen as you have now in module pool.
And then make a call screen to your intial module pool.
In this way you can all the advantage of variants as well as module pool.
OR
2. Create a transaction variant using transaction SHDO.
Hope it is helpful.
and do search the form , it is already answered before.
regards
venkat

Module Pool Programming - Calling SAP Standard Text Screen

Hi Gurus
I am working on Module Pool Programming...In the one of the screen there is a column named "Description" where I need to keep a Button to call a SAP standard text editing screen and what ever information I enter in the field should be downloadable
is this option possible?If so...Plz send me the Sample code
Thanks
Ganesh

Hi Gani,
I can help you till getting the text editor in your module pool program.
TOP
PROGRAM ZREDDY_TEXT.
constants: line_length type i value 132.
   data:
reference to wrapper class of control
   g_editor type ref to cl_gui_textedit,
reference to custom container: necessary to bind TextEdit Control
   g_editor_container type ref to cl_gui_custom_container,
   g_repid like sy-repid,                        " getting program name
   g_ok_code like sy-ucomm,                " return code from screen
   g_mytable(132) type c occurs 0,        " getting the text of table
   g_mycontainer(30) type c,                " string for the containers
   v_result(256) type c,                        " getting the text of table control
   gw_thead like thead,                        " for header information
   it_line type table of tline with header line. " internal table of type tline
PBO
MODULE STATUS_0900 OUTPUT.
SET PF-STATUS 'ZTEXT'.
SET TITLEBAR 'xxx'.
if g_editor is initial.
create control container
   create object g_editor_container
   exporting
   container_name = 'CUSTOM_CONTROL' " Make sure when you create custom container in layout give name as Custom container
   exceptions
   cntl_error = 1
   cntl_system_error = 2
   create_error = 3
   lifetime_error = 4
   lifetime_dynpro_dynpro_link = 5.
   g_mycontainer = 'CUSTOM_CONTROL'.
create calls constructor, which initializes, creates and links
TextEdit Control
create object g_editor
   exporting
   parent = g_editor_container
   wordwrap_mode =
cl_gui_textedit=>wordwrap_off
   cl_gui_textedit=>wordwrap_at_fixed_position
cl_gui_textedit=>WORDWRAP_AT_WINDOWBORDER
   wordwrap_position                      = line_length
   wordwrap_to_linebreak_mode     = cl_gui_textedit=>true.
   refresh g_mytable. " to initialize table upon OK_CODE 'BACK' at PAI
   endif.
ENDMODULE.                 " STATUS_0900 OUTPUT
Cheers!!
Balu
Edited by: Balu CH on Oct 22, 2008 8:55 PM

Calling search helps dynamically in module pool program

Similar Messages

Maybe you are looking for