topic Re: module pool programe in Application Development and Automation Discussions

module pool programe

Former Member — Thu, 12 Jul 2007 04:38:02 GMT

hi all,

i want to create module pool programme.

tell me the steps.

i want to develop one selection screen by that selection i want to display that data in screen.

Re: module pool programe

Former Member — Thu, 12 Jul 2007 04:41:17 GMT

Hi,

goto <b>abapdocu</b> tcode

select ABAP User Dialogs ->Screens->Processing Screens

see all those programs,they will be surely helpful to u.

rgds,

bharat,

Re: module pool programe

Former Member — Thu, 12 Jul 2007 04:41:59 GMT

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

<b>Reward points if useful</b>

Regards

Ashu

Re: module pool programe

Former Member — Thu, 12 Jul 2007 04:43:14 GMT

hi,

wher can i get userdailog

Re: module pool programe

Former Member — Thu, 12 Jul 2007 04:46:46 GMT

Hi venkat

Use bcalv* in program and select f4, you will get all the alv programs.

regards,

prasanth

*reward if helpful

Message was edited by:

Prasanth Narayanasetty

Re: module pool programe

Former Member — Thu, 12 Jul 2007 04:48:54 GMT

hi,

goto SE80 ->

give program name ->

create or click on save ->

give type M for report program ->

give top include if u want or disable that check box ->

right click on program name ->

select create screen ->

u ll get flow logic and decomment the pbo and pai module ->

click on layout and design the screen -> activate ->

double click on pbo module and decomment title bar and menu status [create as required] save -> back ->

double click on pai module -> write ur code in this pai module -> activate ->

right click on program ->

create a transaction ->

give transaction name starting with Z******* and select GUI FOR WINDOWS radio button -> save ->

back -> activate ->

create a new session -> give transaction code which u have created in command box

if helpful reward some points.

with regards,

Suresh.A

Re: module pool programe

Former Member — Thu, 12 Jul 2007 07:53:47 GMT

hi,

1) Create zreport save and activate and close

2) then go to SE51 type same z report name and give screen No.

3) click on change button on se51 then remove comment from PBO , PAI event.

4) click on layout button and desing screen as per your requirment , save check, and activate

5) click on PBO and PAI events write some code there.

now come to se38 select your z report and

before calling Module pool write

CALL SCREEN 'screen-number' which you have selected during createion in se51.

save check and activate.

Rewards if yousfull.

Re: module pool programe

Former Member — Thu, 12 Jul 2007 09:10:26 GMT

ABAP Report Types

ABAP report types are those ones available in some report's attributes screen, i.e. :
· Executable program
· Function group (containing function modules)
· Include
· Interface pool
· Class pool
· Module pool
· Subroutine pool

ABAP/4 Module Pool
In the Object Browser, the module pool code belongs to one of the following categories:
Global fields:
data declarations that can be used by all modules in the module pool
PBO modules:
modules that are called before displaying the screen
PAI modules:
modules that are called in response to the user input
Subroutines:
subroutines that can be called from any position within the module pool

By default, the system divides a module pool into one or several include programs. An include program can contain several modules of the same type (only PBO modules or only PAI modules). The main program then consists of a sequence of INCLUDE statements that link the modules to the module pool:

*&--------------------------------------------------------------- 
*&
*& Module pool      SAPMTZ10 
*& 
*&--------------------------------------------------------------- 
*& 
*& Display data of Table SPFLI 
*& 
*&--------------------------------------------------------------- 

* Global data 
INCLUDE MTZ10TOP. 

* PAI modules 
INCLUDE MTZ10I01. 

* PBO modules 
INCLUDE MTZ10O01. 
In the ABAP/4 editor, you can display the code hidden behind the INCLUDE statements by choosing Edit ---> More functions ---> EXPAND include. With all INCLUDE statements expanded, the module pool looks like this: 
*&--------------------------------------------------------------- 
*& Module pool      SAPMTZ10 
*&           FUNCTION: Display data from Table SPFLI 
*& 
*&--------------------------------------------------------------- 
*----------------------------------------------------------------- 
* INCLUDE MTZ10TOP (This is the TOP include: 
* the TOP module contains global data declarations) 
*---------------------------------------------------------------- 
PROGRAM SAPMTZ10. 
     TABLES: SPFLI. 

     DATA OK_CODE(4). 

*---------------------------------------------------------------- 
* INCLUDE MTZ10I01 (This is a PAI include.) 
*---------------------------------------------------------------- 
*&--------------------------------------------------------------- 
*& Module USER_COMMAND_0100 INPUT 
*&--------------------------------------------------------------- 
* Retrieve data from SPFLI or leave transaction 
*---------------------------------------------------------------- 
MODULE USER_COMMAND_0100 INPUT. 
CASE OK_CODE. 
     WHEN 'SHOW'. 
          CLEAR OK_CODE. 
          SELECT SINGLE * FROM SPFLI WHERE CARRID = SPFLI-CARRID 
                                                                  AND       CONNID = SPFLI-CONNID. 
     WHEN SPACE. 
     WHEN OTHERS. 
          CLEAR OK_CODE. 
          SET SCREEN 0.
          LEAVE SCREEN. 
     ENDCASE. 
ENDMODULE. 
*---------------------------------------------------------------- 
* INCLUDE MTZ10O01 (This is a PBO include.) 
*---------------------------------------------------------------- 
*&--------------------------------------------------------------- 
*& Module STATUS_0100 
*&--------------------------------------------------------------- 
* Specify GUI status and title for screen 100 
*---------------------------------------------------------------- 
MODULE STATUS_0100. 
     SET PF-STATUS 'TZ0100'. 
     SET TITLEBAR '100'. 
