POH in module pool.....have ur points..

Hi ALL,
-I took a text box with name 'AGE' in layout of the screen.
-Now i want to give F1 help to this filed.
-I used PROCESS ON HELP-REQUEST. field AGE with 'for user age'.
now i m executing the transaction & pressing F! help there...but no help
ples help me...
have ur points..
Regards,
pradeep phogat

Hi,
Calling Help Texts from Dialog Modules
If data element supplement documentation is insufficient for your requirements, or you want to display help for program fields that you have not copied from the ABAP Dictionary, you can call dialog modules in the POH event:
PROCESS ON HELP-REQUEST.
FIELD <f> MODULE <mod>.
After the PROCESS ON HELP-REQUEST statement, you can only use the MODULE statement together with the FIELD statement. When the user chooses F1 for a field <f>, the system calls the module <mod> belonging to the FIELD <f> statement. If there is more than one FIELD statement for the same field <f>, only the first is executed. However, the contents of the screen field <f> are not available in the module <mod>, since it is not transported by the FIELD statement during the PROCESS ON HELP-REQUEST event. The field help should not be
dependent on the user input.
The module <mod> is defined in the ABAP program like a normal PAI module. The processing logic of the module must ensure that adequate help is displayed for the field in question. Instead of calling an extra screen with text fields, you should use one of the following function modules to display a suitable SAPscript document:
HELP_OBJECT_SHOW_FOR_FIELD
This function module displays the data element documentation for components of any structure or database table from the ABAP Dictionary. You pass the name of the component and structure or table to the import parameters FIELD and TABLE.
HELP_OBJECT_SHOW
Use this function module to display any SAPscript document. You must pass the
document class (for example, TX for general texts, DE for data element documentation) and the name of the document to the import parameters DOKCLASS and DOKNAME. For technical reasons, you must also pass an empty internal table with the line type TLINE to the tables parameter of the function module.
Ex.
Field help on screens.
REPORT DEMO_DYNPRO_F1_HELP.
DATA: TEXT(30),
VAR(4),
INT TYPE I,
LINKS TYPE TABLE OF TLINE,
FIELD3, FIELD4.
TABLES DEMOF1HELP.
TEXT = TEXT-001.
CALL SCREEN 100.
MODULE CANCEL INPUT.
LEAVE PROGRAM.
ENDMODULE.
MODULE F1_HELP_FIELD2 INPUT.
INT = INT + 1.
CASE INT.
WHEN 1.
VAR = '0100'.
WHEN 2.
VAR = '0200'.
INT = 0.
ENDCASE.
ENDMODULE.
MODULE F1_HELP_FIELD3 INPUT.
CALL FUNCTION 'HELP_OBJECT_SHOW_FOR_FIELD'
EXPORTING
DOKLANGU = SY-LANGU
DOKTITLE = TEXT-002
CALLED_FOR_TAB = 'DEMOF1HELP'
CALLED_FOR_FIELD = 'FIELD1'.
ENDMODULE.
MODULE F1_HELP_FIELD4 INPUT.
CALL FUNCTION 'HELP_OBJECT_SHOW'
EXPORTING
DOKCLASS = 'TX'
DOKLANGU = SY-LANGU
DOKNAME = 'DEMO_FOR_F1_HELP'
DOKTITLE = TEXT-003
TABLES
LINKS = LINKS.
ENDMODULE.
Regards,
Bhaskar

Similar Messages

Reg. POV in module pool---have ur points...

Hi all,
I m trying to use POV event in module pool, I wrote
PROCESS ON VALUE-REQUEST.
FIELD ZPHOGAT-ROLLNO MODULE ABC.
Here in module ABC is wrote 'break-point'. when i click on F4 help of that field i my break-point is not getting executed.
Pleas help me out...
Have ur point.s
regards,

First make sure everything is compiled, then try an extended check on the main program to make sure you have your variable names, module pool name etc etc synchonised (in case you have a typo in the module or variable name)... then try changing your break-point for "message s398(00) with 'This is my POV' space space space." or something similar.

Want help in creating pov and poh in module pool

i want to create process on help and process on value request.
which function modules to use and how use them
then i want put icon symbols over push buttons.
can u please send me this information also.
i am new to screen programming .

krishna,
For POV
Input Help in Dialog Modules
You can call dialog modules in the POV event using the event keyword PROCESS ON VALUE-REQUEST.
PROCESS ON VALUE-REQUEST.
FIELD are not available, since it is not transported by the FIELD statement during the PROCESS ON HELP-REQUEST event. You can now program your own value lists in the module. However, this procedure is only recommended if it really is not possible to use a search help. Defining search helps is much easier than PROCESS ON VALUE-REQUEST, since the system takes over some of the standard operations, such as getting field contents from the screen. It also ensures that the F4 help has a uniform look and feel throughout the system. Furthermore, it means that you do not have to reassign input help to fields on each screen.
Despite the introduction of search helps (and search help exits), there are still cases in which you need to use parts of the standard F4 functions directly. In this case, there are some standard function modules that you can use in the POV event. They support search helps, as well as all other kinds of input help, and are responsible for data transport between the screen and the input help. These all have the prefix F4IF_. The most important are:
F4IF_FIELD_VALUE_REQUEST
Calls the input help of the ABAP Dictionary dynamically. You can pass the component names of a structure or database table of the ABAP Dictionary to the function module in the import parameters TABNAME and FIELDNAME. The function module starts the ABAP Dictionary input help for this component. All of the relevant screen fields are read. If you specify the import parameters DYNPPROG, DYNPNR, and DYNPROFIELD, the users selection is returned to the corresponding field on the screen. If you specify the table parameter RETURN_TAB, the selection is returned into the table instead.
F4IF_INT_TABLE_VALUE_REQUEST
This function module displays a value list that you created in an ABAP program. The value list is passed to the function module as the table parameter VALUE_TAB. If you specify the import parameters DYNPPROG, DYNPNR, and DYNPROFIELD, the users selection is returned to the corresponding field on the screen. If you specify the table parameter RETURN_TAB, the selection is returned into the table instead.
There are also two function modules - DYNP_VALUES_READ and DYNP_VALUES_UPDATE - that can read the values of screen fields and return values to them during the POV event. For further information, refer to the relevant function module documentation.
Input help in dialog modules
REPORT DEMO_DYNPRO_F4_HELP_MODULE.
TYPES: BEGIN OF VALUES,
         CARRID TYPE SPFLI-CARRID,
         CONNID TYPE SPFLI-CONNID,
       END OF VALUES.
