topic Re: when we create a program from se38 in Application Development and Automation Discussions

when we create a program from se38

Former Member — Mon, 06 Aug 2007 08:43:05 GMT

We are provided to choose one of the values such as 'Executable Program', 'Module Pool' etc.

Here is the question is that I, up to this time, coded just executable program.

I wonder how and why we could use 'Module Pool'.

What can we do with module pool?

Thanks in advance.

Deniz.

Re: when we create a program from se38

Former Member — Mon, 06 Aug 2007 08:49:11 GMT

module pool is used to create custom screens with table-controls, subscreens etc which may be used for both input/output.

If your ABAP program requires a user dialog then dialog programming is required.

A user dialog is any form of interaction between the user and the program :

Entering data

Choosing a menu item

Clicking a button

Clicking or double clicking an entry

It is also used when we need to navigate back and forth between screens

Dialog Programs:

A dialog program allows you to work interactively with the system and to change the contents of the database tables. Each dialog program has a certain sequence of screens that are processed by the system one after the other.

From the view of a user, a dialog step consists of receiving a screen for entering data, then after the users clicks a button or selects a menu entry, processing is started. From the view of the SAP system, the screen is prepared and sent. After this, the user receives it and fills it out. Then the system analyzes and processes the data contained on the screen after receiving it from the user.

A dialog program offers:

a user-friendly user interface

format and consistency checks for the data entered by the user

easy correction of input errors

access to data by storing it in the database.

Components of Dialog Program

Transaction Codes

Starts the screen sequence.

Can be created through transaction SE93.

Screens

Each dialog program consists of one or many screens.

They are called either by

Transaction codes outside the program

Using CALL SCREEN statement in corresponding program

Dynamic programs have their own data objects called screen fields that are linked to input/output fields that appear on the screen

Screen consists of screen mask or layout and its flow logic. A flow logic determines the logical processing within screen.

Screen has an independent component of program called GUI status.

GUI Status

Each screen has GUI Status/es which are independent components of the program. These include

Menu Bars

Standard toolbar

Application toolbar

Function key settings

Can be created through Menu Painter in ABAP Workbench.

ABAP Program

Each screen and GUI Status in R/3 system belongs to single ABAP Program

An ABAP Program includes dialog modules called by the screen

also check this link

http://www.sapmaterial.com/dialog_programming.html

Hope this helps

if it helped, you can acknowledge the same by rewarding

regards

dinesh

Re: when we create a program from se38

Former Member — Mon, 06 Aug 2007 08:55:05 GMT

Hi,.

Look at the below link

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

Regards

Sudheer

Re: when we create a program from se38

Former Member — Mon, 06 Aug 2007 08:59:08 GMT

'Executable Program' 　on line list program

Classical Reports

These are the most simple reports. Programmers learn this one first. It is just an output of data using the Write statement inside a loop.

Classical reports are normal reports. These reports are not having any sub reports. IT IS HAVING ONLY ONE SCREEN/LIST FOR OUTPUT.

Events In Classical Reports.

INTIALIZATION: This event triggers before selection screen display.

AT-SELECTION-SCREEN: This event triggers after proccesing user input still selection screen is in active mode.

START OF SELECTION: Start of selection screen triggers after proceesing selection screen.

END-OF-SELECTION : It is for Logical Database Reporting.

[Edit section] Interactive Reports

As the name suggests, the user can Interact with the report. We can have a drill down into the report data. For example, Column one of the report displays the material numbers, and the user feels that he needs some more specific data about the vendor for that material, he can HIDE that data under those material numbers.

And when the user clicks the material number, another report (actually sub report/secondary list) which displays the vendor details will be displayed.

We can have a basic list (number starts from 0) and 20 secondary lists (1 to 21).

Events associated with Interactive Reports are:

AT LINE-SELECTION

AT USER-COMMAND

AT PF<key>

TOP-OF-PAGE DURING LINE-SELECTION.

HIDE statement holds the data to be displayed in the secondary list.

sy-lisel : contains data of the selected line.

sy-lsind : contains the level of report (from 0 to 21)

Interactive Report Events:

AT LINE-SELECTION : This Event triggers when we double click a line on the list, when the event is triggered a new sublist is going to be generated. Under this event what ever the statements that are been return will be displayed on newly generated sublist.

AT PFn: For predefined function keys...

AT USER-COMMAND : It provides user functions keys.

TOP-OF-PAGE DURING LINE-SELECTION :top of page event for secondary list.

module pool: screen desizn

pbo

pai

Re: when we create a program from se38

Former Member — Mon, 06 Aug 2007 11:00:07 GMT

Module pool programs are useful in dialogue programming