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

What are PBO Modules?

Former Member
0 Likes
6,583

What is PBO modules in a modular pool programming?

& how is this pbo modules triggered??

In what way do they function & why activating a normal screen we get this comment against the INCLUDE program name-

"PBO-Modules

1 ACCEPTED SOLUTION
Read only

Former Member
3,860

In the Dialog programming(Module Pool programming) basically two main events,,

PBO and PAI.

PBO(Process before Output ) is the default event which will get triggerred whenever there is a call to the screen you have designed.

it means it will processs or execute the entire code in that module before displaying the screen. usually the default values in the gui elements in that screen and their validations will be given in the PBO..

Say for an example you have designed a screen Ytest_screen with the number 100.

Screen will have these three elements :

1. Flow Logic,

2. Screen Layout

3. Field attributes.

In the screen layout you will design your screen and place all the gui elements(check boxes, buttons, input output fields table controls, tab strips etc etc).

For all these fields you will give some attributes (input only, Input/output enables, function codes for the push buttons, etc etc).

You will write the logic in the Flow logic.

In the flow logic you will by default have two events,, PBO and PAI.

when you uncomment any these modules, and double click on them,, it will take you the abap program assiciated to it.

and you will find module and endmodule.. you will have to write the entire logic for PBO and PAI in that module and endmodule.

when you run the transaction or the abap program, when you make a call to the screen..

initially PBO will get triggerred.

and in the screen when you perform any action, like pressing button etc.. PAI will get triggered and those events can be caught using the system variable called SY-UCOMM.

and after every PAI, by default PBO will again get triggered.

if you still have queries, don't hesitate to ask..

if found useful, don't forget to reward points.

Thanks-

Rahul

What is PBO modules in a modular pool programming?

& how is this pbo modules triggered??

In what way do they function & why activating a normal screen we get this comment against the INCLUDE program name-

"PBO-Modules

7 REPLIES 7
Read only

Former Member
0 Likes
3,860

Hi,

PBO---Process Before Output

--->this is the event in Module pool program.

--->this event functions same as Initialization event in Classical reporting.

-->the code under this event is triggered before displaying the screen.

Regards,

vineela

Read only

Former Member
0 Likes
3,860

Hi,

Process Before Output is screen event. Triggered by the ABAP runtime environement before a screen is sent to the presentation server. After PBO processing, screen fields receive the contents of data objects of the same name of the ABAP program.

check this link

http://help.sap.com/saphelp_46c/helpdata/en/fc/eb2d67358411d1829f0000e829fbfe/content.htm

regards

shibu

Edited by: shibuettickal on Mar 4, 2008 6:22 PM

Read only

Former Member
3,861

In the Dialog programming(Module Pool programming) basically two main events,,

PBO and PAI.

PBO(Process before Output ) is the default event which will get triggerred whenever there is a call to the screen you have designed.

it means it will processs or execute the entire code in that module before displaying the screen. usually the default values in the gui elements in that screen and their validations will be given in the PBO..

Say for an example you have designed a screen Ytest_screen with the number 100.

Screen will have these three elements :

1. Flow Logic,

2. Screen Layout

3. Field attributes.

In the screen layout you will design your screen and place all the gui elements(check boxes, buttons, input output fields table controls, tab strips etc etc).

For all these fields you will give some attributes (input only, Input/output enables, function codes for the push buttons, etc etc).

You will write the logic in the Flow logic.

In the flow logic you will by default have two events,, PBO and PAI.

when you uncomment any these modules, and double click on them,, it will take you the abap program assiciated to it.

and you will find module and endmodule.. you will have to write the entire logic for PBO and PAI in that module and endmodule.

when you run the transaction or the abap program, when you make a call to the screen..

initially PBO will get triggerred.

and in the screen when you perform any action, like pressing button etc.. PAI will get triggered and those events can be caught using the system variable called SY-UCOMM.

and after every PAI, by default PBO will again get triggered.

if you still have queries, don't hesitate to ask..

if found useful, don't forget to reward points.

Thanks-

Rahul

Read only

Former Member
0 Likes
3,860

Hi saswat mohanty ,

Welcome to SDN!!!!!

Process Before Output....

It triggers before the display of the selection screen. So whatever logic we write under this will be triggered before processing of selection screen.

It use for validation means if u want to change attributes of screen elements then u can do it here

Read only

Former Member
0 Likes
3,860

hi,

PBO module is similiar to intialisation in clasical reporting.

it is an event which is triggered before the screen is displayed to the user.

u can change the attributes of the screen and u can modify the screen for which the logic is to be written here.

regards,

bharathi

Read only

Former Member
0 Likes
3,860

Thanx to all for helping me out with those answers..

A special thanx to rahul malhotra ,as he took out some time to explain me through an example.

I got my answer ...Thanx to all of you.

Read only

Former Member
0 Likes
3,860

Hi Saswat,

These four are the events in modulepool programming.

PBO means Process before output. It triggers before the display of the selection screen or after the PAI of the Previous Screen. So whatever logic we write under this will be triggered before processing of selection screen. for example by setting context-specific field contents or by suppressing fields from the display that are not needed.

The other events in Module Pool - PAI,POH,POV.

Process After Input (PAI) event

Which is processed after a user action on the screen

Process on help request (POH)

which is processed when F1 is pressed

Process on value request (POV)

which is processed when F4 is pressed

Go through the Link:

PBO on the Selection Screen:

http://help.sap.com/saphelp_nw04s/helpdata/en/79/34a234d9b511d1950e0000e8353423/frameset.htm

Rewards Points if its Helpful to you.