DATA: CARRIER(3) TYPE C,
      CONNECTION(4) TYPE C.
DATA: PROGNAME LIKE SY-REPID,
      DYNNUM   LIKE SY-DYNNR,
      DYNPRO_VALUES TYPE TABLE OF DYNPREAD,
      FIELD_VALUE LIKE LINE OF DYNPRO_VALUES,
      VALUES_TAB TYPE TABLE OF VALUES.
CALL SCREEN 100.
MODULE INIT OUTPUT.
PROGNAME = SY-REPID.
DYNNUM   = SY-DYNNR.
CLEAR: FIELD_VALUE, DYNPRO_VALUES.
FIELD_VALUE-FIELDNAME = 'CARRIER'.
APPEND FIELD_VALUE TO DYNPRO_VALUES.
ENDMODULE.
MODULE CANCEL INPUT.
LEAVE PROGRAM.
ENDMODULE.
MODULE VALUE_CARRIER INPUT.
CALL FUNCTION 'F4IF_FIELD_VALUE_REQUEST'
       EXPORTING
            TABNAME           = 'DEMOF4HELP'
            FIELDNAME         = 'CARRIER1'
            DYNPPROG          = PROGNAME
            DYNPNR            = DYNNUM
            DYNPROFIELD       = 'CARRIER'.
ENDMODULE.
MODULE VALUE_CONNECTION INPUT.
CALL FUNCTION 'DYNP_VALUES_READ'
       EXPORTING
            DYNAME                   = PROGNAME
            DYNUMB                   = DYNNUM
            TRANSLATE_TO_UPPER       = 'X'
       TABLES
            DYNPFIELDS               = DYNPRO_VALUES.
READ TABLE DYNPRO_VALUES INDEX 1 INTO FIELD_VALUE.
SELECT CARRID CONNID
    FROM SPFLI
    INTO CORRESPONDING FIELDS OF TABLE VALUES_TAB
    WHERE CARRID = FIELD_VALUE-FIELDVALUE.
CALL FUNCTION 'F4IF_INT_TABLE_VALUE_REQUEST'
       EXPORTING
            RETFIELD         = 'CONNID'
            DYNPPROG         = PROGNAME
            DYNPNR           = DYNNUM
            DYNPROFIELD      = 'CONNECTION'
            VALUE_ORG        = 'S'
       TABLES
            VALUE_TAB        = VALUES_TAB.
ENDMODULE.
The next screen (statically defined) for screen 100 is itself. It has the following layout:
The input fields have been adopted from the program fields CARRIER and CONNECTION. The pushbutton has the function code CANCEL with function type E.
The screen flow logic is as follows:
PROCESS BEFORE OUTPUT.
MODULE INIT.
PROCESS AFTER INPUT.
MODULE CANCEL AT EXIT-COMMAND.
PROCESS ON VALUE-REQUEST.
FIELD CARRIER MODULE VALUE_CARRIER.
FIELD CONNECTION MODULE VALUE_CONNECTION.
When the user chooses input help for the individual fields, the following is displayed:
For the Airline field, the POV module VALUE_CARRIER is called. The function module F4IF_FIELD_VALUE_REQUEST displays the input help for the component CARRIER1 of the structure DEMOF4HELP from the ABAP Dictionary, namely the search help DEMOF4DE. The users selection is returned to the screen field CARRIER.
For the Flight number field, the POV module VALUE_CONNECTION is called. The function module DYNP_VALUE_READ transports the value of the screen field CARRIER into the program. The program then reads the corresponding values from the database table SPFLI into the internal table VALUES_TAB using a SELECT statement, and passes the internal table to F4IF_INT_TABLE_VALUE_REQUEST. This displays the internal table as input help, and places the users selection into the screen field CONNECTION.
For POH
Field Help
There are three ways of displaying field help for screen elements:
Data Element Documentation
If you place a field on the screen in the Screen Painter by copying a ABAP Dictionary field, the corresponding data element documentation from the ABAP Dictionary is automatically displayed when the user chooses field help (as long as the help has not been overridden in the screen flow logic).
For further information about creating data element documentation, refer to data elements.
Data Element Supplement Documentation
If the data element documentation is insufficient, you can expand it by writing a data element supplement
Data element supplement documentation contains the heading Definition, as well as the following others:
Use
Procedure
Examples
Dependencies
To create data element supplement documentation for a screen, choose Goto ® Documentation ® DE supplement doc. from the element list of the screen. A dialog box appears in which the system proposes a number as the identified for the data element supplement. You can then enter help texts for the above headings using the SAPscript editor.
Data element supplement documentation created in this way is program- and screen-specific. Any data element supplement documentation created in the ABAP Dictionary with the same number is overridden by the screen-specific documentation. You can link existing data element supplement documentation created in the ABAP Dictionary with a screen field by using the table THLPF. To do this, crate a new row in THLPF containing the following data: Program name, screen name, field name, and number of the data element supplement documentation.
To display data element supplement documentation, you must code the following screen flow logic in the POH event:
PROCESS ON HELP-REQUEST.
FIELD is defined in the ABAP program like a normal PAI module. The processing logic of the module must ensure that adequate help is displayed for the field in question. Instead of calling an extra screen with text fields, you should use one of the following function modules to display a suitable SAPscript document:
HELP_OBJECT_SHOW_FOR_FIELD
This function module displays the data element documentation for components of any structure or database table from the ABAP Dictionary. You pass the name of the component and structure or table to the import parameters FIELD and TABLE.
HELP_OBJECT_SHOW
Use this function module to display any SAPscript document. You must pass the document class (for example, TX for general texts, DE for data element documentation) and the name of the document to the import parameters DOKCLASS and DOKNAME. For technical reasons, you must also pass an empty internal table with the line type TLINE to the tables parameter of the function module.
For further information about how to create SAPscript documents, refer to the Documentation of System Objects documentation.
Field help on screens.
REPORT DEMO_DYNPRO_F1_HELP.
DATA: TEXT(30),
       VAR(4),
       INT TYPE I,
       LINKS TYPE TABLE OF TLINE,
       FIELD3, FIELD4.
