Module pool program input field

Hi friends,
I took a input field in the screen and named it as match, I need to pass the sum of the values capture in a variable v_total to that field. Can u tell me how to do this, coz I tried but unable to display the sum value on the screen.
Regards,
Line

hi line,
i guess the input field is on the second screen or ,you may want to show the
value on the input field after you do a commad. i suggest you use the memory id
when defineing the input field give a memory id to id . and in the program you export the value v_total to the same memory id .
if this not work well try to use FM DYNP_VALUES_READ
and DYNP_VALUES_UPDATE
regards.

Similar Messages

Module Pool Programming : Screen Fields.

Hello
i have 2 fields in a screen. Field1 and Field2
i enter the field1 and want to set the f4 help for second field field2 on the basis of the input in field1.
but when i enter field1 and press f4 help for field2, it doesnot work because the field1 values are not passed when i use process on value request for field2 .
please help .... what am i missing.
Thanks

Hi ,
you have to use "DYNP_VALUES_READ" function mdule to read the field1 value to process in "F4IF_INT_TABLE_VALUE_REQUEST" function module.
check the code below
declare one internal table like this.
data dynpro_values type table of dynpread.
add the fields which you want to read.
field_value-fieldname = Z_POLCY-BUKRS'.
append field_value to dynpro_values.
field_value-fieldname = 'Z_POLCY-WERKS'.
append field_value to dynpro_values.
call function 'DYNP_VALUES_READ'
 exporting
 dyname = progname
 dynumb = dynnum
 translate_to_upper = 'X'
 REQUEST = ' '
 PERFORM_CONVERSION_EXITS = ' '
 PERFORM_INPUT_CONVERSION = ' '
 DETERMINE_LOOP_INDEX = ' '
 tables
 dynpfields = dynpro_values
 exceptions
 invalid_abapworkarea = 1
 invalid_dynprofield = 2
 invalid_dynproname = 3
 invalid_dynpronummer = 4
 invalid_request = 5
 no_fielddescription = 6
 invalid_parameter = 7
 undefind_error = 8
 double_conversion = 9
 stepl_not_found = 10
 others = 11
if sy-subrc <> 0.
 message id sy-msgid type sy-msgty number sy-msgno
 with sy-msgv1 sy-msgv2 sy-msgv3 sy-msgv4.
else.
 call function 'F4IF_INT_TABLE_VALUE_REQUEST'
 exporting
 DDIC_STRUCTURE = ' '
 retfield = 'POLTYPE'
 PVALKEY = ' '
 dynpprog = progname
 dynpnr = dynnum
 dynprofield = 'z_POLCY-POLTYPE'
 STEPL = 0
 WINDOW_TITLE =
 VALUE = ' '
 value_org = 'S'
 MULTIPLE_CHOICE = ' '
 DISPLAY = ' '
 CALLBACK_PROGRAM = ' '
 CALLBACK_FORM = ' '
 tables
 value_tab = it_poltype
 FIELD_TAB =
 RETURN_TAB =
 DYNPFLD_MAPPING = it_ret
 exceptions
 parameter_error = 1
 no_values_found = 2
 others = 3
 if sy-subrc <> 0.
 message id sy-msgid type sy-msgty number sy-msgno
 with sy-msgv1 sy-msgv2 sy-msgv3 sy-msgv4.
 endif.
endif.
regards
shibu
*check the code for syntax i just given one prototype

F4 help for the screen fields in module pool program

Hi All,
I have a requirement that, i want to provide F4 help for the 2 fields in module pool program. the fields are document number and fiscal year from rbkp table.
i could provide search help for two fields.
but how to select matching fiscal year for that document number.
problem: i am getting fiscal year as first four digits of document number.
please help me to solve this problem.
Thanks & Regards,
Namratha.V

Hi,
If your requirement is after selecting the document no from f4 help then the corresponding year should be updated in the document year field then use FM --> DYNP_VALUES_UPDATE
In this function module pass the screen no program & field for which u want to update value

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 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 validate the field values in module pool program?

