OO ABAP is a must or not for Module Pool

Hi all,
I want a valuable suggetion from you.
Is Object Oriented ABAP Programming is a must for Module Pool Programmer not. Because, I think I am preti much confident abt Module Pool but not in OO ABAP.
Please help me out my doubt.
Thanks & Regards,
Ajoy Chatterjee

Sorry, can't agree that they are obsolete... I've done dozens of dialog programs over the last few years, with more on the current "to do" list... it depends on what you client site are doing - if they want online data entry transactions inside the SAPGui, then that's what you build.
As you can't have screens in a class pool, so you're going to need to define these dynpros somewhere else (although my usual preference is having them within function groups rather than module pools).
But I do agree that getting your head around ABAP OO is unavoidable - and can add a level of elegance to your code if implemented well, and add a level of future-proofing when it comes time to change your presentation layer to Web Dynpro or whatever, or exposing some logic via web services.
However you can stil make "classic" ABAP elegant - there's little difference between the readability of :
call method z_my_class=>get_region_of_rental_object
exporting
    io_contract = ls_contract
importing
    rd_region   = l_region
    os_return   = ls_return
exceptions
    others      = 1.
and
call function 'Z_GET_REGION_OF_RENTAL_OBJECT'
exporting
    io_contract = ls_contract
importing
    rd_region   = l_region
    os_return   = ls_return
exceptions
    others      = 1.
i.e. it's often the way you modularise and encapsulate your logic that is the most important step.
Jonathan
p.s. perhaps this should head off to the Coffee Corner...!

Similar Messages

Hi i need material for module pool and alv's.

hi
i need material for module pool and ALV's(not object oriented) if any one have pls do send that to my
ID [email protected]
thanx in advance.