TABLES DEMOF1HELP.
TEXT = TEXT-001.
CALL SCREEN 100.
MODULE CANCEL INPUT.
LEAVE PROGRAM.
ENDMODULE.
MODULE F1_HELP_FIELD2 INPUT.
INT = INT + 1.
CASE INT.
    WHEN 1.
    VAR = '0100'.
    WHEN 2.
    VAR = '0200'.
    INT = 0.
ENDCASE.
ENDMODULE.
MODULE F1_HELP_FIELD3 INPUT.
CALL FUNCTION 'HELP_OBJECT_SHOW_FOR_FIELD'
       EXPORTING
            DOKLANGU                      = SY-LANGU
            DOKTITLE                      = TEXT-002
            CALLED_FOR_TAB                = 'DEMOF1HELP'
            CALLED_FOR_FIELD              = 'FIELD1'.
ENDMODULE.
MODULE F1_HELP_FIELD4 INPUT.
CALL FUNCTION 'HELP_OBJECT_SHOW'
       EXPORTING
            DOKCLASS                      = 'TX'
            DOKLANGU                      = SY-LANGU
            DOKNAME                       = 'DEMO_FOR_F1_HELP'
            DOKTITLE                      = TEXT-003
       TABLES
            LINKS                         = LINKS.
ENDMODULE.
The next screen (statically defined) for screen 100 is 100. It has the following layout:
The screen fields DEMOf1HELP-FIELD1 and DEMOF1HELP-FIELD2 from the ABAP Dictionary and the program fields FIELD3 and FIELD4 are assigned to the input fields. The pushbutton has the function code CANCEL with function type E.
The screen flow logic is as follows:
PROCESS BEFORE OUTPUT.
PROCESS AFTER INPUT.
MODULE CANCEL AT EXIT-COMMAND.
PROCESS ON HELP-REQUEST.
FIELD DEMOF1HELP-FIELD2 MODULE F1_HELP_FIELD2 WITH VAR.
FIELD FIELD3 MODULE F1_HELP_FIELD3.
FIELD FIELD4 MODULE F1_HELP_FIELD4.
The components FIELD1 and FIELD2 of structure DEMOF1HELP both refer to the data element DEMOF1TYPE. This data element is documented, and also has two supplements with numbers 0100 and 0200.
The following field help is displayed:
When the user chooses F1 on the input field for DEMOF1HELP-FIELD1, the data element documentation for DEMOF1TYPE is displayed, since the field does not occur in the PROCESS ON HELP-REQUEST event.
If the user chooses F1 repeatedly for the input field DEMOF1HELP-FIELD2, the data element documentation is displayed, along with the supplement documentation for either 0100 or 0200 alternately. The variable VAR is filled in the dialog module F1_HELP_FIELD2.
When the user chooses F1 on the input field for FIELD3, the data element documentation for DEMOF1TYPE is displayed, since this is called in the dialog module F1_HELP_FIELD3 by the function module HELP_OBJECT_SHOW_FOR_FIELD.
When the user chooses F1 on the input field for FIELD4, the SAPscript documentation DEMO_FOR_F1_HELP is displayed, since this is called in the dialog module F1_HELP_FIELD4 by the function module HELP_OBJECT.
Don't forget to reward if useful...

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.

Regarding standard menu in module pool... have ur point.s

Hi all,
I wanna copy stanadard status to my module pool program. Could u pleas help me for that...
have ur points..
Regards,
[email protected]

Hi Pradeep,
Goto SE41--> give the prog name SAPLKKBL and select the Status Radio button and give STANDARD
now press Ctrl+F6 which prompts you a new dialog to enter your desired prog name and status name. give in teh program name and enter a status name, which copies the standarad status to your program.
now in your program set the status using the statement
set pf-status 'NEW_STANDARD'.
Regards
Gopi