ENDMODULE.

You use the ABAP/4 Dictionary to store frequently used data declarations centrally. Objects defined in the Dictionary are known throughout the system. Active Dictionary definitions can be accessed by any application. Data defined in the Dictionary can be included in a screen or used by an ABAP/4 program. You declare global data in the TOP module of the transaction, using the TABLES, STRUCTURE, LIKE statements and others. Transaction TZ10 accesses the Dictionary definition of Table SPFLI to provide the desired flight data display. If the TOP include contains the TABLES: SPFLI declaration, all modules in the module pool can access the table fields of Table SPFLI.

The PAI module USER_COMMAND_0100 checks which pushbutton the user activated (CASE OK_CODE). The Display pushbutton in Transaction TZ10 has the function code 'SHOW'. The program then tries to select those records in the SPFLI database that correspond to the data the user entered. The WHERE condition determines matching records by comparing the fields SPFLI-CARRID and SPFLI-CONNID with the database key fields CARRID and CONNID. As soon as a matching record is found, the database transfers all accompanying SPFLI fields to the program table.

When the screen is displayed again, the complete information appears in the output fields of the screen. The system automatically displays these fields, since the ABAP/4 field names SPFLI-CARRID and SPFLI-CONNID are the same as the screen field names.

In the PBO module STATUS_0100 of Transaction TZ10, the screen 100 receives a GUI status (using SET PF-STATUS) and a GUI title (using SET TITLEBAR):

SET PF-STATUS 'TZ0100'. 
SET TITLEBAR '100'.

A GUI status is a subset of the interface elements used for a certain screen. The status comprises those elements that are currently needed by the transaction. The GUI status for a transaction may be composed of several elements.

The GUI title is the screen title displayed in the title bar of the window. In contrast to the GUI status that can be used for several screens, a GUI title belongs to one screen.

To create and edit GUI status and GUI title, you use the Menu Painter. To start the Menu Painter, create a GUI status or GUI title in an object list in the Object Browser (or double-click on an existing status or title).

For more information on the Menu Painter, see the SAP documentation ABAP/4 Development Workbench: Tools.

Interactions between Screens and ABAP/4 Modules

In its most simple form, a transaction is a collection of screens and ABAP/4 routines, controlled and executed by a dialog processor. The dialog processor processes screen after screen, thereby triggering the appropriate ABAP/4 processing for each screen.

For each screen, the system executes the flow logic that contains the corresponding ABAP/4 processing. The control passes from screen flow logic to ABAP/4 code and back.

The sequence of events for Transaction TZ10, for example, looks like this:

1. In the PBO event, the statement MODULE STATUS_0100 passes control to the corresponding ABAP/4 module. In the ABAP/4 module pool, the screen to be displayed receives a menu interface.

2. After processing the module STATUS_0100, control returns to the flow logic. For the PBO event, no further processing is required. The system display the screen and receives entries from the user. The entries are:

§ the values for the fields Company and Flight number.

§ the four-character function code that tells which pushbutton the user activated.

3. The user input triggers the PAI event. The first PAI statement passes control to the ABAP/4 module USER_COMMAND_0100. Module USER_COMMAND_0100 processes the requests of the user. In our example, only one request is possible: displaying the flight data for the specified flight. The ABAP/4 statement SELECT retrieves the data from the database and displays it.

4. After processing MODULE USER_COMMAND_0100, control returns to PAI. This terminates the dialog.

Communication: Screen – ABAP/4 Module Pool

The screen flow logic is divided into two events for each screen:
· The PROCESS BEFORE OUTPUT event (PBO) is executed before the screen is displayed.
· The PROCESS AFTER INPUT event (PAI) is executed after the user has pressed ENTER.
· The system processes the modules in an event sequentially.
· In each module, control passes from the dialog processor to the ABAP/4 processor. After processing, control is returned to the dialog processor.
· When all the PBO modules have been processed, the contents of fields in the ABAP/4 work area are copied to the identically named fields in the screen work area.
· Before the PAI module is processed, the contents of fields in the screen work area are copied to the identically named fields in the ABAP/4 work area.

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. The flow logic of a dynpro contains calls of modules from the corresponding module pool. Interactive modules called at the PBO event are used to prepare the screen template in accordance to the context, for example by setting field contents or by suppressing fields from the display that are not needed. Interactive modules called at the PAI event are used to check the user input and to trigger appropriate dialog steps, such as the update task.

All dynpros to be called from within one transaction refer to a common module pool. The dynpros of a module pool are numbered. By default, the system stores for each dynpro the dynpro to be displayed next. This dynpro sequence or chain can be linear as well as cyclic. From within a dynpro chain, you can even call another dynpro chain and, after processing it, return to the original chain.

Reward all helpfull answers

Regards

Pavan

Message was edited by:

Pavan praveen

Re: module pool programe

hermanoclaro — Thu, 12 Jul 2007 12:40:45 GMT

Hi,

You can create a module pool program accessing transaction SE80 and creating a new program of the type module pool. A module pool program is basically a pool of includes that separates the functionalities like PBO, PAI, etc.

After the program creation, you need to uncomment the includes of the main program and create them. Now, create a new windows, by right-clicking the main program name in the left menu and clicking Create>Screen.

There's a program to draw your screen, you can access it by selecting your screen and clicking the button "Screen Painter" (if I'm correct).

Reward with points if usefull.

Regards,

-h