Re: module pool programming

Former Member · ‎2006 Jun 01

hi all

can anyone just help me describing the complete flow in module pool programming

Former Member · ‎2006 Jun 01

Hi

Please check out this link for dialog or module pool programming

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

Please awards points if helpful

Former Member · ‎2006 Jun 01

Hi,

Please check transaction ABAPDOCU for sample

examples for dialog programing.

Dialog program consists of

1) process before output-> Event called before

screen is displayed

similar to at selection-

screen output in report

2) Process before input -> Event perform user

action Ex Buton click

3 ) Process on help request-> F1 help

4 process on value request: F4 help

Regards,

Amole

Former Member · ‎2006 Jun 01

hi

there are four important ecents in modulepool programming

PROCESS BEFOR OUTPUT(PBO)

PROCESS AFTER INPUT(PAI)

PROCESS ON HELP REQUEST

PROCESS ON VALUE REQUEST

when you execute the modulepool program with the help of the transaction

first it will go to the PBO of the first screen then screen will be displayed.

if you press enter or handle any button in that screen it will go to the pai of the screen.

from there if you call another screen it goes to the PBO of the next screen. like that the process repeats.

if there is no next screen it again goes to the same screen pbo.

Former Member · ‎2006 Jun 01

Hi,

first of all, you have to create a program type module pool program. this can be done in SE80 transaction.

There the program will have 4 includes:

TOP include is use for the declaration of the variables and internal tables.

IN include includes the code written in PAI event.

OO include has the code in PBO event of the screen.

F include for function modules.

These includes improve the modularity of the program.

Once you have create the program, you have to create a screen. There, you have to create the layout for the screen, activate it and in the flow logic you have to write the logic in PBO and PAI event in different modules (IN and OO). After writing the logic, we can create a transaction for running the program.

When a program is executed, first the PBO event of the screen is executed, from there(the flow logic of the screen), the control moves on to the module pool program(different modules in PBO event). Then, when the user does any action, clicks any buttonfor example, then the control goes to the PAI event(same way from the flow logic to the different modules in the module pool program).

This way, the program is executed.

Regards,

Aswin

rahulkavuri · ‎2006 Jun 01

Screen Flow Logic

You can go to this screen either by

Initial screen of Screen painter  Flow logic

Or

From Screen attribute screen  Flow logic

When transaction is executed, the screen is displayed, user enters few fields, selects few functions. Later the screen is processed and processing of screen is done by flow logic. The events that are associated with screen are as follows:

• Process before Output (PBO)

• Process after input (PAI)

• Process on value request (POV)

• Process on help request (POH)

The system automatically displays two very important events or modules in flow logic i.e. PAI and PBO

PBO event

This event is triggered before the screen is displayed. The processing of screen before the display of screen is done in this event. For example, filling in default values in the screen fields.

PAI event

This event is responsible for processing of screen after the user enters the data and clicks the pushbutton. The processing of screen can include displaying another screen, or just displaying list or quitting the transaction itself and many more things. Usually it is displaying another screen. These operations can be carried out in the PAI event. OKCODE plays an important role in this operation.

POV event

Process on value request is triggered when the user clicks F4 key. You can handle this event when the user presses F4 key by writing code for the same in module pool program. Normally when the user presses F4, list of possible values is displayed. The standard list produced by system is adequate for applications you develop yourself. However, you can also have the option of setting up your own documentation and lists of possible values that are more detailed.

POH event

Normally when the user places the cursor on the field and presses F1 function key, the system displays its own Help for that particular field. You can add your own functionality to the Help button by writing code for the same in the POH event.

<b>Please refer the above and award points if found helpful</b>