Reg. module pool....have ur points..

Hi all,
In module pool programming, we see "MODULE CANCEL AT EXIT-COMMAND" in PAI. Pleas let me know the meaning of this in simple language.....
n Have ur points.

Hi,
AT EXIT-COMMAND, only checks for the function code which is marked as 'E' in PF-STATUS, and the module below that is executed whenever you press that key associated with the function code.
AT USER-COMMAND, works for all keys with function-code.
So if you press F3, which is BACK and is usually associated with 'E' , and if you have both AT EXIT-COMMAND and AT USER-COMMAND, module below AT EXIT-COMMAND will be executed.
MODULE
Syntax
MODULE mod [ AT {EXIT-COMMAND|CURSOR-SELECTION} ]
[ ON {CHAIN-INPUT|CHAIN-REQUEST} ].
... AT EXIT-COMMAND
Effect
Addition AT EXIT-COMMAND at the event PAI causes module mod to be called exactly if:
The function used to trigger event PAI has function type "E"
Into the input field of the standard toolbar, the user entered a character string starting with "E" and confirmed it using ENTER.
The dialog module is called before the automatic input checks defined in the system or in the ABAP Dictionary and independent of its position in the event block. The only screen field transported to the ABAP program is the OK field. If the function that triggered the PAI event does not fulfill any of the above prerequisites, the MODULE statement is not executed.
If several MODULE statements have the AT EXIT COMMAND addition, only the first one is executed. If no MODULE statement has the addition AT EXIT COMMAND, a normal PAI processing is executed: The predefined input checks are executed and then the PAI event block is processed sequentially. Provided the screen processing is not terminated in the dialog module mod, after the return from the dialog module, the complete PAI processing is executed. You must not use the addition AT EXIT COMMAND in connection with the statement FIELD.
Note
The function type of a function is determined in the Screen Painter or Menu Painter. Usually those functions of the user interface are defined with function type "E" that are assigned to the icons Back, Exit and Cancel in the standard toolbar of the GUI status. Therefore, the called dialog module should terminate the screen processing and allow security checks, if required.
reward if it helps..
Regards,
Omkar.

Standard menu in module pool.....take ur points.

Hi all,
I want to use standard menu in my Module pool program. Pleas tell me the way for that?
I tried in SE41 by copying status from SAPLKKBL, menu is should but buttons are not working.
Pleas help me.
Have ur points.
Regards,

I assume u have copied the PF STATUS and used SET PF-STATUS in the PBO of the screen.
Now in the menu painter - u can view the Function Codes attached to each and every ICON/Button. In the PAI of the screen - u can handle the User commands.
data : fcode TYPE SY-UCOMM.
CASE FCODE.
WHEN 'BACK'.
WHEN 'CANC'.
ENDCASE.
In the Screen painter attach this variable FCODE to the OK code ( Go to Element list tab).
This will solve ur problem.

Want to have F4 help from an internal table in Module Pool.

Hi,
I have a input/output field in a Module pool program. I want to attach an F4 help on this from an internal table.
Please suggest me some techniques.
Thanks in advance..

Hi all,
This is the piece of code I have written...But I am getting the message "No Values Found"-
DECLARATION
TYPES:
     BEGIN OF ty_shipto,
     ship_to TYPE kunnr,
     END OF ty_shipto.
DATA:
        tb_shipto TYPE TABLE OF ty_shipto,
       wa_shipto TYPE ty_shipto.
REFRESH:
        tb_shipto.
CLEAR:
       wa_shipto.
TABLE TB_SHIPTO IS FILLED
SELECT spart
    FROM mara
    INTO CORRESPONDING FIELDS OF TABLE mara_it
    FOR ALL ENTRIES IN vlcvehicle_it
    WHERE matnr = vlcvehicle_it-matnr.
LOOP AT vlcvehicle_it INTO vlcvehicle_ls.
    MOVE-CORRESPONDING vlcvehicle_ls TO wa_vehinfo.
    APPEND wa_vehinfo TO tb_vehinfo.
ENDLOOP.
LOOP AT mara_it INTO mara_ls.
    MOVE-CORRESPONDING mara_ls TO wa_vehinfo.
    APPEND wa_vehinfo TO tb_vehinfo.
ENDLOOP.
LOOP AT vlcvehicle_it INTO vlcvehicle_ls.
    MOVE vlcvehicle_ls-vhcle TO va_vhcle.
    CALL FUNCTION 'ZCN_SD_GET_VLC_BRAND'
      EXPORTING
        in_vhcle          = va_vhcle
      IMPORTING
        out_distr_channel = va_vtweg.
    MOVE va_vtweg TO wa_vtweg.
    MOVE-CORRESPONDING wa_vtweg TO wa_vehinfo.
    APPEND wa_vehinfo TO tb_vehinfo.
ENDLOOP.
CLEAR:
       va_vtweg.
IF tb_vehinfo[] IS NOT INITIAL.
    LOOP AT tb_vehinfo INTO wa_vehinfo.
      MOVE wa_vehinfo-kunnr TO va_kunnr.
      IF va_kunnr IS NOT INITIAL.
        MOVE va_kunnr TO va_kunnr_final.
      ENDIF.
      MOVE wa_vehinfo-zvkorg TO va_vkorg.
      IF va_vkorg IS NOT INITIAL.
        MOVE va_vkorg TO va_vkorg_final.
      ENDIF.
      MOVE wa_vehinfo-spart TO va_spart.
      IF va_spart IS NOT INITIAL.
        MOVE va_spart TO va_spart_final.
      ENDIF.
      MOVE wa_vehinfo-vtweg TO va_vtweg.
      IF va_vtweg IS NOT INITIAL.
        MOVE va_vtweg TO va_vtweg_final.
      ENDIF.
    ENDLOOP.