Hi Guys
 I am working with module pool programming.
 Here I want to validate the fields like below.
 with out filling all the fields if I click SAVE option it has to show a message that all fields has to be filled. This can be done by checking all the fields individually.
 I think it can be done through LOOP AT SCREEN ......ENDLOOP. sequence.
 If it is possible, can anyone help me?

You need to write the Module in between the CHAIN and ENDCHAIN statment in SE51
If you send a warning or error message from a module <mod> that you called using a FIELD statement as follows:
CHAIN.
FIELD: <f1>, <f 2>,...
MODULE <mod1>.
FIELD: <g1>, <g 2>,...
MODULE <mod2>.
ENDCHAIN.
all of the fields on the screen that belong to the processing chain (all of the fields listed in the field statements) are made ready for input again. Other fields are not ready for input. Whenever the MODULE statement appears within a processing chain, even if there is only one FIELD attached to it, all of the fields in the chain (not only the affected field) are made ready for input again, allowing the user to enter new values. If the fields in the processing chain are only checked once, the PAI processing continues directly after the FIELD statement, and the preceding modules are not called again.
Look at the DEMO program DEMO_DYNPRO_FIELD_CHAIN.
ashish

How to make the field as mandatory in module pool program.

Hi Experts,
Could you please advice me in making a screen field as mandatory input field in module pool programming.
Thanks in advance.

Or you could add a check in a PAI module to check if there is some value, if not give error message.
module check_value.
if lv_value is initial.
message e001(00) with 'Enter a value'.
endif.
endmodule
In the PAI screen flow logic...
Process after input.
field lv_value module check_value.
Regards,
Rich Heilman

F1 help on a field in module pool programming

I want to create f1 help on a field in module pool programming. How to use POH event. where should i write the help documentation. Before using this f1 help on a field i have to set some properties on GUI interface Editor. Please clearly mention the steps i have to follow.

PROCESS ON HELP-REQUEST.
FIELD P_LFA1 MODULE HELP_F1_LIFNR.
MODULE HELP_F1_LIFNR INPUT.
PERFORM SHOW_HELP_F1 USING 'ZFAG_DOC1'.
ENDMODULE. " help_f1_lifnr INPUT
FORM SHOW_HELP_F1 USING P_OBJECT.
Dati testo help
DATA: T_LINE LIKE TLINE OCCURS 0,
XHEAD LIKE THEAD,
HELP_INFO LIKE HELP_INFO,
TEXC LIKE SY-UCOMM OCCURS 0,
V_OBJECT LIKE DOKHL-OBJECT.
Costante
DATA: PREF_SIMG(4) VALUE 'SIMG',
DOCID_HY LIKE DOKHL-ID VALUE 'HY'.
Testo
CONCATENATE PREF_SIMG P_OBJECT INTO V_OBJECT.
Estrazione testo
CALL FUNCTION 'DOCU_GET_FOR_F1HELP'
EXPORTING
ID = DOCID_HY
LANGU = SY-LANGU
OBJECT = V_OBJECT
IMPORTING
HEAD = XHEAD
TABLES
LINE = T_LINE
EXCEPTIONS
RET_CODE = 1
OTHERS = 2.
CASE SY-SUBRC .
WHEN 0.
Visualizzazione testo
GET CURSOR FIELD HELP_INFO-DYNPROFLD.
HELP_INFO-DOCUID = DOCID_HY.
HELP_INFO-DOCUOBJECT = V_OBJECT.
HELP_INFO-SPRAS = SY-LANGU.
HELP_INFO-PROGRAM = SY-REPID.
HELP_INFO-DYNPRO = SY-DYNNR.
HELP_INFO-DYNPPROG = SY-REPID.
HELP_INFO-PFKEY = SY-PFKEY.
HELP_INFO-FIELDNAME = HELP_INFO-DYNPROFLD.
CALL FUNCTION 'HELP_DOCULINES_SHOW'
EXPORTING
HELP_INFOS = HELP_INFO
OVERLAY_HEADER = XHEAD
TABLES
EXCLUDEFUN = TEXC
HELPLINES = T_LINE.
WHEN OTHERS. MESSAGE S720(SH).
ENDCASE.
ENDFORM. " SHOW_HELP_F1

