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

module pool tips

Former Member — Thu, 06 Dec 2007 10:21:09 GMT

hai to al.

iam creating transaction screens .

in that i want to create , change and display the screen .

for that iam creating a screen .

what are the function modules to save the data .

can any body suggest the module pool tips for creating screen.

Re: module pool tips

Former Member — Thu, 06 Dec 2007 10:23:24 GMT

Hi,

Check this links.

http://www.thespot4sap.com/Articles/SAP_Design_Dynpro.asp

http://www.sapgenie.com/abap/functions.htm

Regards,

Maha

Re: module pool tips

VikasB — Thu, 06 Dec 2007 10:49:04 GMT

Hi Satya,

You can create Module Pool from Tcode SE38, give the Report type as 'Module Pool' instead of 'Executable Report'.

Module pool contains only PBO and PAI modules for series of screen you hav craeted. you can create buttons for CREATE and CHANGE the data and depending upon the value of SY-UCOMM u can save that data using SQL statements like INSERT, MODIFY..

regards,

vikas

plz reward if helpful

Re: module pool tips

Former Member — Thu, 06 Dec 2007 11:13:58 GMT

Hi Satya,

For module pool u can create sceens in SE51 i think it is known to you.

Module pool programms consits of PAI and PBO events.

As per ur requiremnt u can use this Events. If you want to create , change and display use the fuction code for that. In SE51 u are having option such as button for each button assian one function key

ex: For dispay button assign ur own function text = 'DISP'.

And use these function keys in ur program using CASE.

For user fuction key we use SY-UCOMM. system defind

Ex:

Case SY-UCOMM.

when 'DISP'

write your source code here wht u want to display in PBO or PAI event.

endcase.

Depending up on the function key u can write the code what u want to do below the function key.

No need of function modules in this case. Read the Documentation about PAI and PBO events before dealing with module pool programmes.

if any thing j

<b>reward if useful</b>

Regards,

sunil kairam.

Re: module pool tips

Former Member — Thu, 06 Dec 2007 11:17:34 GMT

Read this it will help u.

Screen Flow Logic

Screen flow logic contains the procedural part of a screen. You create it in the flow logic editor in the Screen Painter, which is very similar to the ABAP Editor. The language used to program screen flow logic has a similar syntax to ABAP, but is not part of ABAP itself. It is sometimes referred to as screen language.

Unlike ABAP programs, screen flow logic contains no explicit data declarations. You define screen fields by placing elements on the screen mask.

The screen flow logic is like an ABAP program in that it serves as a container for processing blocks. There are four event blocks, each of which is introduced with the screen keyword PROCESS:

PROCESS BEFORE OUTPUT.

...

PROCESS AFTER INPUT.

...

PROCESS ON HELP-REQUEST.

...

PROCESS ON VALUE-REQUEST.

As in ABAP, the event block is introduced by the corresponding keyword statement, and it concludes either when the next block is introduced, or at the end of the program. The first two statements are created automatically by the Screen Painter when you create a new screen. The corresponding events are triggered by the runtime environment:

· PROCESS BEFORE OUTPUT (PBO) is automatically triggered after the PAI processing of the previous screen and before the current screen is displayed. You can program the PBO processing of the screen in this block. At the end of the PBO processing, the screen is displayed.

· PROCESS AFTER INPUT (PAI) is triggered when the user chooses a function on the screen. You can program the PAI processing of the screen in this block. At the end of the PAI processing, the system either calls the next screen or carries on processing at the point from which the screen was called.

· PROCESS ON HELP-REQUEST (POH) and PROCESS ON VALUE-REQUEST (POV) are triggered when the user requests field help (F1) or possible values help (F4) respectively. You can program the appropriate coding in the corresponding event blocks. At the end of processing, the system carries on processing the current screen.

As is normal with events, you must only program event blocks for the events to which you want the flow logic to react. However, the screen flow logic must contain at least the two statements PROCESS BEFORE OUTPUT and PROCESS AFTER INPUT in the correct order.

Example of Flow Logic Example

The following example shows some use of screen flow logic:

*----

Sample Code

*----

*Processing Before Screen Output

PROCESS BEFORE OUTPUT.

MODULE INIT_FIELDS.

Self-programmed F1 Help

PROCESS ON HELP-REQUEST.

FIELD GSSG-BUKRG MODULE V-BUKRG.

Processing after user input

PROCESS AFTER INPUT.

Lock customer master record

CHAIN.

FIELD GSSG-KTNRG

MODULE ENQUEUE_CUSTOMER_MASTER.

Read customer master record

MODULE READ_CUSTOMER_MASTER.

Read business area

MODULE READ_GSSG.

ENDCHAIN.

Process function code

FIELD OK-CODE MODULE OKCODE ON INPUT.

regards,

sunil kairam.

Re: module pool tips

Former Member — Thu, 06 Dec 2007 11:25:16 GMT

Hi ,

Just go through the below link you will find all regarding module pool

http://help.sap.com/saphelp_47x200/helpdata/en/e4/2adbef449911d1949c0000e8353423/frameset.htm

Reward if usefull

Thanks,

Ramya.

Re: module pool tips

Former Member — Thu, 06 Dec 2007 11:28:21 GMT

Hi Sir,

The best link to lear module pool programming(dialog programming) is to go through the link :

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

you will find all related queries and answers for that over here..

Thankx.

Plz reward if helpful.