ENDIF.
SELECT kunn2
    FROM knvp
    INTO TABLE tb_shipto
    WHERE kunnr = va_kunnr_final AND
          vkorg = va_vkorg_final AND
          spart = va_spart_final AND
          vtweg = va_vtweg_final AND
          parvw = 'WE'.
POV- TXT_SHIPTO_NVAL_NAR IS THE FIELD NAME IN DYNPRO
PROCESS ON VALUE-REQUEST.
FIELD:
       txt_shipto_nval_nar     MODULE f4_help_shipto_nar.
MODULE f4_help_shipto_nar INPUT.
CALL FUNCTION 'F4IF_INT_TABLE_VALUE_REQUEST'
    EXPORTING
      retfield         = 'SHIP_TO'
      dynpprog         = sy-repid
      callback_program = sy-repid
      dynpnr           = sy-dynnr
      dynprofield      = 'TXT_SHIPTO_NVAL_NAR'
    TABLES
      value_tab        = tb_shipto
      return_tab       = return_tab.
ENDMODULE.                 " M_F4_HELP_NVAL_SHIPTO INPUT
The code is runnig error free but I am unable to see any popup.
Message displayed: "No Values Found". But, I have checked in debugging that the table TB_SHIPTO contains some values when the FM is called.
Please point out the mistake.
Thanks in advance.

Very Important: Employee photo on module pool screen: Points assured

hi all
I have uploaded the employee photos using tcode OOAD.
Now in a module pool program, i need to show the emloyee's photo on the screen alongside the employee's other details..
Please let me know how to get the employee photo on screen.
thanks in advance
Points assured 

You can use the PICTURE CONTROL for this. Check the Link for further details
http://help.sap.com/printdocu/core/Print46c/en/data/pdf/BCCIIMAGE/BCCIIMAGE.pdf
http://help.sap.com/saphelp_erp2004/helpdata/en/9b/d080c09fc111d2bd68080009b4534c/frameset.htm
Also check the program RSDEMO_PICTURE_CONTROL
Message was edited by:
Abhishek Jolly

How to have a search help in module pool without using Process on value req

Can someone please tell me what r the ways if any to have F4 help in the module pool screen
with out using POV ?

Hi,
They are two ways to define search help for an object...
BY using POV
or
go to screen Layout and double click on the field you want F4 help and Pass the Search help math code for feild at the
place of Search_help field aand also you can add parameter-id at this place to provide search help.
go to screen Layout -->double click on the field you want F4 help
-->Pass the Search help math code for feild at the place of Search_help
save and activate..
reagrds,
Prabhudas

I have design one screen in Module pool

Hi,
I created one screen and i have taken 6 push buttons which is select all , Dselect all ,create new row,delete new row,Asending and Desendinf order How to write a code for these push buttons.
regards

Hi,
It is absolutely possible to perform a BDC operation in a module pool program irrespective any screen you are.
In the PAI, after capturing the appropriate ok_code (sy-ucomm), you branch to the SAVE option. There you call out a subrotuine. say PERFORM bdc_save_VF21.
Inside this subroutine write your logic. What happens is the transaction VF21 gets updated with your bdc code with the help of CALL TRANSACTION. Check out in debugging.
Also you can see by making the mode in call transaction to All screen mode 'A'.
Please let me know if you can succeed in this.
Award me if this is helpful to you!
If you require further help, please send me your mail id.. i'll send some code to you.
Regards,
Ananth
Edited by: Anantharamakrishnan Venkatesan on Jan 9, 2008 5:31 PM

Does anyone have any notes on how to create a module pool?

Hi,
I have created a new task type called "Notice Period Change Date" which I need to default in a task date of 5 years service (from their hiring date). Having read up on this I think I need to create a module pool and link via the dynamic action but I am a bit unsure on how to do this.
Any assistance would be greatly appreciated.
Thanks
Hannah

I think that you could use a dynamic action to create this new task date.
Create the dynamic action on the infotype 0000 when the action type (MASSN) = hiring,
Call infotype 0019 with the subtype = your new task type.
Then call a function (F) to add 5 years to the hire date (P0000-BEGDA) and put the result into the task date field P0019-TERMN
Take a look at the dynamic actions table T588Z - there are probably some examples already there.
Mark

Module Pool and Smart Form

Can anybody Provide me good step by step procedure for module pool and smart for programming with screenshot.
my email Id is [email protected]

