Application Development and Automation Discussions
Join the discussions or start your own on all things application development, including tools and APIs, programming models, and keeping your skills sharp.
cancel
Showing results for 
Search instead for 
Did you mean: 
Read only

module pool program

0 Likes
1,297

Hi all

can anybody send me some simple demo programs on module pool for learning if possible any documents.

As Iam been much cofused in understanding it.

Regards

Bhaskar

1 ACCEPTED SOLUTION
Read only

Former Member
0 Likes
964

Hi Bhaskar

I've some collection regarding Modulepool programs

If u provide me ur mail id, i can send u

5 REPLIES 5
Read only

Former Member
0 Likes
964

Hi Bhaskar,

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.

Refer below Links:

http://abaplovers.blogspot.com/2008/03/sap-abap-tutorial-module-pool.html

http://help.sap.com/saphelp_nw04/helpdata/en/9f/db9ce935c111d1829f0000e829fbfe/content.htm

http://help.sap.com/saphelp_crm30/helpdata/en/35/26b1aaafab52b9e10000009b38f974/content.htm

http://abaplovers.blogspot.com/2008/03/sap-abap-tutorial-module-pool_17.html

Regards,

Sunil

Read only

naimesh_patel
Active Contributor
0 Likes
964

You can find all type of example in your system ...

Go to SE38 ..

Enviornment > Examples > Ergonomics Examples > Screens

Regards,

Naimesh Patel

Read only

Former Member
0 Likes
964

The module pool consists of modularized ABAP/4 syntax which is placed inside include programs belonging to the dialog program.

These modules are invoked when called upon by flow logic.

Processing of flow logic and ABAP/4 modules is handled by different processors in the SAP system.

Flow logic is processed by the dialog processor while all ABAP/4 is processed by the ABAP/4 processor.

The ABAP/4 module pool consists of the following components:

The main program which will contain a series of include programs. Customer dialog programs should begin with SAPMZ or SAPMY.

Global data declarations in the form of a top include program. The program is named with the last five characters of the main program followed by ‘TOP’ (for TOP include). All data declarations will be placed within this program during development.

For modularization purposes, remaining ABAP/4 is developed using the following structure of include programs:

A PBO module include program is created to hold modules invoked by the PBO event of any of the screens in the dialog program. A PAI module include program is created to hold modules invoked by the PAI event of any of the screens in the dialog program. The proper naming convention uses the last five characters of the main program followed by either ‘O’ for PBO modules or ‘I’ for PAI modules, ending with a sequential number beginning with ‘01’. All PBO and PAI modules are placed inside their respective include program until the need for further modularization arises at which point a new include can be created using the next number in the sequence.

If further modularization is required a forms include program is created for subroutines name with the last 5 characters of the main program followed by ‘F’ for forms followed by a sequential number beginning with ‘01’.

Unlike report, interface, and conversion development which generally entails the creation of one autonomous program which can be executed independently of other objects, dialog program development entails development of multiple objects, none of which can be executed on its own. Instead, all objects are linked hierarchically to the main program and are executed in a sequence dictated by the program.

Dialog programs are composed of the following main components:

Screens

Module pool

Subroutines

Menus/GUI statuses

Transaction codes

Screens are made up of the following components:

Screen attributes

Screen layout/screen elements

Fields

Flow logic

Flow logic is comprised of two events:

The process before output (PBO) event invokes any processing which is to occur before the screen is displayed to the user.

The process after input (PAI) event invokes any processing which is to occur after the user has completed interaction with the screen by invoking any one of the possible functions (I.E. Save, back, enter, etc.).

U can find demo programs at the following :

[url]http://abapcode.blogspot.com/search/label/Dialog%20Programs

http://www.geocities.com/ZSAPcHAT[url];

<REMOVED BY MODERATOR>

Edited by: Alvaro Tejada Galindo on Apr 30, 2008 1:40 PM

Read only

Former Member
0 Likes
964

Hi

Refer these links

http://help.sap.com/saphelp_webas630/helpdata/en/9f/db9cdc35c111d1829f0000e829fbfe/content.htm

http://sap.niraj.tripod.com/id25.html

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

http://www.sapdomain.com/test.php?cat=13

u will get a clear idea on them..these include demo programs also..

thnx

sravani

<REMOVED BY MODERATOR>

Edited by: Alvaro Tejada Galindo on Apr 30, 2008 1:41 PM

Read only

Former Member
0 Likes
965

Hi Bhaskar

I've some collection regarding Modulepool programs

If u provide me ur mail id, i can send u