Solved: Re: MODULE POOL / MODULE PROGRAMMING / DIALOGUE PR...

If it is not there (not supporting the sap(not there in sap) For that we have crate the table and we have to update the table for that we can go for the Dialod programming.

Module pools are directly created using the ABAP Editor and are introduced with the PROGRAM statement. With the exception of reporting event blocks and function modules, module pools can contain all processing blocks supported in ABAP and as many local classes as required. While they are executed, all events of the ABAP runtime environment may be triggered.

The most important technical attribute of a module pool is that it can only be controlled using screen flow logic. You must start them using a transaction code, which is linked to the program and one of its screens (initial screen). Another feature of these programs is that you must define your own screens in the Screen Painter (although the initial screen can be a selection screen).

When you start a program using a transaction code, the runtime environment starts a processor that calls the initial screen. This then calls a dialog module in the corresponding ABAP program. The remainder of the program flow can take any form. For example, the dialog module can:

· return control to the screen, after which the processing passes to a subsequent screen. Each screen has a following screen, set either statically or dynamically. Screens and their subsequent screens are components of freely definable screen sequences.

· call other screen sequences, selection screens or lists, from which further processing blocks in the ABAP program are started.

· call other processing blocks itself, either internally or externally.

· call other application programs using CALL TRANSACTION or SUBMIT.

It is appropriate to use module pools when you write dialog-oriented programs using a large number of screens whose flow logic largely determines the program flow of screen sequences.

Check these links.

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

This link will give u a step by step procedure.

http://sap.mis.cmich.edu/sap-abap/abap09/sld007.htm

Regards,

Priyanka.

Former Member · ‎2007 May 16

All are one and the sale .

people use to call it as module pool because it was driven through module's

like PBO,PAI ,POH,POV Modules .

Dialog means screen by screen , in the screen module by module so the meaning of the navigation is called Dailog .

ofcus you are doing all sort of programing in th all the modules so it can be called as Module pool programming .

moral is : Module Pool Programming /Dailog Programming

Girish

Former Member · ‎2007 May 16

well,

Can anyone please explain me PBO and PAI..??

Because, I feel they are the same..

When u insert an input, that triggers ---> PAI(Process after Input)

and then the output comes (So that is Process Before Output)..

SO ultimately PAI == PBO..

is this true?!!

Explain!!

Thanks!

Former Member · ‎2007 May 16

Hai,

PBO triggers while we r giving Execute from the Report program.After Entering the Input it will Triggers PAI.

Regards,

Padmam.

Former Member · ‎2007 May 16

hi PBO (process before output) it triggers before the output of the report

PAI(process after input) it triggers befores the output disply(selection screen)

from above links u may get total details

reward if it helps u

vijay pawar

Former Member · ‎2007 May 16

HI,

PAI->process after input.it will trigger imeediately after calling the screen and before showing the screen.

PBO->process before output.it will trigger after user has given any input and click on any button or menu item.

example

*****************************

&----

*& Module pool ZBHMOD2 *

*& *

&----

*& *

&----

REPORT ZBHMOD2.

DATA: OKCODE1 TYPE SY-UCOMM,

OKCODE2 TYPE SY-UCOMM,

ENAME(10) TYPE C,

DNAME(10) TYPE C.

MODULE STATUS_1000 OUTPUT.

SET PF-STATUS 'xxxxxxxx'.

SET TITLEBAR 'TIT1'.

ENDMODULE. " STATUS_1000 OUTPUT

MODULE STATUS_1001 OUTPUT.

SET PF-STATUS 'xxxxxxxx'.

SET TITLEBAR 'TIT2'.

ENDMODULE. " STATUS_1001 OUTPUT

MODULE USER_COMMAND_1000 INPUT.

CASE OKCODE1.

WHEN 'BACK'.

SET SCREEN '0'.

WHEN 'NEXT'.

DNAME = ENAME.

SET SCREEN '1001'.

ENDCASE.

ENDMODULE. " USER_COMMAND_1000 INPUT

MODULE USER_COMMAND_1001 INPUT.

CASE OKCODE2.

WHEN 'BACK'.

SET SCREEN '1000'.

ENDCASE.

ENDMODULE. " USER_COMMAND_1001 INPUT

FORM ON_CTMENU_FORM USING ZDEMO1 TYPE REF TO CL_CTMENU.

CALL METHOD ZDEMO1->LOAD_GUI_STATUS

EXPORTING

PROGRAM = 'ZDEMO1'

STATUS = 'ZDEMO1'

MENU = ZDEMO1.

ENDFORM. " ON_CTMENU_FORM

FLOW LOGIC:

PROCESS BEFORE OUTPUT.

MODULE STATUS_1000.

*

PROCESS AFTER INPUT.

MODULE USER_COMMAND_1000.

PROCESS BEFORE OUTPUT.

MODULE STATUS_1001.

*

PROCESS AFTER INPUT.

MODULE USER_COMMAND_1001.

rgds,

bharat.

Former Member · ‎2007 May 16

Hai,

Actually Dialog Programming is Module pool Programming.

Please go thru this , see if your dbout gets clear.

Basic components of dialog program :

- Screens (Dynpros)

- Each dialog in an SAP system is controlled by dynpros.A dynpros 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.

check this link:

http://help.sap.com/printdocu/core/Print46c/en/data/pdf/BCDWBTUT/BCDWBTUT.pdf

http://help.sap.com/saphelp_40b/helpdata/en/d3/2e974d35c511d1829f0000e829fbfe/applet.htm

Have a look at these good links-

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