Hi,
A module pool is a collection of screens, flow logic, menu bars and ABAP code that you use to build an application. Typically the transaction code that calls the application will refer to the module pool and the initial screen number.
-->What are the requirements a dialog program must fulfill ?
A dialog program must fulfill the following requirements
. 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.
What are the basic components of dialog program ?
Screens (Dynpros)
Each dialog in an SAP system is controlled by dynpros. A Dynpro consists of a screen and its flow logic and controls exactly one dialog step.
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.
What is a dynpro ? What are its components ?
A dynpro (DYnamic PROgram) consists of a screen and its flow logic and controls exactly
one dialog step.
- The different components of the dynpro are:
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
What is screen flow logic? What are the selections in it? Explain PAI and PBO?
Ans - Screen flow logic contains the procedural part of a screen. The screen flow logic is like an ABAP program in that it serves as a container for processing blocks. There are four event blocks, each of which is introduced with the screen keyword PROCESS:
PROCESS BEFORE OUTPUT.
PROCESS AFTER INPUT.
PROCESS ON HELP-REQUEST.
PROCESS ON VALUE-REQUEST.
Selections are performed in PAI.
PROCESS BEFORE OUTPUT (PBO) is automatically triggered after the PAI processing of the previous screen and before the current screen is displayed. You can program the PBO processing of the screen in this block. At the end of the PBO processing, the screen is displayed.
PROCESS AFTER INPUT (PAI) is triggered when the user chooses a function on the screen. You can program the PAI processing of the screen in this block. At the end of the PAI.
processing, the system either calls the next screen or carries on processing at the point from which the screen was called.
PROCESS ON HELP-REQUEST (POH) and PROCESS ON VALUE-REQUEST (POV) are triggered when the user requests field help (F1) or possible values help (F4) respectively. You can program the appropriate coding in the corresponding event blocks. At the end of processing, the system carries on processing the current screen.
step by step process of dialog programing:
Firstly, you can go to Tcode SE80 and here create a package.
On that package name right click and select program.
Then choose program type modulepool program.
Similarly, you can create screen and then select layout and drag and drop labels and pushbuttons as per your requirements.. Then double click on th push buttons.You will see property window and there we will find FCTCODE and there type the names e.g suppose you want to
display then typy on the fctcode Display or any name as you wish.
After that save and activate it. and then close the window.
And then go back to the intial screen .
And then click Flow logic button and then uncomment the statement
module status_1000 PBO block and then doible click on status_1000
save and activate and then go back and then PAI block uncomment the statement module status_1000 and the dobule click on status_1000.
step by step process of creating smartforms:
1.        What is Smartforms?
Smartforms is a tool to create and maintain forms for mass printing in SAP Systems. Just like sapscripts, for Smart
forms print program is used to create the output internal table which in turn is thrown to the smart form where the
field values are displayed. The output medium for Smartforms support printer, fax, e-mail, or the Internet.
Transaction Code: SMARTFORMS
To print a form the program for the data retrieval and a Smartform that contains the entire form logic is required. As
these two are separate one should adapt the Smartform if changes to the form logic are necessary. The application
program passes the data via a function module interface to the Smartform. When activating the Smartform the system
automatically generates the function module.
The architecture of the smart form is given below:
Creating Forms Using SAP Smart Forms
When creating a form one must:
1.      Retrieve the application data
2.      Describe the form
3.      Pass the application data to the form
Example: Create Smartform for printing Purchase order.
Retrieving the application data (Purchase Order information):
Write an ABAP program (Print Program) to retrieve data or include a retrieval routine into the application. This
code consists of statements that select data from databases according to certain selection criteria. Store the
retrieved data in internal tables, structures or variables and transfer it to the form in one step.
SAP has already provided with the Print Program (/SMB40/FM06P) for Purchase Order. Based on the business
requirement, this Print Program can be copied and modified to get the required data and transfer to Smartform.
Describing the Form:
The user defines the form using a Smartform. Use the tools of the form builder as listed below:
1.        Use the form painter to position the windows, graphics and addresses on a page.
2.        Use the PC editor to write the texts.
3.        Use the table painter to format the tables.
The flow control is used to print the pages and elements.
Form Logic (Introduction)
In the form builder one can describe a Smartform by a set of nodes. To do this, one can build up a tree structure on
the left side of the user interface.
The node global settings and its three successors form attributes, form interface and global definitions always exists
for any newly created forms.
To describe the form logic, create the hierarchy under the node pages and windows.
The following rules apply to control the flow of the form output.
1.        The nodes in the tree structure are processed from top to bottom.
2.        For each node there is a tab, this can be used to link the node to a condition. If the condition is true, the
system processes the node. If not, it skips the node and all its successors.
3.        One should define a next page for each page.
The SAP form builder of the smart form consists of:
1.        Form painter for creating the layout of the form
2.        PC Editor for entering texts and fields into output areas
3.        Navigation tree for maintaining the form logic
4.        Table painter for creating templates and tables
To define the text formats, one can use the Smart Styles.
Style builder:
On the left of the style builder screen consists of the predetermined nodes (header data, folder for paragraph
formats, and folder for character formats).
On the right one can see the maintenance screen with its tab pages. At the bottom the preview of the selected font
can be viewed.
Create Purchase Order Smartform
Create a Smartform, copy the existing SAP provided purchase order Smartform to ZSFM_PURCHASEORDER for
customizing as per business requirement.
1. Form Settings under Global Settings node, set the parameters in Output Option:
Page Format: Letter
Character per Inch: 20
Line per Inch: 6
Style: ZSTM_SMB40_SF
Output Format: Standard Output
2.        Form Interface
We can add parameters in the Import Parameters and tables in Tables tab of the form interface for the application
data to be available for the Smartform to print.
3. In Global definition we can define the all the global variables which can be used in Smartforms. Initialization
can be used for initializing the variables and even for retrieving the data.
Creating pages:
Each form consists of one or more pages. The first page in the tree structure is the start page and the
processing of the form starts with this page itself.
1.        Open the context menu for existing page node and choose create®page
2.        Enter a unique name (FIRST) for the node and a description (Page)
3.        Determine the format (1, 2, 3...)and the mode of the page counter (Increase counter) on the general
attributes tab
4.        Determine the print attributes (Portrait Format) of the page on the output options
5.        Determine a background graphic for the entire page on the background tab (Not used in PO).
Creating windows:
The size and position of the window can be graphically set in the form painter. There are main windows and
secondary windows. The difference between these two is that the output in a main window can cover several
pages.
1.        Open the context menu for an existing page node and choose®window
2.        Enter a name for the node (NAMEFORM) and a description (Title Window).
3.        On the general attributes indicate type of window. NAMEFORM is secondary window.
In similar fashion all the other windows are created and positioned as per the form design. Only one MAIN
window is created, it is used for line items which can cover several pages.
Positioning texts on the form
The texts are displayed in the form using text nodes. The only exceptions are addresses.
The predecessor node of the text node determines its use:
Predecessor node        Used to
Secondary window        Position text on one or more pages
Main window        Display text in relation to other nodes in the main window, it may cover several pages
Template         Displays texts for table cells of a static table
Table        Display table contents
There are three text types:
1.        Text element : to enter new text in the PC editor
2.        Text module : to include a text module
3.        Include text : to include an existing SAPscript text
Entering texts in PC editor: (TITLE)
·        To create a text node call the context menu for that node in the tree structure that should receive the
text, then choose->text
·        Enter a unique name (TITLE) for the node and the node description (TITLE)
·        On the general attributes tab choose text element as text type
·        In the text node box choose whether the text should be started with a new paragraph or only in a new
line
·        Enter the text in the PC editor. Text could be a program element like &Title& or Purchase Order. &Title&
is a variable for which the value is assigned in Program line before the text.
Including text modules: (TERMSCONDITION)
Text module of the text node is used to refer to an existing text module in the system. The text modules can be
used in two ways:
·        To create a text node, call the context menu for that node in the tree structure that shall contain the text
and choose create->text under the window TERMSCONDITION.
·        Enter a unique name for the node (TERMSCONDITION) and a description (Terms and Condition)
·        On the general attributes tab select the text type text module
·        Enter the name of the text module in the text name field (&G_TERMS_TEXT&). &G_TERMS_TEXT& is
used to determine the Text name dynamically in the program lines preceding the text module node.
·        Program Lines: GETTERMSCONDITION
Concatenate 'ZTMM_PO_TERMS_' ZXEKKO-BUKRS
                                  INTO G_TERMS_TEXT.
