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

Similar Messages

How to find out no of customize module pool program in SAP

Hi All,
I want to find out number of customize module pool program, Workflow, number of changes made to standard SAP objects (SPAU/SPDD in our SAP system
Regards
Sagar

Join the table with TRDIR to find module-pool program (TRDIR-SUBC = 'M')
Regards,
Raymond
Aravind. R was faster...
Edited by: Raymond Giuseppi on Jun 18, 2009 12:56 PM

How to Upload a module Pool Program in SAP

Hello All,
I have downloaded My Program Using Report REPTRAN. Now i want to know how we can Upload the Module pool program and Reports in SAP .

Hi Ram,
Use open source project SAPLINK for downloading objects into files and uploading them into SAP. I think REPTRAN is only to download the source code.
Regards,
Shravan

How to down load the Module pool program from sap

hi friends,
i am having the Module pool program in one server
it consists of 1 screen.
now i want to down load the Module pool program into another server.
those two server are not linked.
is there any way to copy from one server to another server.
like what we do in smartfroms,that is downloading form and uploading the form.

Hi,
You can down load code from source system and u can upload those in your destination system. You can down load Code as normally like execute SE38 > enter ur program name> click on change button> Utilities(in menu bar)->more utilities>upload/down load>down load in source system & Just use same path with upload instead of down load. So this will help u to transfer code from one system to other.
Screens transfer: SE51> enter ur program name & screen no> click on change button> click on Layout button> Utilities(m)>upload/download>download for down loading a screen from source system.
And follow the same procedure in destination system also just use up load instead of download. to upload a screen in destination system.
Hope useful.
Regards,
BBR.

Checkbox positioning issue in module pool program screen

Hello All,
I am facing one issue with the checkbox positioning in module pool program.I have designed the screen in 'SAP Signature Theme' and the checkbox position looks fine (while tested the screen in SE80) as shown below.
Test Result from 'SAP Signature Theme':
But the lead has a different theme in his SAP system and he got the below result where the checkbox automatically shifts right with the same code and screen design as shown below.
Test Result from'Enjoy' theme :
Could you please help me resolve this strange issue as soon as possible.
Thanks in advance!!!
Thanks & Regards,
Hafizul

Hi Bhaskar,
Sure , in fact this is has been created by dragging and dropping of the the standard checkbox template availabe in the layout,no custom code has been written for this.
Please find the layout properties for this checkbox below.
P9021-COMPLI_CONF is one character field.
Please let me know if you need any other details on the same.
Thanks & Regards,
Hafizul

In module pool program - i want to control size of screen.

Hi,
In module pool program , I am handling 2 screen . while calling the 2 nd screen , i want to display the window size as i required.
Plz help me.
Regards,
Rani.

Hi,
Specify the positions as
CALL SCREEN dynnr
[STARTING AT col1 lin1
[ENDING AT col2 lin2]].
By default, the screens of all dynpros of the called dynpro sequence are displayed in the current window. Use addition STARTING AT to open a modal dialog window.
Addition
... STARTING AT col1 lin1 [ENDING AT col2 lin2]
Effect
Use addition STARTING AT to open a new popup level and to display all screens of the called dynpro sequence in a modal dialog window. The upper left corner of the dialog window is determined by the values col1 and lin1 for column and line. The values refer to the window with popup level 0. The lower right corner is set automatically or you can use col2 and lin2 to specify it after ENDING AT. For col1, lin1, col2 and lin2, data objects of type i are expected. The values of col1, lin1 should be smaller than those of col2, lin2, because otherwise the behavior is undefined. The maximum popup level is 9.
Pls reward points if solved your issue.
Regards,
Renjith Michael.

How to remove the print popup screen from module pool program

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

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

Function module / table which lists screen numbers in module pool program

Hi everyone,
I wish to make a list of all screen numbers used in my module pool program Is there any FM / table which maps module pool program name with all the screens used in it?
For example, if my module pool is SAPMZPROG and it has screens 9001, 9002 and 9003, then I want to have a report as follows:
Input to the report (selection screen): SAPMZPROG
Output:
9001
9002
9003
Thanks,
Shailesh

Hello
Try tables D020S, D020T

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

Drop down list in module pool program.

Hi Experts,
Can any one tell me how to maintain values in dropdown list on screen of module pool.
I have ' z' module pool program in which i have screen for z tcode and i want to add new values in drop down list . please tell me where to do modification.
Regards,
Rahul S

Hi,
Check the below code.
TYPE-POOLS: VRM.
DATA:V_NUM TYPE I.
DATA:NAME TYPE VRM_ID,
LIST TYPE VRM_VALUES,
VALUE LIKE LINE OF LIST.
DATA:I_WORKPATTERN LIKE ZWORKPAT OCCURS 0 WITH HEADER LINE.
DATA:ZPATTXT(60).
MODULE WORKPATTERN_LISTBOX OUTPUT.
NAME = 'P9434-ZWORKPATTERN'. --> Screen Field
IF V_NUM IS INITIAL.
CLEAR I_WORKPATTERN.
REFRESH I_WORKPATTERN.
SELECT *
FROM ZWORKPAT --> List box contents from the z table
INTO TABLE I_WORKPATTERN.
IF NOT I_WORKPATTERN[] IS INITIAL.
LOOP AT I_WORKPATTERN.
VALUE-KEY = I_WORKPATTERN-ZWORKPATTERN.
VALUE-TEXT = I_WORKPATTERN-ZWORKPATTERN.
APPEND VALUE TO LIST.
ENDLOOP.
ENDIF.
CALL FUNCTION 'VRM_SET_VALUES'
EXPORTING
ID = NAME
VALUES = LIST
EXCEPTIONS
ID_ILLEGAL_NAME = 1
OTHERS = 2.
IF SY-SUBRC 0.
CLEAR SY-SUBRC.
ENDIF.
V_NUM = V_NUM + 1.
ENDIF.
Regards,
Kumar Bandanadham
Edited by: Velangini Showry Maria Kumar Bandanadham on May 26, 2009 3:53 PM

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 make a fld mandatory in module pool program?

I need help on following 2 things
I have module pool program created, in that many screen subscreens created.
1.I want to make a field mandatory
second one is, I have a general tab and data tab.
General tab screen - 2101
Data tab = 2102
In general tab, I have edited the values (change mode), when change the values and try to save it,
It is holding old value.but If i exucute the transaction once again, it is showing the changed value(new value)
For ex: there is a date field value is 03/08/2009
If I change this to 03/09/2009 and press on Save button from the standard menu, still it is showing the value 03/08/2009. but I execute this transaction once again it is showing the value as 03/09/2009
I will be thankful if someone helps me here

Hi Chitra,
Go to the properties of the filed select program tab and say input required.
then you will get the problem solved.
For second one actually its saving but not displaying the saved value at the same time ,
for this you write the select statement after saving , so that once save is execute m, select statement also will execute and it will display the newly saved value.
so after saving imdeatly u write the select statement.
like case sy-ucomm.
when 'SAVE'.
insert ztable.
select filed from z table.
endcase.
let me know if ur problem solved.
Regards
Rajendra

How to store the variant in Module Pool Programming

Hi,
I have the module pool program which is having 4 screen. depends on the first and second screen, third screen is called. i want to store the data of third screen to the variant. All the screen except first screen is a subscreen.
Regards,
Dhiraj.

Hi Dhiraj,
You can create a variant only for a Report. Module Pool Programs require a dialog with the user & hence creating a varint is not possible. You can possibly create some Parameter IDs & default values in there.
Regards,
Suresh Datti

COPY THE STANDARD SAP MODULE POOL PROGRAM

HOW I CAN COPY THE STANDARD SAP MODULE POOL PROGRAM ((INCLUDING SCREENS) INTO Z REPORT?

Hi,
Go to transactionSE38 ABAP Editor.Type the program name.Click copy.It will ask whether you want copy documentation,screens,etc.,
Check mark it.

What is module pool programming?how we can change the standard screen?

Hi EXPERTS
what is module pool programming?how we can change the standard screen using module pool programming ?
please explain with example.

Check the below link:
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
http://www.geocities.com/ZSAPcHAT
http://www.allsaplinks.com/files/using_table_in_screen.pdf
http://help.sap.com/saphelp_webas630/helpdata/en/9f/db9cdc35c111d1829f0000e829fbfe/content.htm
http://www.sapdevelopment.co.uk/dialog/dialoghome.htm
http://www.sap-img.com/
http://help.sap.com/saphelp_46c/helpdata/en/08/bef2dadb5311d1ad10080009b0fb56/content.htm
http://www.sapgenie.com/links/abap.htm
http://help.sap.com/saphelp_nw04/helpdata/en/c9/5472fc787f11d194c90000e8353423/frameset.htm
You can also check the transaction ABAPDOCU which gives you lot of sample programs.
Also you can see the below examples...
Go to se38 and give demodynpro and press F4.
YOu will get a list of demo module pool programs.
One more T-Code is ABAPDOCU.
YOu can find more examples there.
See the prgrams:
DEMO_DYNPRO_TABLE_CONTROL_1 Table Control with LOOP Statement
DEMO_DYNPRO_TABLE_CONTROL_2 Table Control with LOOP AT ITAB
http://www.geocities.com/ZSAPcHAT
http://www.allsaplinks.com/files/using_table_in_screen.pdf
regards,
venkat.

Module Pool Programming - Calling SAP Standard Text Screen

Similar Messages

Maybe you are looking for