Current time in module pool programming in text field

Hello Friends,
In module pool programming ther is a input output field for time i want the current system time should be displayed in that field and when user press saves tht time should get saved in the database tables.
regards,
Sunny

Hi, sunny,
If I understand your question correctly than I think that the following code will help you, you will have to write this code in the called program means where you are calling your screens.
data: tf_rec_no(10). u201Ctf_rec_nou201D is the field name on your screen
initialization.
write: sy-uzeit to tf_rec_no.
after this you can update db using this field.
Replay if any problem or you have some different query.
Kind Regards,
Faisal.

I want to go back from mandatory field in module pool program

Hi
i am doing tab strip control in module pool program.i want to go back from the selection field, which is a mandatory, to the main program by pressing f3.but i am nt able to get the output.can anybody pls help me.
Amayika

Hi
1. For your BACK or CANCEL button on menu bar, give Button
Ftype "E".
2. In PAI : Write below Modules.
PROCESS AFTER INPUT.
MODULE CANCEL AT EXIT-COMMAND.
MODULE BACK AT EXIT-COMMAND.
double click on it.Inside of modules write below code.
MODULE CANCEL INPUT.
IF OK_CODE = 'CANCEL'.
CLEAR OK_CODE.
LEAVE PROGRAM.
ENDIF.
ENDMODULE.
MODULE BACK INPUT.
IF OK_CODE = 'BACK'.
CLEAR: OK_CODE, INPUT1, INPUT2.
LEAVE TO SCREEN 100.
ENDIF.
ENDMODULE.

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

Module pool programming - supressing display of some fields

Moderator message: better to start a new thread.
Hi i have similar requirement to this. module pool programming - supressing display of some fields
suppose i am displying
BUKRS    0001
Sales org 0001
KUNNR    1000
i dont want todisplay if the field is blank.
suppose if sales org is blank
expected result is liek this
BUKRS    0001
KUNNR    1000
i tried through loop at screen by uisng that
i am getting output like below.
BUKRS    0001
KUNNR    1000
hello subbarao, could you tell if your problem solved.

Hi Naidu,
In PBO put
DATA: FLAG TYPE I VALUE 0.
IF SALESORG = SPACE.
FLAG = 1.
ENDIF.
LOOP AT SCREEN.
IF FLAG = 1.
    IF SCREEN-NAME = 'SALESORG'.
       SCREEN-INVISIBLE = 'X'.
       MODIFY SCREEN.
    ENDIF.
ENDIF.
ENDLOOP.
Thanks,
Chidanand

No Interval effect in Module Pool Program field

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

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

How to access screen field value in a module pool programming?

Hi Experts,
   I have create a module pool program SAPMYDLG. It contains two screens 100 and 200.
   The first screen contains Employee_ID field. This field is not a dictionary field.
   In the second screen 200, I want to access the value of Employee_ID field from first screen.
   For this I created a global variable v_empid in TOP include.
   Then in the PAI of the screen 100 I have assigned the screen field value to global variable.
   v_empid = Employee_ID.
   But this gives an error saying " Field Employee_ID not defined".
   What am I doing wrong? How can I access the screen field value?
Thanks
Gopal

Hi,
Employee_ID field also must u define in the top include when u define that 100 screen and 200 screen will access.
regards,
muralii

How to Add F4 Help To a Screen Field In a Module Pool Program

Hi Friends,
1. How to Add F4 Help To a Screen Field In a Module Pool Program?
2. How to select a single cell in ALV report output for interactive reporting ?
Kindly give code example.
regards,
Pradeep

Hi,
Try using the fm 'F4IF_INT_TABLE_VALUE_REQUEST'.
Refer the link below for selecting single cell.
alv
Reward points if useful.
Regards
Rose

Module pool program input field

Similar Messages

Maybe you are looking for