Including SAPscript texts: (HD_TXT_F01 Order Header Text)
The text type include text node to refer to a SAPscript text, which already exists in the system. To identify the
text the text name, object, id and the language is needed.
·        To create the text node, call the context menu for that node in the tree structure that shall receive the
text and choose create -> text under the main window.
·        Enter a unique name (HD_TXT_F01) for the node and the node description (Order Header Text).
·        On the general attributes tab choose include text as text type
·        Text Name - &ZEKKO-EBELN&, Text Object EKKO, Text ID F01, Language - &SY-LANGU&. Also check
mark No error if no text exists.
Tip: Since the size of text is not known, its better to have the text in MAIN window, so that it can run to more
than one page if required.
Inserting addresses: (SENDER):
Address node is used to insert an address into the form. This guarantees that the address is formatted
according to the postal rules of the sender country.
·        To create an address node , call the context menu for that node in the tree structure that one wants to
contain the text and choose create->Address
·        Enter a name for the node (COMPANY_CODE_ADDRESS) and a description (Company Code Address)
·        Determine the address type (Organization Address) on the general attributes tab
·        For organizational addresses - specify the address number, for any other - specify the person number
and the address number. In this case we get the company code address into variable &ADDNR&, so we need
program lines (SENDER) preceding the address text.
·        In the box additional addresses, attributes to specify how to display the address are maintained.
Printing graphics: (LOGO):
Tcode SE78 is used to import graphics into the SAP system. The transaction imports the graphics and stores it
in the BDS (business transaction server) and then it can be displayed in the form.
·        To create the graphic node , call the context menu for that node in the tree structure and choose create-
>graphic
·        Enter a name (LOGO) for the node and the description (Logo Graphic)
·        On the general attributes determine whether a colored or a black and white
·        On General Attributes use the fields object - GRPAHIC, id BMAP and name - &G_LOGO& to identify the
graphic. &G_LOGO& is variable and therefore we can print company code specific logo. Program line preceding
the graphic is required.
·        Program line COMP_LOGO is used to assign the value to G_LOGO. Concatenate 'ZCOMPANY_LOGO_'
ZXEKKO-BUKRS INTO G_LOGO. So, the name of graphic for example will be ZCOMPANY_LOGO_0202 for
company code 0202.
Displaying a static table (Window INFO, Template - TEM_INFO)
Use node type template to display a table whose layout and size is determined before the runtime of the print
program.
To create a template, define a table layout to determine the cell structure for each line. The cells are used to
display the cell structure for each line. The cells are used to display the contents of the successor nodes of the
template node.
·        Create Template under the INFO window node. Create > Template.
The template layout is used to determine the following,
1.        The number of lines and cells
2.        The height of each cell
3.        The width of each cell
4.        The alignment of the table in the window
5.        Whether and where to display separator lines or frames
Use the table control on the template tab to define the layout of the lines. Each line of the template must have
a definition.
Use the pattern box to select the desired table pattern.
Displaying contents in cells: (TLE_CONTACT)
The template node defines the table layout. The successor nodes of the template         determine the data to be
displayed in the table cells.
In General Attributes choose Text type Text Element. In editor, type DTE         Contact.
In Output Options, define the output structure LINE 5 and Column 1.
Similarly all other information for each cell can be filed using the text module and         address module.
Displaying Dynamic Table (ITEM_TABLE)
·        Create TABLE under the MAIN window node. In DATA Tab, loop through the data internal table.
L_XEKPO is the item table which has all the line item details.
Define the line types based on the positioning of the text in main window. For         example: TABLE_HEADER1
is used for positioning Header texts in the table.
·        Table is divided into three parts: Header, Main Area and Footer.
·        Header is used for printing the Header Title of the table and it at the start of the table on every page.
·         Main Area is used to print the line item details of the PO. Create a line (ITEM_DETAIL) of the line type
TABLE_HEADER1. It will dynamically generate number cells based on the line type defined in the table layout.
Name all the cells as per the usage. For each cell create the text node to display the information. For example:
Cell VAL_MATERIAL, Text node MATNR is created which has text element - -matnr.
·        Footer is used for printing the information after Main Area data is printed. This can be used for Total
printing or any other information which needs to be printed after all line items are printed. Create line
TLE_CONTR_STP for Contractual Stipulation of the line type LINE which has only one column. Create the
text element to print the information.
Special Requirement: Printing the Acknowledgement text if the order value is greater then USD 50,000.00 on
the second copy only.
·        This requirement needs the modification in the print program and the Smartform.
·        Modification in Print Program to trigger the second copy if the order value is greater then 50K. Its
advisable to copy the standard print program to custom Z program (Z_SMB40_FM06P), and changes should
be made to Z program. Number of copies is passed from NAST to ls_composer_param-tdcopies in Smartforms.
The value ls_composer_param-tdcopies is modified in the print program to 2 if the order value is greater then
50K.
·        The printing of Acknowledgement Text only on second copy is achieved using the COPIES WINDOW in
Smartforms. Define Window ACKN_COPY of the type COPIES WINDOW and Output to Only Copies Copies
Differ. Also set the condition in the Condition Tab of the window SFSY-JOBPAGES = 1, so that it only print
on the first page of the copy.
·        If user selects to print 2 copies and the order value is more then 50k, program needs to print 2 sets
meaning 4 copies. So number of copies is taken care of in Print program but again the printing of
Acknowledgement Text should be only the Even number copy meaning Copy# 2 and 4. This achieved by using
the program lines to determine the even copy. SFSY-COPYCOUNT will tell us the current copy number being
printed.
regards,
vineela.
Edited by: Radha Vineela Aepuru on Mar 13, 2008 11:12 AM