Hi
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
ALV
ABAP List Viewer
The common features of report are column alignment, sorting, filtering, subtotals, totals etc. To implement these, a lot of coding and logic is to be put. To avoid that we can use a concept called ABAP List Viewer (ALV).
This helps us to implement all the features mentioned very effectively.
Using ALV, We can have three types of reports:
1. Simple Report
2. Block Report
3. Hierarchical Sequential Report
There are some function modules which will enable to produce the above reports without much effort.
All the definitions of internal tables, structures and constants are declared in a type-pool called SLIS.
1. SIMPLE REPORT.
The important function modules are
a. Reuse_alv_list_display
b. Reuse_alv_fieldcatalog_merge
c. Reuse_alv_events_get
d. Reuse_alv_commentary_write
e. Reuse_alv_grid_display
A. REUSE_ALV_LIST_DISPLAY : This is the function module which prints the data.
The important parameters are :
I. Export :
i. I_callback_program : report id
ii. I_callback_pf_status_set : routine where a user can set his own pf status or change the functionality of the existing pf status
iii. I_callback_user_command : routine where the function codes are handled
iv. I_structure name : name of the dictionary table
v. Is_layout : structure to set the layout of the report
vi. It_fieldcat : internal table with the list of all fields and their attributes which are to be printed (this table can be populated automatically by the function module REUSE_ALV_FIELDCATALOG_MERGE
vii. It_events : internal table with a list of all possible events of ALV and their corresponding form names.
II. Tables :
i. t_outtab : internal table with the data to be output
B. REUSE_ALV_FIELDCATALOG_MERGE : This function module is used to populate a fieldcatalog which is essential to display the data in ALV. If the output data is from a single dictionary table and all the columns are selected, then we need not exclusively create the field catalog. Its enough to mention the table name as a parameter(I_structure name) in the REUSE_ALV_LIST_DISPLAY. But in other cases we need to create it.
The Important Parameters are :
I. Export :
i. I_program_name : report id
ii. I_internal_tabname : the internal output table
iii. I_inclname : include or the report name where all the dynamic forms are handled.
II Changing
ct_fieldcat : an internal table with the type SLIS_T_FIELDCAT_ALV which is
declared in the type pool SLIS.
C. REUSE_ALV_EVENTS_GET : Returns table of possible events for a list type
Parameters :
I. Import :
Et_Events : The event table is returned with all possible CALLBACK events
for the specified list type (column 'NAME'). For events to be processed by Callback, their 'FORM' field must be filled. If the field is initialized, the event is ignored. The entry can be read from the event table, the field 'FORM' filled and the entry modified using constants from the type pool SALV.
II. Export :
I_List_type :
0 = simple list REUSE_ALV_LIST_DISPLAY
1 = hierarchcal-sequential list REUSE_ALV_HIERSEQ_LIST_DISPLAY
2 = simple block list REUSE_ALV_BLOCK_LIST_APPEND
3 = hierarchical-sequential block list
REUSE_ALV_BLOCK_LIST_HS_APPEND
D. REUSE_ALV_COMMENTARY_WRITE : This is used in the Top-of-page event to print the headings and other comments for the list.
Parameters :
I. it_list_commentary : internal table with the headings of the type slis_t_listheader.
This internal table has three fields :
Typ : H header, S selection , A - action
Key : only when typ is S.
Info : the text to be printed
E. REUSE_ALV_GRID_DISPLAY : A new function in 4.6 version, to display the results in grid rather than as a preview.
Parameters : same as reuse_alv_list_display
This is an example for simple list.
2. BLOCK REPORT
This is used to have multiple lists continuously.
The important functions used in this report are:
A. REUSE_ALV_BLOCK_LIST_INIT
B. REUSE_ALV_BLOCK_LIST_APPEND
C. REUSE_ALV_BLOCK_LIST_HS_APPEND
D. REUSE_ALV_BLOCK_LIST_DISPLAY
A. REUSE_ALV_BLOCK_LIST_INIT
Parameters:
I. I_CALLBACK_PROGRAM
II. I_CALLBACK_PF_STATUS_SET
III. I_CALLBACK_USER_COMMAND
This function module is used to set the default gui status etc.
B. REUSE_ALV_BLOCK_LIST_APPEND
Parameters :
Export :
I. is_layout : layout settings for block
II. it_fieldcat : field catalog
III. i_tabname : internal table name with output data
IV. it_events : internal table with all possible events
Tables :
i. t_outtab : internal table with output data.
This function module adds the data to the block.
Repeat this function for all the different blocks to be displayed one after the other.
C. REUSE_ALV_BLOCK_LIST_HS_APPEND
This function module is used for hierarchical sequential blocks.
D. REUSE_ALV_BLOCK_LIST_DISPLAY
Parameters : All the parameters are optional.
This function module display the list with data appended by the above function.
Here the functions REUSE_ALV_FIELDCATALOG_MERGE, REUSE_ALV_EVENTS_GET, REUSE_ALV_COMMENTARY_WRITE can be used.
3. Hierarchical reports :
Hierarchical sequential list output.
The function module is
A. REUSE_ALV_HIERSEQ_LIST_DISPLAY
Parameters:
I. Export:
i. I_CALLBACK_PROGRAM
ii. I_CALLBACK_PF_STATUS_SET
iii. I_CALLBACK_USER_COMMAND
iv. IS_LAYOUT
v. IT_FIELDCAT
vi. IT_EVENTS
vii. i_tabname_header : Name of the internal table in the program containing the
output data of the highest hierarchy level.
viii. i_tabname_item : Name of the internal table in the program containing the
output data of the lowest hierarchy level.
ix. is_keyinfo : This structure contains the header and item table field
names which link the two tables (shared key).
II. Tables
i. t_outtab_header : Header table with data to be output
ii. t_outtab_item : Name of the internal table in the program containing the
output data of the lowest hierarchy level.
slis_t_fieldcat_alv : This internal table contains the field attributes. This internal table can be populated automatically by using REUSE_ALV_FIELDCATALOG_MERGE.
Important Attributes :
A. col_pos : position of the column
B. fieldname : internal fieldname
C. tabname : internal table name
D. ref_fieldname : fieldname (dictionary)
E. ref_tabname : table (dictionary)
F. key(1) : column with key-color
G. icon(1) : icon
H. symbol(1) : symbol
I. checkbox(1) : checkbox
J. just(1) : (R)ight (L)eft (C)ent.
K. do_sum(1) : sum up
L. no_out(1) : (O)blig.(X)no out
M. outputlen : output length
N. seltext_l : long key word
O. seltext_m : middle key word
P. seltext_s : short key word
Q. reptext_ddic : heading (ddic)
R. ddictxt(1) : (S)hort (M)iddle (L)ong
S. datatype : datatype
T. hotspot(1) : hotspot
Simple ALV report
http://www.sapgenie.com/abap/controls/alvgrid.htm
http://wiki.ittoolbox.com/index.php/Code:Ultimate_ALV_table_toolbox
ALV
1. Please give me general info on ALV.
http://www.sapfans.com/forums/viewtopic.php?t=58286
http://www.sapfans.com/forums/viewtopic.php?t=76490
http://www.sapfans.com/forums/viewtopic.php?t=20591
http://www.sapfans.com/forums/viewtopic.php?t=66305 - this one discusses which way should you use - ABAP Objects calls or simple function modules.
2. How do I program double click in ALV?
http://www.sapfans.com/forums/viewtopic.php?t=11601
http://www.sapfans.com/forums/viewtopic.php?t=23010
3. How do I add subtotals (I have problem to add them)...
http://www.sapfans.com/forums/viewtopic.php?t=20386
http://www.sapfans.com/forums/viewtopic.php?t=85191
http://www.sapfans.com/forums/viewtopic.php?t=88401
http://www.sapfans.com/forums/viewtopic.php?t=17335
4. How to add list heading like top-of-page in ABAP lists?
http://www.sapfans.com/forums/viewtopic.php?t=58775
http://www.sapfans.com/forums/viewtopic.php?t=60550
http://www.sapfans.com/forums/viewtopic.php?t=16629
5. How to print page number / total number of pages X/XX in ALV?
http://www.sapfans.com/forums/viewtopic.php?t=29597 (no direct solution)
6. ALV printing problems. The favourite is: The first page shows the number of records selected but I don't need this.
http://www.sapfans.com/forums/viewtopic.php?t=64320
http://www.sapfans.com/forums/viewtopic.php?t=44477
7. How can I set the cell color in ALV?
http://www.sapfans.com/forums/viewtopic.php?t=52107
8. How do I print a logo/graphics in ALV?
http://www.sapfans.com/forums/viewtopic.php?t=81149
http://www.sapfans.com/forums/viewtopic.php?t=35498
http://www.sapfans.com/forums/viewtopic.php?t=5013
9. How do I create and use input-enabled fields in ALV?
http://www.sapfans.com/forums/viewtopic.php?t=84933
http://www.sapfans.com/forums/viewtopic.php?t=69878
10. How can I use ALV for reports that are going to be run in background?
http://www.sapfans.com/forums/viewtopic.php?t=83243
http://www.sapfans.com/forums/viewtopic.php?t=19224
11. How can I display an icon in ALV? (Common requirement is traffic light icon).
http://www.sapfans.com/forums/viewtopic.php?t=79424
http://www.sapfans.com/forums/viewtopic.php?t=24512
12. How can I display a checkbox in ALV?
http://www.sapfans.com/forums/viewtopic.php?t=88376
http://www.sapfans.com/forums/viewtopic.php?t=40968
http://www.sapfans.com/forums/viewtopic.php?t=6919
Go thru these programs they may help u to try on some hands on
ALV Demo program
BCALV_DEMO_HTML
BCALV_FULLSCREEN_DEMO ALV Demo: Fullscreen Mode
BCALV_FULLSCREEN_DEMO_CLASSIC ALV demo: Fullscreen mode
BCALV_GRID_DEMO Simple ALV Control Call Demo Program
BCALV_TREE_DEMO Demo for ALV tree control
BCALV_TREE_SIMPLE_DEMO
BC_ALV_DEMO_HTML_D0100
Reward points if useful
Regards
Anji

Send me one link for module pool programming !

Send me the link Where i can get the screen shots step by step to create a simple module pool programming !

hi,
pls Go through this link for module pool programming
http://www.allsaplinks.com/dialog_programming.html
http://sap.mis.cmich.edu/sap-abap/abap09/
http://www.sapdevelopment.co.uk/dialog/dialoghome.htm
http://help.sap.com/saphelp_webas630/helpdata/en/9f/db9cdc35c111d1829f0000e829fbfe/content.htm
http://sap.mis.cmich.edu/abap-00/
http://www.allsaplinks.com/files/using_table_in_screen.pdf
http://help.sap.com/saphelp_46c/helpdata/en/08/bef2dadb5311d1ad10080009b0fb56/content.htm
http://www.sapgenie.com/links/abap.htm
http://help.sap.com/saphelp_nw04/helpdata/en/c9/5472fc787f11d194c90000e8353423/frameset.htm
http://www.sapdevelopment.co.uk/dialog/dialoghome.htm
http://help.sap.com
http://www.sapgenie.com/abap/example_code.htm
http://help.sap.com/saphelp_47x200/helpdata/en/52/670ba2439b11d1896f0000e8322d00/frameset.htm
http://www.allsaplinks.com/dialog_programming.html
http://www.sapbrain.com/TUTORIALS/default.html
http://www.sappoint.com/abap/spmp.pdf
http://sappoint.com/abap.html
http://www.sap-img.com/abap.htm
http://sap.ittoolbox.com/code/archives.asp?i=10&t=450&a=t
http://www.sapdevelopment.co.uk/dialog/dialoghome.htm
http://www.sap-img.com/abap/
http://www.sapdevelopment.co.uk/dialog/dialoghome.htm
http://www.sap-img.com/
http://www.sappoint.com/faq/faqdiapr.pdf
http://www.allsaplinks.com/dialog_programming.html
Reward Points if usefull
Regards
Fareedas

Variants for module pool screena

Hi,
I tried creating a variant for module pool screen by using the FM : RS_CREATE_VARIANT.
For this i created a dummy report which has the same parameters as the fields in the screen.
CALL FUNCTION 'RS_VARIANT_CONTENTS'
 EXPORTING
 report = gc_dummy_rep
 variant = 'variant5'
 MOVE_OR_WRITE = 'W'
 NO_IMPORT = ' '
 EXECUTE_DIRECT = ' '
 IMPORTING
 SP =
 tables
 L_PARAMS =
 L_PARAMS_NONV =
 L_SELOP =
 L_SELOP_NONV =
 valutab = lt_params
 OBJECTS =
 FREE_SELECTIONS_DESC =
 FREE_SELECTIONS_VALUE =
 EXCEPTIONS
 VARIANT_NON_EXISTENT = 1
 VARIANT_OBSOLETE = 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.
but when i try to retrieve the values stored in the variant using FM : RS_VARIANT_CONTENTS.
CALL FUNCTION 'RS_VARIANT_CONTENTS'
 EXPORTING
 report = gc_dummy_rep
 variant = 'variant5'
 MOVE_OR_WRITE = 'W'
 NO_IMPORT = ' '
 EXECUTE_DIRECT = ' '
 IMPORTING
 SP =
 tables
 L_PARAMS =
 L_PARAMS_NONV =
 L_SELOP =
 L_SELOP_NONV =
 valutab = lt_params
 OBJECTS =
 FREE_SELECTIONS_DESC =
 FREE_SELECTIONS_VALUE =
 EXCEPTIONS
 VARIANT_NON_EXISTENT = 1
 VARIANT_OBSOLETE = 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.
I get an error message : variant5 not found.
is there anything that i miss here?
or is the way i use to create variant for module pool screen not right?
Regards,
Kamini

Hi,
To avail save variant option in module pool screen,
1. You need to create a data base table similar to INDX table with the fields RELID, VARI_NAME
PROG_NAME
UNAME
SRTF2, MEMORYID, CLUSTR, CLUSID. And the remaining fields can be anything.
2. Enable the Save button in the Function keys part of GUI Status. And Add a push button for Get variant.
3. When Save button clicked call a screen with a single field for variant (let us say g_var). After g_var entered, in the PAI of the initial screen export all the screen values to the created database index using the statement .
 EXPORT: g_characteristics_tab TO DATABASE zav0257(ch) ID g_var,
 s_auart TO DATABASE zav0257(au) ID g_var.
 So that the values will be exported to database.
 Then update the fields(VARI_NAME,PROG_NAME,UNAME) of the database table using modify from work area.
 So that you will have the history of variance existence.
4. Next time , when the user clicks on Get Variant option, call another screen to enter the variant name. Then import the values for that variant from the memory id in the database table.
It worked for me.

How to conduct training for Module Pool Programming

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

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

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

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

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

Reg : Variant saving for Module Pool Programming

Hey Friends,
Plz help me in how to create variant for Module Pool Programming as in normal reports.Thanx in advance.

Hi,
You can create variants for Module pool program using the transaction SHD0. You can create Screen variants for your screens using this Tcode.
Go to SHD0 -> Give the Transaction code(ZTRAN) for which you want to create a variant -> name of some variant (ZVAR) -> create -> takes you to your transaction -> Give the values that you want to be displayed as variants -> Click on Save -> Opens a pop up to confirm the screen entries -> Check the check boxes of those fields that you have entered the data with (the column with check boxes that says W.Content) -> Exit and Save -> Save the variant -> You can see a screen variant created (ZVAR_0100)
Now Goto -> Create variant transaction -> Give your transaction variant name (ZVAR) -> Select Transaction with variant -> Takes you to SE93 transaction -> Give the transaction variant name -> save. Run with the created transaction.
Edited by: Nitwick on Jul 27, 2009 4:49 PM

Varient for module pool screen

can we create varient for module pool screen.

namaste anil anna.
how is pune .
how is erwada joil.
salman khan vunnada leda
Try out on the filled screen:
System - User defaults - Keep data
If you re-run it:
System - User defaults - Restore data
or try this link
http://help.sap.com/saphelp_nw04/helpdata/en/7d/f63a0a015111d396480000e82de14a/content.htm
regards
nagaraju madipadiga
hcl technologies
09958011191

Online Documentation for Module Pool Programs

Hi All,
Is it possible to display online documentation for module pool programs?
When the report program is excuted,we have an icon to display online documentation.Can we have the same for module pool ?
Helpful answers wouuld be rewarded.
Regards
Prathima

Hi Friend,
Continuing with previous post here...
Create a Push Button in application toolbar, check the function code in USER-COMMAND event.
There u write code to call function module DSYS_SHOW_FOR_F1HELP..
Pass DOKCLASS = RE
        DOKLANGU = sy-langu
        DOKNAME = 'Module pool name'
        SHORT_TEXT = 'X'.
It will populate the documentation window.
Regards
Krishnendu

Links/Docs for Module Pool Programing using abap objects

Hi all,
Can anyone send me links/docs related to Module Pool programing using Abap Objects.
Thanks n Regards
Maruthi Rao. A

hi maruthi rao,
check the below link
http://abapcode.blogspot.com/2007/06/object-oriented-alv-sample-program-to.html

Reusing Standard Classes for Module pool Programming using Abap Objects

Hi.,
    I debugged the ME21n transaction and found a number of classes such as
         CL_BASIC_MODEL_VIEW_MM
         CL_GENERIC_MODEL_VIEW_MM
         CL_GENERIC_VALUE_MODEL_MM
         CL_MODEL_CONTAINER_MM
         CL_MODEL_CONTROL_VIEW_MM
         CL_MODEL_VIEW_MM
         CL_TABLE_MODEL_MM
         CL_TABLE_MODEL_TREE_VIEW_MM
         CL_VALUE_MODEL_MM
         CL_VALUE_MODEL_VIEW_MM
         CL_BASIC_MODEL_VIEW_MM
        CL_COMPOSITE_SCREEN_VIEW_M
        CL_CUSTOM_CONTROL_VIEW_MM
        CL_EXPAND_BUTTON_VIEW_MM
        CL_EXPAND_VIEW_MM
        CL_FOREIGN_APPLICATION_VIE
        CL_GENERIC_MODEL_VIEW_MM
        CL_GRID_VIEW_MM
        CL_MODEL_CONTROL_VIEW_MM
       CL_MODEL_VIEW_MM
       CL_SCREEN_VIEW_MM
      CL_SETUPVIEW_BUILDER_MM
        CL_SIMPLE_TREE_VIEW_MM
         CL_TABLE_MODEL_TREE_VIEW_M
         CL_TABLE_VIEW_CONTAINER_MM
         CL_TABLE_VIEW_MM
         CL_TABSTRIP_VIEW_MM
         CL_TC_BUTTON_VIEW_MM
         CL_TC_ITEM_VIEW_MM
         CL_TOGGLE_VIEW_MM
         CL_VALUE_MODEL_VIEW_MM
         CL_DEFAULT_CONTROLLER_MM
         CL_CONTROLLER_MM
         CL_ATP_CONTROLLER_MM
         CL_DRAG_DROP_CONTROLLER_MM ..
               How we can reuse these classes to build a custom module pool program which supports MVC architecture as used in enjoy SAP transactions .I am very much confused from where to start .
Guide me on this.I want to create a simple module pool program with Subscreens, Table Controls and Tabstrips ..
Regards.,
S.Sivakumar

Have you got any solution on this.
because i want to use CL_GRID_VIEW_MM->handle_on_data_changed for one of my development related to ME51N.

How can one save variants for module pool screens.

hai all,
i have done a module pool screen for taking information from user..later i leave to list processor and give a report to the user.
i am testing the program with many input parameters.i don't want to enter the values each time i execute the program.can i not save a variant like i save for normal abap editor programs?
any other solution ?

Hii..
Variants can be created in Selection Screen only...
For ur Scenario:
To leave to the list use the Statements
LEAVE TO LIST-PROCESSING And return .
then the Data will be automatically retained.
Reward if Helpful

Update statement is not working. module pool program,why? check this code

*& Module Pool ZCUST_CALL_REC
PROGRAM ZCUST_CALL_REC.
TABLES: ZCUST_CALL_REC,ZREMARKS.
data: v_kun_low like ZCUST_CALL_REC-kunnr ,
 v_kun_high like ZCUST_CALL_REC-kunnr,
 v_bud_low like ZCUST_CALL_REC-budat,
 v_bud_high like ZCUST_CALL_REC-budat.
ranges r_kunnr for ZCUST_CALL_REC-kunnr .
ranges r_budat for zcust_call_rec-budat.
DATA: ITAB TYPE STANDARD TABLE OF ZCUST_CALL_REC WITH HEADER LINE,
 JTAB TYPE STANDARD TABLE OF ZREMARKS WITH HEADER LINE.
*data:begin of itab occurs 0,
 MANDT LIKE ZCUST_CALL_REC-MANDT,
 kunnr like ZCUST_CALL_REC-kunnr,
 budat like ZCUST_CALL_REC-budat,
 code like ZCUST_CALL_REC-code,
 remarks like ZCUST_CALL_REC-remarks,
 end of itab.
*data:begin of Jtab occurs 0,
 MANDT LIKE ZCUST_CALL_REC-MANDT,
 kunnr like ZCUST_CALL_REC-kunnr,
 budat like ZCUST_CALL_REC-budat,
 code like ZCUST_CALL_REC-code,
 remarks like ZCUST_CALL_REC-remarks,
 end of Jtab.
CONTROLS:vcontrol TYPE TABLEVIEW USING SCREEN '9001'.
CONTROLS:vcontrol1 TYPE TABLEVIEW USING SCREEN '9002'.
*start-of-selection.
*& Module USER_COMMAND_9000 INPUT
 text
MODULE USER_COMMAND_9000 INPUT.
CASE sy-ucomm.
WHEN 'BACK' OR 'EXIT' OR 'CANCEL'.
SET SCREEN 0.
LEAVE SCREEN.
CLEAR sy-ucomm.
WHEN 'ENQUIRY'.
perform multiple_selection.
perform append_CUSTOMER_code.
PERFORM SELECT_DATA.
call screen '9001'.
WHEN 'UPDATE'.
 perform append_CUSTOMER_code.
 PERFORM SELECT_DATA.
 call screen '9002'.
 perform update on commit.
WHEN 'DELETE'.
 perform append_CUSTOMER_code.
 PERFORM SELECT_DATA.
 call screen '9002'.
ENDCASE.
ENDMODULE. " USER_COMMAND_9000 INPUT
*& Module STATUS_9000 OUTPUT
 text
MODULE STATUS_9000 OUTPUT.
SET PF-STATUS 'ZCUSTOMER'.
SET TITLEBAR 'xxx'.
ENDMODULE. " STATUS_9000 OUTPUT
*& Module USER_COMMAND_9001 INPUT
 text
MODULE USER_COMMAND_9001 INPUT.
CASE sy-ucomm.
WHEN 'BACK' OR 'EXIT' OR 'CANCEL'.
SET SCREEN 0.
LEAVE SCREEN.
CLEAR sy-ucomm.
endcase.
ENDMODULE. " USER_COMMAND_9001 INPUT
*& Module STATUS_9001 OUTPUT
 text
MODULE STATUS_9001 OUTPUT.
SET PF-STATUS 'ZCUSTOMER'.
SET TITLEBAR 'xxx'.
move itab-MANDT to zcust_call_rec-MANDT.
move itab-kunnr to zcust_call_rec-kunnr.
move itab-budat to zcust_call_rec-budat.
move itab-code to zcust_call_rec-code.
move itab-remarks to zcust_call_rec-remarks.
vcontrol-lines = sy-dbcnt.
ENDMODULE. " STATUS_9001 OUTPUT
*& Module USER_COMMAND_9002 INPUT
 text
module USER_COMMAND_9002 input.
CASE sy-ucomm.
 WHEN 'BACK' OR 'EXIT' OR 'CANCEL'.
 SET SCREEN 0.
 LEAVE SCREEN.
 CLEAR sy-ucomm.
 WHEN 'UPDATE'.
 perform move_data.
 UPDATE ZCUST_CALL_REC FROM TABLE ITAB.
 IF SY-SUBRC = 0.
 MESSAGE I000(0) WITH 'RECORDS ARE UPDATED'.
 ELSE.
 MESSAGE E001(0) WITH 'RECORDS ARE NOT UPDATED'.
 ENDIF.
WHEN 'DELETE'.
 perform move_data.
 DELETE ZCUST_CALL_REC FROM TABLE ITAB.
 IF SY-SUBRC = 0.
 MESSAGE I000(0) WITH 'RECORDS ARE DELETED'.
 ELSE.
 MESSAGE E001(0) WITH 'RECORDS ARE NOT DELETED'.
 ENDIF.
endcase.
endmodule. " USER_COMMAND_9002 INPUT
*& Module STATUS_9002 OUTPUT
 text
module STATUS_9002 output.
SET PF-STATUS 'ZCUSTOMER1'.
SET TITLEBAR 'xxx'.
endmodule. " STATUS_9002 OUTPUT
*& Module update_table OUTPUT
 text
module update_table output.
 move itab-MANDT to zcust_call_rec-MANDT.
 move itab-kunnr to zcust_call_rec-kunnr.
 move itab-budat to zcust_call_rec-budat.
 move itab-code to zcust_call_rec-code.
 move itab-remarks to zcust_call_rec-remarks.
vcontrol-lines = sy-dbcnt.
endmodule. " update_table OUTPUT
***Selection Data
FORM SELECT_DATA.
SELECT mandt kunnr budat code remarks FROM zcust_call_rec INTO
 table itab
 WHERE kunnr IN r_kunnr AND BUDAT IN R_BUDAT.
ENDFORM.
****append vendor code
FORM APPEND_CUSTOMER_CODE.
clear r_kunnr.
clear itab.
clear r_budat.
refresh r_kunnr.
refresh itab.
refresh r_kunnr.
IF r_kunnr IS INITIAL
 AND NOT v_kun_low IS INITIAL
 AND NOT v_kun_high IS INITIAL.
 CALL FUNCTION 'CONVERSION_EXIT_ALPHA_INPUT'
 EXPORTING
 input = v_kun_low
 IMPORTING
 OUTPUT = r_kunnr-low.
 CALL FUNCTION 'CONVERSION_EXIT_ALPHA_INPUT'
 EXPORTING
 input = v_kun_high
 IMPORTING
 OUTPUT = r_kunnr-high.
 r_kunnr-option = 'BT'.
 r_kunnr-sign = 'I'.
 append r_kunnr.
 PERFORM V_BUDAT.
ELSEIF r_kunnr IS INITIAL
 AND NOT v_kun_low IS INITIAL
 AND v_kun_high IS INITIAL.
 CALL FUNCTION 'CONVERSION_EXIT_ALPHA_INPUT'
 EXPORTING
 input = v_kun_low
 IMPORTING
 OUTPUT = r_kunnr-low.
 r_kunnr-SIGN = 'I'.
 r_kunnr-OPTION = 'EQ'.
 APPEND r_kunnr.
 PERFORM V_BUDAT.
ELSEIF r_kunnr IS INITIAL
 AND v_kun_low IS INITIAL
 AND NOT v_kun_high IS INITIAL.
 CALL FUNCTION 'CONVERSION_EXIT_ALPHA_INPUT'
 EXPORTING
 input = v_kun_low
 IMPORTING
 OUTPUT = r_kunnr-low.
 r_kunnr-SIGN = 'I'.
 r_kunnr-OPTION = 'EQ'.
 APPEND r_kunnr.
 PERFORM V_BUDAT.
ELSEIF r_kunnr IS INITIAL
 AND v_kun_low IS INITIAL
 AND v_kun_high IS INITIAL.
 IF SY-SUBRC = 0.
 MESSAGE I003(0) WITH 'ENTER CUSTOMER NUMBER'.
 CALL SCREEN '9000'.
 ENDIF.
PERFORM V_BUDAT.
ENDIF.
ENDFORM.
FORM V_BUDAT.
IF R_BUDAT IS INITIAL
 AND NOT v_BUD_low IS INITIAL
 AND NOT v_BUD_high IS INITIAL.
 r_budat-low = v_bud_low.
 r_budat-high = v_bud_high.
 r_budat-option = 'BT'.
 r_budat-sign = 'I'.
 append r_budat.
 ELSEIF R_BUDAT IS INITIAL
 AND NOT v_BUD_low IS INITIAL
 AND v_BUD_high IS INITIAL.
 r_budat-low = v_bud_low.
 r_budat-high = v_bud_high.
 r_budat-option = 'EQ'.
 r_budat-sign = 'I'.
 append r_budat.
 ELSEIF R_BUDAT IS INITIAL
 AND v_BUD_low IS INITIAL
 AND NOT v_BUD_high IS INITIAL.
 r_budat-HIGH = v_bud_HIGH.
 r_budat-option = 'EQ'.
 r_budat-sign = 'I'.
 append r_budat.
 ELSEIF R_BUDAT IS INITIAL
 AND v_BUD_low IS INITIAL
 AND v_BUD_high IS INITIAL.
 IF SY-SUBRC = 0.
 MESSAGE I002(0) WITH 'ENTER POSTING DATE'.
 CALL SCREEN '9000'.
 r_budat-low = ''.
 r_budat-option = ''.
 r_budat-sign = ''.
 ENDIF.
 ENDIF.
ENDFORM.
*& Form update
 text
--> p1 text
<-- p2 text
form update .
commit work.
endform. " update
*& Form move_data
 text
--> p1 text
<-- p2 text
form move_data .
 clear itab.
refresh itab.
 move-corresponding zcust_call_rec to itab.
 MOVE ZCUST_CALL_REC-MANDT TO ITAB-MANDT.
 MOVE ZCUST_CALL_REC-KUNNR TO ITAB-KUNNR.
 MOVE ZCUST_CALL_REC-BUDAT TO ITAB-BUDAT.
 MOVE ZCUST_CALL_REC-CODE TO ITAB-CODE.
 MOVE ZCUST_CALL_REC-REMARKS TO ITAB-REMARKS.
 APPEND ITAB.
 delete itab where kunnr is initial.

Hi,
try to use
start-of-selection.
call screen 100.
module pai input.
endmodule
Reward points
Regards

Online Background job for Module pool program

Hi,
I need to process the dialog program in background. Normally for any executable report programs by default we will have that functionality. But i need the same functionality for my module pool program. User needs 2 execute buttons - one is for direct excute (foreground execute) and the other one is for back ground processing.
I tried with the 3 function modules job_open, job_submit & job_close. But i am keep on getting some issues and i am not sure how those will work because i wrote all the validations in direct exucte user command, now if user clicks on Background how that logic will be called and how it will be processed.
Can any one give your valuable suggestions.
regards
Jaya

Hi
Create a Transaction code for this Program.
Then implement the BDC Code to Process the SCreens with the Required input Values.
Schedule this BDC Session in Backgound using RSBDCSUB.
Reward if usefull

Select-option on subscreen for Module pool

Hi all,
I need to add some elements on standard screen of a standard transaction. Everything works fine, but the problem starts when I want to add select-option. It is displayed, but when I press on Multiple selection button no action occurs, no window appears...I simplified the case and created test program with test screen and also I get the same behaviour. Anyone had similiar problem?
Thnak you in advance for help,
Anna

I donot know how u have created the select-option. but u can try these 2 methods to create it. And I have checked that both of them work fine.
1) How to create a select-options in a module pool screen.
Method 1
a) Create a subscreen area in your screen layout where you want to create the select options.
b) In the top include of your module pool program declare a selection screen as a subscreen e.g.
 SELECTION-SCREEN BEGIN OF SCREEN 100 AS SUBSCREEN.
 select-options s_matnr for mara-matnr.
 SELECTION-SCREEN END OF SCREEN.