How to change the logon language in module pool program?

Hello All,
I had created a module pool program and had desiged a screen.
When i am logged in English language i am able to see them in english as per the requirement it is working fine.
But the requirement is wen i am logged in DE then the selection-screen texts should show in English and not in German.
Kindly give me a solution for this.
Thanks & Regards,
Rajesh Kumar

Hi Rajesh,
This problem is because you have maintained a standard dictionary fields on selection screen and all the standard dictionary fields are maintained in DE language, on the screen layout, go to the attributes of that particular text field, there is a option MODIFIZ for dictionary fields (it is a drop down), selection F TEXT, now whatever the text u will define, it will remain same for all the languages, once u do this then u again login in DE,l u will see the text maintained by u and not the DE text.
Do reply if problem still persist.
point if useful.
Rohit G
Edited by: Rohit Gaharwar on Aug 11, 2009 1:24 PM
Edited by: Rohit Gaharwar on Aug 11, 2009 1:30 PM
Edited by: Rohit Gaharwar on Aug 11, 2009 1:36 PM
Edited by: Rohit Gaharwar on Aug 11, 2009 1:36 PM
Edited by: Rohit Gaharwar on Aug 11, 2009 1:37 PM
Edited by: Rohit Gaharwar on Aug 11, 2009 1:38 PM

Module Pool - POV

hi ,
I want to display a given set of nationalities(25/250) in the combobox of my module pool screen.
I hav used POV as follows .
process on value-request.
field P0002-NATIO module onvalue_land1.
MODULE onvalue_land1 INPUT.
data : GT_LAND TYPE T005T OCCURS 10 WITH HEADER LINE .
DATA GT_RETURN like DDSHRETVAL occurs 0 with header line.
call function 'F4IF_INT_TABLE_VALUE_REQUEST'
exporting
retfield = 'NATI0'
dynpprog = sy-repid
dynpnr = sy-dynnr
dynprofield = 'P0002-NATIO'
value_org = 'C'
tables
value_tab = GT_LAND
return_tab = gt_return
exceptions
parameter_error = 1
no_values_found = 2
others = 3.
While running my Combo box is blank .
Wht could be the problem ?
Any help would be much apperciated .
Regrds,
J

Yes now am able to display the given fields in my List box . i hav used 'VRM_SET_VALUES' .
Now , While saving ....it's not converted to it's key automatically .
ex .. If i save the nationality "Swiss" it takes the two char SW and it's saving . But the actual key is "CH".
Am getting the following error status.
"entry - SW - doesn't exist in your check entry "
How to find the check entry .I hav used ,
SELECT * FROM T005T INTO TABLE I005T_LONG
WHERE SPRAS = SY-LANGU
AND ( LAND1 = 'IN' OR LAND1 = 'SW' )
Surly i will reward points to u all .
help plz .
Regrds ,
J
Message was edited by: P079223

POH in module pool.....have ur points..

Similar Messages

Maybe you are looking for