c) In the PBO and PAI of the main screen where the select options needs to be created do a call subscreen of the above screen (100).
 CALL SUBCREEN sub_area INCLUDING <program> <screen>
This call subscreen statement is necessary for transport of values between screen and program.
Note: All validations of the selection screen fields e.g. the s_matnr field created above should be done in selection screen events like AT SELECTION-SCREEN etc and not in PAI. These selection screen validations etc should be done in the top include only.
Method 2
a) Create 2 separate fields in your screen layout - one for the low value and one for the high value. Insert an icon beside the high value which will call the multiple selections popup screen on user command. Use function module COMPLEX_SELECTIONS_DIALOG to achieve this.
struc_tab_and_field-fieldname = con_cust. " 'KUNNR'
struc_tab_and_field-tablename = con_kna1. " 'KNA1'.
CALL FUNCTION 'COMPLEX_SELECTIONS_DIALOG'
 EXPORTING
 TITLE = ' '
 text = g_titl1 " 'Customers'
 tab_and_field = struc_tab_and_field
 TABLES
 RANGE = rng_kunnr
 EXCEPTIONS
 NO_RANGE_TAB = 1
 CANCELLED = 2
 INTERNAL_ERROR = 3
 INVALID_FIELDNAME = 4
 OTHERS = 5.
IF NOT rng_kunnr[] IS INITIAL.
 Read the very first entry of the range table and pass it to
 dynpro screen field
 READ TABLE rng_kunnr INDEX 1.
 IF sy-subrc = 0.
 g_cust = rng_kunnr-low.
ENDIF.
You can use the return table rng_kunnr to populate your own internal range table with the values entered by the user. Basically here you are just simulating the work of a select-options parameter by module pool screen elements.
Regards,
Joy.

OO ABAP is a must or not for Module Pool

Similar Messages

Maybe you are looking for